apple pencil battery life

Thanks for the post. You are receiving phone calls from blocked numbers in iOS 26? 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 I would recommend contacting them to help you on that feature as should be working well in iOS 26. Thanks, Albert Pascual
  Worldwide Developer Relations.

Hi @scavengar Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. I'd greatly appreciate it if you could open a bug report, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report. In the meantime try deploying Building a guessing game for visionOS to TestFlight as a means of debugging. If that reproduces the issue, please add that information to the bug report. Otherwise try comparing your code to the sample code as a means of debugging.

Dear Apple, with regards to the above - can you please shed light on the connection between: CXProvider delegate method providerDidReset This is called when the XPC connection between CXProvider and callservicesd is interrupted. invalidate() method in CXProvider Among other things, this breaks the XPC connection between CXProvider and callservicesd. If you call invalidate(), then the delegate will receive providerDidReset. Is it 100% always true? When it comes to software engineering, I am violently allergic to the word always. The system is big, complicated, and constantly evolving, which means there's a pretty big difference between: This is what the system normally does VS The system behaves this way under all circumstances today, in previous versions, and in all future versions Yes, I suspect providerDidReset generally does get called when you invalidate, both now and in the past. That's the strongest promise I'll make. My current Xcode has a line like: The provider must be invalidated before it

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

Thank you for your answer. I tried with both AsheKube.app.a-Shell.localWebServer and com.example.example-extension. The only difference I could see is that sometimes it would fail when uploading (I would get the error message inside Xcode) and other time it would fail after uploading: I would get a kind e-mail from AppStore Connect, stating: Hello, We noticed one or more issues with a recent delivery for the following app: a-Shell App Apple ID 1473805438 Version 1.17.0 Build 500 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90349: Invalid Info.plist value - The value of the EXExtensionPointIdentifier key, AsheKube.app.a-Shell.localWebServer, in the Info.plist of “a-Shell.app/Extensions/localWebServer.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. Apple Developer Relations Builds 496

Could you provide a test project that reproduces the issue. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. For additional tips on creating Apple Developer Forums posts, see tips on writing forums posts.

Did anyone found a solution? I have a small update, when upgraded to Xcode 26 (instead of Xcode 16), the appclip did not build right away. The reason was Apple has changed how we need to create the .entitlements files. So I had to do the following: com.apple.developer.parent-application-identifiers - $(PARENT_APP_IDENTIFIER) + $(AppIdentifierPrefix)com.mydomain.parentID i.e add AppIdentifierPrefix + parentID instead of PARENT_APP_IDENTIFIER With this fix, the appClip got build with Xcode 26. My issue with appClip invocation is not yet fully fixed (though now it works on some cases), but hope this will give someone a starting point. Let me know if anyone found a proper solution. I have also opened a feedback and the number is FB20453270

Thank you again! As the project is (currently) only for internal testing, the Document directory way works fine for now. I've set the keys (both were necessary), and now the App's Documents folder shows up in On My Apple Vision Pro. Reading & writing content in there via Unity's Application.persistentDataPath works fine as well. Just what I wanted. Thank you very much for your help!

As per usual - once you post about something the solution just comes to you. The solution for anyone running into the same thing is just adding Apple Vision as the only destination for the Share Extension target, and removing the Apple Vision (Designed for iPhone) one that is automatically created for the template.

I have a small update, when upgraded to Xcode 26 (instead of Xcode 16), the appclip did not build right away. The reason was Apple has changed how we need to create the .entitlements files. So I had to do the following: com.apple.developer.parent-application-identifiers - $(PARENT_APP_IDENTIFIER) + $(AppIdentifierPrefix)com.mydomain.parentID i.e add AppIdentifierPrefix + parentID instead of PARENT_APP_IDENTIFIER With this fix, the appClip got build with Xcode 26. My issue with appClip invocation is not yet fully fixed, but hope this will help someone. Let me know if someone found a better solution. Note: I have seen it works in some phones with iOS 26 (like iPhone 14) when I use the appClip code (circular code), but not with plain QR code, and that too not on all phones (still not works on 14 pro max). But once it works on a given phone, it worked on normal QR code too (weird, I know). My best guess is that it' a cache issue.

We tried testing this in two ways. The first was by disabling the Camera App in Settings App → Screen Time → Content & Privacy Restrictions → Allowed Apps & Features. We used the API [UIImagePickerController isSourceTypeAvailable:UIImagePickerControllerSourceTypeCamera] to return YES and checked AVAuthorizationStatus was AVAuthorizationStatusAuthorized. The other was by setting the profile mobile config setting allowCamera to false. The test results were still the same: always return YES. I think it's an Apple iOS 26.1 beta2 beta3 bug and hope it can be fixed as soon as possible. Thank you.