İOS 26 beta battery %1

No, when you are using CarPlay you go into the CarPlay settings on your radio, go to display settings and there use to be an option to toggle on and off the “smart display zoom“ ever since the new iOS update to 26.4 beta the setting is no longer available and the CarPlay screen is to large for the veh 12” vertical screen.

Just change the label in your customized version and then change the configuration to use a different value for QueueDirectories. Then, when your directory gets modified, it will launch your custom process, not the system one.

Do you have a feedback report yet? If not, would you mind to file one with a sysdiagnose, and share your report ID here? The way to capture a sysdiagnose is detailed in the instructions. Given that killing apsd makes the last notification come through, which approves the subscription for your Mac is there, and that the same code and configuration work well on iOS, and also the systems before macOS Sonoma, but just not on macOS 26.3, the issue is most likely a bug. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thanks for the clarification. In the case where you fetch with nil change token, the server will give you all the records it has, which you can use to build up a new local cache (and destroy the existing one). Other than the bullet c in my previous post, you don't need to care about the deletion history, do you? Best, —— Ziqiao Chen  Worldwide Developer Relations.

In my case I was told that my app is somehow too simialr to one that a previous developer account submitted, but that account was terminated, so they think I'm spamming them. I don't know what it is that is too similar, because they won't give me any explanation. I develop new features, rejected again, zero explanation what it is they find objectionable, or how to identify what must be addressed. It's basically somew sort of weird Kafka novel going on. Have you ahd any luck with your by now, any new information they may have given you?

I am having the same experience. I have no problem with reviews rejecting submission, with some sort of explanation. But there is never an actual explanation, just copy/pasting of the policy text, which explains nothing concretely. You can waste weeks and month on building new features and may all be a red herring because they actually meant something else. It's very strange, I don't understand why they refuse to give a simple straight-forward answer. Your app is spam. Could be one of these 10 reasons, but we won't tell you wich. Ok, I have completely rebuild things, added new features and really proud. Your review actually motivated me to make the app even better, look at all these changes I have made. Thanks fro driving me to do better. Please accept now? No, your app is spam. Could be any of these 10 reasons but we won't tell you which. Have you had any luck since then? Any new advice they gave you? or did you end up just abandoning it?

If you use your intent phrase inside of the Xcode scheme settings (there is a place called Siri Intent Query where you can type it in), does the same thing happen? If that's still giving you trouble, then the next thing I'd do is create a brand new test project in Xcode, give it an app name that's pretty unique, and bring in the basic outline of your Siri intent code, and make sure everything is working there. The goal of that is so that you review all of the integration steps again from a clean slate to make sure you didn't miss anything, as well as validating that once the code does run, you have a basic functional outline you can build upon for exploring the API as you build out the feature for your real app. Jumping ahead a step, one additional thing that trips people up when debugging their intent extension is a misunderstanding of when the code runs — it is in a separate process, and so depending how you launch it, breakpoints you set for debugging may or may not be activated. A good rule of th

Thanks again for reporting the issue. It seems that the issue is impacting the community, but I haven't seen any feedback report ID posted here. Do folks have any feedback report yet? If not, would you mind to file one and share your report ID here? I understand that filing an actionable feedback report takes time, but that will help. I am trying to capture the issue, and yet, my current configuration, Xcode 26.2 (17C52) + iPhone 17 Pro with iOS 26.3 (23D127) + Apple Watch series 10 with watchOS 26.3 (23S620), does work for me. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thanks for your post as it seems very well written explaining the issue with the code in the end, but following your code as you just looking at a subscription is difficult to understand what is the cause of the issue. I’m not an expert in subscriptions but I wonder looking at your code if could be a Swift's concurrency issue as you are not setting the for await result in Transaction.updates ? I think the problem may b3e that your current handler, though running on @MainActor, processes transactions sequentially within that single loop. If processing takes even a few milliseconds, new updates can arrive and pile up behind the currently processing one, potentially leading to them being handled more than once if logic isn't airtight? I do believe by encapsulating your logic within an actor and using a set for deduplication, you create a predictable and thread-safe environment for handling StoreKit's asynchronous transaction updates, effectively solving the duplicate problem you've encountered. Somethin