“apple pencil battery life”

[quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] I need to support both use case (exec and dylib). [/quote] OK. [quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] [Library validation] does not apply in my scenario since the library is provided by a third party [/quote] I’d like to better understand that. It’s quite common for Mac apps to use libraries created by other developers, and they retain library validation by re-signing those libraries. Is there something preventing you from doing that in this case? The most obvious case where folks need to disable library validation is that their app supports in-process plug-ins, where those plug-ins are built and shipped by other third-party developers in a way that’s completely independent of the main app’s vendor. Is that what’s happening here? Because if you’re managing these plug-in releases then it’d be better to have you re-sign the plug-in and leave library validation enab

Thanks for bringing this to the forums. The com.apple.token keychain access group, aka kSecAttrAccessGroupToken, isn’t a normal keychain access group. Rather, it’s a special group that holds all of the credentials that the system finds in CryptoTokenKit (CTK) tokens. Given that, you can’t add credentials to this group directly. It is possible to create a persistent CTK token, that is, one that’s not tied to smart card hardware. If you do that then the credentials published by that token will be available to all apps that are set up to use token-based credentials. It’s not clear whether this approach will work for your ultimate goal: [quote='819445021, h-noto, /thread/819445, /profile/h-noto'] so that Microsoft Edge for iOS … can … use it for client certificate authentication [/quote] My advice is that you first prototype this with an actual smart card [1]. If you can get that working, it’d be worth exploring the virtual token option. Finally, if you’re curious how an app can work with token-based credentials,

We're experiencing a similar issue with our app (Apple ID: 6754461151) and wanted to share our situation in case others are facing the same. Our app has been stuck in Waiting for Review twice in a row now: Version 1.0.2: Submitted February 7, 2026. After 24 days with zero movement, we were forced to withdraw it. Version 1.0.3: Submitted March 3, 2026. Now at 17 days with no progress. In total, we've been waiting 41 days across two submissions with no feedback, no rejection, no communication from Apple. Steps we've already taken: Submitted an Expedited Review Request 7 days ago - no response Contacted App Review Status support Verified our App Review Information is complete, including demo credentials and invite code Confirmed all agreements and banking details are up to date

[quote='819454021, oleksandr91, /thread/819454, /profile/oleksandr91'] Is this a known macOS bug? [/quote] I’m pretty sure I’ve seen this before. IIRC the problem was reported by a third-party developer and I found it super hard to reproduce, and thus I’m not sure if a bug got filed. Sorry to be vague about the details; I searched my records but was unable to track down the conversation. Anyway, it sounds like you can easily reproduce this. Given that, I think it make sense for you to file your own bug about it. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='819449021, Team Tank Wars, /thread/819449, /profile/Team+Tank+Wars'] the remaining uploads do not proceed in the background and appear to be suspended. [/quote] Suspended forever? Or just a delayed? If you leave the watch in that state for a day, does it eventually attempt these stalled uploads? For context, there are URLSession and watchOS aspects to this. On the URLSession front, the system is free to delay background session transfer until an opportune time. While I have a lot less experience with this on the watchOS side, on iOS this often means that the transfer is deferred until overnight, when the device has both Wi-Fi and mains power. So I’m curious if the same thing is happening on the watch. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Please submit a feedback assistant ticket (http://feedbackassistant.apple.com), and we can assist further. Please provide as much information as possible, ie a sysdiagnose, app apple ID, in-app apple IDs, sandbox account apple ID (if applicable), transactions IDs, steps to reproduce and other relevant details. File ticket under iOS & iPadOS, macOS, tvOS, watchOS, or visionOS and ensure you select “App Store” for the question “Which area are you seeing an issue with?” Categorize the type of feedback Please attach all available files needed to verify After submitting the feedback, please regularly check the ticket as we'll only communicate through it from then on. Once you open the Feedback Assistant Ticket report, please post the FB number here for reference. If you have any questions about filing a report, take a look at Bug Reporting: How and Why?

It looks like you’re trying to report a bug. If so, the way to do that is via Feedback Assistant. See my Bug Reporting: How and Why? for a lot more info about that process. Please post your bug number, just for the record. FWIW, I’m seeing the same issue with Swift Playground 4.7 on my Mac, so this is not iPad specific. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s not clear what you’re asking for here: Are you a developer who wants to use TestFlight to run a test programme? Are you a user whose been invited to a test programme by a developer? Are you a user who would like to be invited to a test programme by a developer? Or something else? Please clarify. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='819406021, eddiewangyw, /thread/819406, /profile/eddiewangyw'] With ad-hoc signing … the system treats each build as a new app. [/quote] Correct. If you’re curious about the mechanics of this, have a read of TN3127 Inside Code Signing: Requirements. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='819553021, robonaren, /thread/819553, /profile/robonaren'] my understanding is that root daemons typically don’t run sandboxed [/quote] Correct. While it is possible to enable the App Sandbox on a daemon, folks don’t normally do that. [quote='819553021, robonaren, /thread/819553, /profile/robonaren'] The plugin only connects to the legitimate daemon [/quote] The canonical way to do that is by setting the privileged flag. I have a link to an explanation of that in XPC Resources. You could also validate the peer’s signature. Again, I have a link to info about that in XPC Resources IMPORTANT This works in this direction because you control the daemon’s main executable. [quote='819553021, robonaren, /thread/819553, /profile/robonaren'] The daemon only accepts connections from trusted clients [/quote] There isn’t a good way to achieve this goal, presuming that this set of trusted clients includes an authorisation plug-in. The issue is that authorisation plug-ins are in-memory plug-ins, so you don’t control

Are you really supplying an empty Apple Account string? Or did you just redact that for the sake of this post? Regardless, I have a couple of generic bits of advice here: To get started, use the store-credentials subcommand. It runs you through the authentication process interactively, which can help head off the most obvious errors. Make sure you’re using an app-specific password, rather than the password for your Apple Account. An app-specific password should have the format aaaa-aaaa-aaaa-aaaa, where each a is a lowercase letter. If you get stuck, switch to authenticating with an API key. IME it’s often easier to get that working. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com