apple pencil battery life

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.