apple pencil charging

[quote='816179021, GangOrca, /thread/816179, /profile/GangOrca'] Whereas, with conditional variables, there are no warnings. [/quote] I wouldn’t read too much into that. These warnings have to be explicitly coded, and we added that code for Dispatch semaphores because that’s the most common offender here. It wouldn’t surprise me if we added a similar warning for pthread condition variables at some point in the future. Then again, it wouldn’t surprise me if we didn’t. The pthreads API is relatively obscure. [quote='816179021, GangOrca, /thread/816179, /profile/GangOrca'] What is the recommend way? [/quote] There isn’t a supported way to block the main thread of a GUI application for long periods of time. On macOS it will SPOD, which is a terrible user experience. On other platforms the app will likely end up being killed by the watchdog. And to be clear, the issue here isn’t about the specific APIs you’re using, it’s this overall design. Speaking of iOS and friends, app termination [1] behaves very differently

I recommend that you review the fine print in general, and specifically the note about AI tools on the submission form. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hmmm, this isn’t first time I’ve seen this. I don’t know anything about it personally, but I recommend that you check out this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Under review since February 6 — already 14 days! The saddest part is that our whining doesn’t seem to interest anyone. Let’s face it, no one has replied to us in the thread so far. Thanks, Apple.

Same here. Apple Support keeps repeating that I should send them a video recording of the entire process where the HTTP error occurs. Has this issue been resolved?

Hi @Antonikhin, did you get your answer from Apple? If yes please share with us!

Hi @ericD_TRI and @SkimoBen Thanks for providing such a detailed question with reproducible code, that's very helpful. I was able to reproduce the issue you're experiencing. The problem appears to occur when deleting or overwriting a .reality file that's associated with an entity currently in the scene, which causes the Failed to load errors on subsequent loads. Workaround: Instead of reusing the same filename, create a unique file for each save operation. You can store the current filename in your appModel so the immersive view knows which file to load. For example: let filename = (UUID().uuidString).(type.preferredFilenameExtension ?? bin) //... try await entity.write(to: fileURL) appModel.activeFileURL = fileURL Finally, 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, reference this forum post, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creati

I have some information. I downloaded Xcode 26.3 Release Candidate (17C519) from the Apple Developer website. I used the VirtualBuddy app and installed macOS Tahoe 26.3. I then opened the Xcode project and configured the StoreKit Configuration file (synchronised with App Store Connect), setting the subscription renewal rate to Any Renewal Every 10 Seconds. I ran the app, made a subscription purchase and observed that my in-app purchase handling code successfully completed the transaction. I also logged Transaction.updates and Product.SubscriptionInfo.Status.updates and everything worked as expected. However, I do not wish to upgrade to macOS Tahoe just yet.