apple pencil charging

The error here, -25303, or errSecNoSuchAttr, suggests a problem with your attributes. And the only non-required attribute you’re supplying is kSecAttrApplicationTag. Which is, in fact, the cause of your issue. kSecAttrApplicationTag is only supported on keys. I recommend that you have a read of SecItem: Fundamentals [1], and specifically the The Four Freedoms^H^H^H^H^H^H^H^H Functions section, which explains how you can use SQL to model the expected behaviour of the SecItem API. In this case, the SQL table for certificate items has no kSecAttrApplicationTag, and thus this error. It also has links to the doc that explains which keychain item class supports which attributes. [quote='815390021, ellinj, /thread/815390, /profile/ellinj'] Is there an alternative to create SecIdentity without keychain access? [/quote] We finally (finally finally!) have this. See the docs for the SecIdentityCreate function. IMPORTANT This was added in Xcode 26 but backdeploys to much older systems. Or at least that’s the plan (-: Thi

That’s not the right API to use for receiving datagrams. Rather, use the receiveMessage(completion:) method or one of its variants. That ensures that you get the entire datagram in one hit. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815354021, JacobHearst, /thread/815354, /profile/JacobHearst'] OSLogStore … it only collects logs for the current process [/quote] Correct, at least on everything except the Mac. I cover this and many other logging topics in Your Friend the System Log. There isn’t truly a happy path here. When it comes to NE debugging, you need to see the full system log and there are no APIs on iOS that’ll let you get that. Oh, one last thing. If you’re goal is to work with Apple to help debug a problem, you can ask your user to file a bug in Feedback Assistant. That’ll attach a sysdiagnose log to the bug report. You won’t be able to see the sysdiagnose log, but if you pass the Apple folks that bug number they should be able to get it. I talk more about this idea in Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='815402021, AbubakrLatif, /thread/815402, /profile/AbubakrLatif'] have created new certificate [/quote] Yikes! That won’t help with this issue and, as these are Developer ID certificates, it can have negative consequences. Developer ID as precious, as I explain in The Care and Feeding of Developer ID. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

knytko wrote: Yes, reported today with ID FB13636366. Thanks for that. Annoyingly, that bug got lost in our system and there’s been no progress on it. I’ve taken steps to get it on the right track. Lanmac, Are you developing an app that contains a system extension? Because reading through your post it doesn’t look like you’re hitting the issue being discussed here. If you’re having a problem with the Finder that’s unrelated to app development, I recommend that you bounce over to the Apple Support Community, run by Apple Support. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

At the top of the Signing & Capabilities editor there’s a Team popup. What does that show in your case? For context, it looks like Xcode thinks that you’re working in a Personal Team. However, the App ID in your screenshot is registered to an Individual team (Team ID 9________S). Individual teams should be able to use NE capabilities, so I’m not sure why Xcode isn’t letting you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815340021, Leo_Nagano, /thread/815340, /profile/Leo_Nagano'] If this is a known limitation or bug in how Xcode validates NE entitlements for Developer ID [/quote] Indeed, this is a known bug in Xcode’s code-signing support )-: [quote='815340021, Leo_Nagano, /thread/815340, /profile/Leo_Nagano'] is there a recommended workaround? [/quote] You have to sign your product manually, outside of Xcode. Exporting a Developer ID Network Extension has all the details here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815372021, MattStewart, /thread/815372, /profile/MattStewart'] is NEFilterDataProvider supported on non-supervised devices for consumer App Store apps …? [/quote] No. TN3134 accurately reflects the allowed deployment paths for NE content filters. [quote='815372021, MattStewart, /thread/815372, /profile/MattStewart'] is this a platform restriction that cannot be worked around? [/quote] You shouldn’t think about this as something to be “worked around”. Rather, this is a platform privacy policy. If there were a way around it, that’d be a major security bug. Notably, macOS, being a different platform, has a different policy. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815439021, faisalIkwal, /thread/815439, /profile/faisalIkwal'] Is there any officially supported way to specify a port range in NENetworkRule? [/quote] I think you’ve answered this yourself (-: If you’d like to see this change in the future, I encourage you to file an enhancement request describing your requirements. And please post your bug number, just for the record. Oh, one more thing. The port range in your example coveres ephemeral ports, which I presume is not a coincidence. If so, consider focusing on that in your ER. The ephemeral port range has changed in the past and it wouldn’t surprise me if it changed again in the future. OTOH, a general port range feature would be more flexible. (One of the nice things about your filing your own ERs is that you get to explain your own requirements in your own words.) [quote='815439021, faisalIkwal, /thread/815439, /profile/faisalIkwal'] Is creating thousands of rules (one per port) considered acceptable or supported? [/quote] Again, I think you’ve answe

DevForums is primarily focus on technical issues. For legal advice, I recommend that you consult an actual lawyer. If you have questions about App Review policy, my advice is: Read App Review Guidelines. If you have further questions, feel free to put them in a new thread in the App Store Distribution & Marketing > App Review topic. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Apple can fairly say: “Agents shouldn’t directly edit our serialization format.” But if they advertise agentic workflows and the agent can’t reliably do core build/debug tasks (target build settings, linking, schemes), then the product gap is real. Agentic workflows require a closed loop: apply build-setting changes → build → fix → repeat. If the only exposed interface is “chat + inline code edits,” it’s not agentic for build/debugging. Therefore Apple needs a supported automation surface (typed project actions with preview/undo), regardless of how ugly project.pbxproj is. Expected: Agent can apply target/scheme/build-setting changes (typed + preview/undo), run build, iterate on failures. Actual (Xcode 26.3 RC): Agent mostly suggests or edits source files; can’t reliably adjust the build/ debug configuration loop for multi-target/C++ integration. C/C++ integration is where an agent should shine because it’s repetitive, error-driven, and configuration-heavy. A “real” agentic C++ loop in Xcode