apple pencil battery life

Thank you for your post. There are a few details that need clarification. Could you please provide the iOS version you are using? Additionally, how do you ascertain that the app is not receiving the token? A more detailed description of how to initiate the activity or if the user initiates the activity would be greatly appreciated. Do you have logs on these method to see if gets called? On the TASK I would add some logs to see when it gets called. https://developer.apple.com/documentation/activitykit/starting-and-updating-live-activities-with-activitykit-push-notifications Additionally, it is crucial to trace the issue if possible. Kindly provide me with the following information for a failed notification: The precise time and date (including the time zone) of the push notification. The public IPv4 address of the server that sent the push notification. The push topic (apns-topic header value). The app’s Bundle ID. The device token. The apns-id if it is set. The full contents of the headers and the payload. An

@RickMaddy I think that might be a little out of scope for this thread. But in any case, I was able to update my macOS 26.1b2 VM to 26.1b3 via my logged-in Apple Account, so I don't think it's universally broken. Although my host is still on Sequoia 15.7.1. The closest thing I've experienced to what you're describing is an issue that I've seen for a while where logging in with an Apple Account hasn't been working for me if I have physical security keys enabled on my account for 2FA (FB19614234). Unfortunately if you're in this situation I don't know of any workaround other than removing all the security keys (and even if you re-enable them after logging in with the VM, eventually the VM will start complaining with pop-ups asking you to login again, although beta updates will still work despite this). This isn't new to 26.1, though. If this isn't the issue you're experiencing you might find better luck creating a new thread since I don't think many people with similar issues are going to find

Kevin and ssmith_c for your assistance. I fortunately managed to file in the bug: FB20677188 Thank you! Looking over the bug, there was one point I wanted to comment on: For the Matter Media Device Basic Video Player Type Apple Home does support the commissioning (adding the device to the list of accessories displayed in Home App), but no controls are displayed. Not even the mandatory required controls: ... This type of Matter Device, which is part of the standard, should at least expose the mandatory controls and commands. The idea that Apple (and general ecosystem vendors more broadly) should try and support the full range of the Matter specification is, IMHO, one of those ideas which sounds reasonable on the surface but is, in fact, a very bad idea. First off, quoting myself: The Matter specification itself is sufficiently broad and complex that, in practice, I'm not sure it will ever really be possible to create a high-quality controller app* that actually supports EVERY possible accesso

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome Albert Pascual
  Worldwide Developer Relations.

The value shown there is the LLVM/clang/swiftc target triple that Swift Testing used when Apple compiled it. Swift Testing's minimum deployment target (the lowest version of the OS you can run it on) is iOS 13, so the target triple shows iOS 13.

I am working on a Gaussian Splatting App using the UnityGaussianSplatting package and building for Apple Vision Pro. I want to be able to load splat (.ply / .splat) files from the Vision Pro's storage into the application. OK. So the main issue to be aware of here is the difference between works fine for a developer and works well for a user. For development purposes, you can basically just set the two keys (UIFileSharingEnabled/LSSupportsOpeningDocumentsInPlace) and then use your Documents directory as your working storage. There could be issues if you edited or deleted those files while your app was actively running, but you will just avoid those issues... by not doing that. On the other hand, if you're planning to ship this to end users then you'll need to use things like file coordination to avoid those issues. Similarly, apps that are more viewer oriented (meaning, they don't edit the files they're working with) often use an import model where they copy (actually clone, so they don't use additio

I can't give legal advice on whether potential actions violate the terms of developer agreements. I suggest that having your customers manage their own MDM push certificates makes sense from the point of view of segmentation of risk. MDM is a very powerful technology, and rarely people abuse it. When Apple becomes aware of abuse of MDM it may take various actions in response. These actions may include revoking the MDM push certificate involved in the abuse, revoking the MDM vendor certificate associated with the MDM push certificate, removing the MDM CSR permission, and/or terminating any Apple Accounts, Apple Developer Program accounts, or Apple Developer Enterprise accounts associated with those certificates. As a device management service vendor, consider if one of your customers abuses device management capabilities and Apple revokes the MDM push certificate and the associated Apple Account. If your device management service used the same MDM push cert