“apple pencil battery life”

In iOS 26.4 the bug is still present. It seems the Apple team has forgotten to investigate the issue...

Thanks for the post, in this page you'll find a sample for AppClips as well as the first note will provide you the 101 of App Clips. I always recommend developers to go over all those videos and documentation liked on that note. Then download the app, look at every single configuration from that app including the Clip target! https://developer.apple.com/documentation/appclip/fruta-building-a-feature-rich-app-with-swiftui In my opinion and without going deep in your solution, the reason your AASA endpoint is never getting called when you scan the QR code is due to a common misconception about how iOS handles App Clips and Universal Links, the iOS device does not fetch the AASA file at the moment you scan a QR code. Downloads the file at app installation time and there is also a delay. When you scan a QR code, iOS checks its local cache and Apple's CDN records to see if that URL is registered to an App Clip. If Apple's CDN hasn't validated your AASA file, or if the TestFlight configuration is

❯ pkgutil --pkg-info-plist com.apple.pkg.MobileDevice groups com.apple.findsystemfiles install-location Library/Apple/ install-time 1772135996 pkg-version 4.0.0.0.1.1762585687 pkgid com.apple.pkg.MobileDevice receipt-plist-version 1 volume / I can't reply in the thread above as a comment due to limited text amount.

Is there any supported way for a sandboxed macOS app to read an MDM-delivered preference plist under /Library/Managed Preferences/? Any guidance on the correct and Apple‑supported method would be appreciated. There are basically two ways to make this work: Have the user select the file or directory using an open panel (or drag and drop). Use an entitlement that gives you access to the target directory. In this particular case, that means using one of the File Access Temporary Exceptions to hard-code access to /Library/Managed Preferences/. A few notes on that: The documentation suggests using Shared Preference Domain Temporary Exceptions. I would certainly try that; however, I suspect it won't work as Managed Preferences may not be part of the standard preference system. While there's always an inherent risk in using a temporary entitlement, I generally consider this particular entitlement set to be relatively safe. The entitlement’s role is clear and straightforward (it gives access to the target),

Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.

After additional testing, this appears to be an orphaned MobileAsset cleanup issue rather than a normal simulator uninstall problem. The runtime payload remains on disk under /System/Library/AssetsV2, but in some cases Xcode no longer exposes it in Components/Platforms and simctl does not have a usable reference to remove it cleanly. In other words, the asset still occupies space, but the supported management tools have effectively lost authoritative control over it. At that point the problem becomes structural: the remaining files are in a SIP-protected system location. So even if the exact asset folder can be identified, it cannot be manually removed through normal user-space means while SIP is enabled. That leaves no supported path to reclaim the space once the asset has fallen out of Xcode/simctl management. Technically, the remaining workaround is to disable SIP and remove the orphaned asset manually, but that is not a reasonable solution for routine simulator runtime cleanup. SIP exists specifically to

We advise against rapidly mutating content that is eligible for download retry, as it can lead to a fragile solution. For further information, please refer to our recommendations on the HTTP Live Streaming (HLS) authoring specification for Apple devices. If this solution is still desired, we suggest exploring the STABLE-RENDITION-ID and STABLE-VARIANT-ID attributes. This approach decouples the variant identity from its CDN location. To facilitate the refresh of the Multi-Variant-Playlist (MVP), you can rely on the HTTP cache-control headers. AVFoundation will attempt to retry expired MVP, but it will default to the cached playlist if a new MVP cannot be retrieved. To achieve the re-download behavior of the MVP, use the HTTP headers Cache-Control: must-revalidate, along with max-age.

When did you install the TestNet Profile and are you sure it's still valid? The previous profile expired in early February, so you'll need to have updated it recently. Note that you need to install the profile on all the devices involved and that a mixed configuration where the iOS device has the current profile but the HomeHub does not will very likely generate behavior similar to what you're seeing. Here is exactly what is happening: Our device successfully sends a QueryImage command to the HomePod. The HomePod receives it, but immediately fires back a QueryImageResponse that essentially means UpdateNotAvailable, forcing the device into an 86400-second sleep timeout. Chapter 4 of the Apple Matter OTA - User Guide (r6) outlines a number of specific recommendations and guidelines. Are you following all those guidelines, particularly around MinApplicableSoftwareVersion and MaxApplicableSoftwareVersion? Many of our recommendations in these specifications are best understood as requirements, not suggest

The Apple Developer Forums are for questions about APIs and features intended specifically for developers. Since it sounds like you went to the Apple Support Community already and were sent here because you are running a beta, then you should file a bug report in Feedback Assistant.

@michelbechelani-aya Yes, if you distribute the app using the Apple Developer Enterprise Program or TestFlight there is no need to resign the app, therefore everything will work on the app. Now the most robust way to handle OAuth/Sign-in flows in automated cloud testing does not need Universal Links entirely for your test builds. Create a specific build configuration for your cloud tests. In this build, configure your app to use a Custom URL scheme for its callback. Configure your staging/testing Auth Server to accept and redirect to this Custom URL scheme instead of the Universal Link (https://...). When the test runner triggers the login, the browser will redirect to myapp-test://, which the OS will route back to your app, regardless of who signed it. Not trying to side track you. Follow your architecture, but I want to make sure to show there are other options. Albert Pascual
  Worldwide Developer Relations.

Thank you for your post. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.