Hello, I have an iOS application that has been submitted for review and is currently in the “Waiting for Review” state. App details: App Name: Fato Platform: iOS Version: 1.2.6 Submission date: February 10 Current status: Waiting for Review This update includes significant UI and user experience changes following previous App Review feedback, including a custom-built interface and updated metadata. The app has been waiting for review for several days without moving to “In Review,” and I wanted to ask if this duration is expected for apps with prior review history, or if there is anything additional I should check from my side. I have already submitted an expedited review request and opened a Developer Support case, and I would appreciate any general guidance on expected timelines or next steps. Thank you in advance.
Search results for
İOS 26 beta battery %1
258,419 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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.
Topic:
App & System Services
SubTopic:
Core OS
On Sequoia, I want to configure my postfix as a server. And for this I have to change the way postfix is started from: /System/Library/LaunchDaemons/com.apple.postfix.master.plist But this file is on the read only / file system. Then I just unloaded this startup, and made a new one in: /Library/LaunchDaemons/com.apple.postfix.master.plist and I was able to start it. But on the next system boot, the system one in /System/Library/LaunchDaemons was started again. How should I cleanly and permanently achieve this server basic modification?
Topic:
App & System Services
SubTopic:
Core OS
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.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
I have the following code running on macOS and iOS: CKQuerySubscription *zsub = [[CKQuerySubscription alloc] initWithRecordType:ESS_CLOUDCONTROLLER_RECORDTYPE_PUSHNOTE predicate:[NSPredicate predicateWithFormat:@TRUEPREDICATE] subscriptionID:@pushZSub options:CKQuerySubscriptionOptionsFiresOnRecordUpdate|CKQuerySubscriptionOptionsFiresOnRecordCreation|CKQuerySubscriptionOptionsFiresOnRecordDeletion]; zsub.zoneID = zid; CKNotificationInfo *inf = [[CKNotificationInfo alloc] init]; inf.shouldSendContentAvailable = YES; inf.desiredKeys = @[ESS_PN_RECORDFIELD_KEY_OVERALLDATE]; zsub.notificationInfo = inf; CKModifySubscriptionsOperation *msop = [[CKModifySubscriptionsOperation alloc] initWithSubscriptionsToSave:@[zsub] subscriptionIDsToDelete:nil]; msop.qualityOfService = NSQualityOfServiceUserInitiated; msop.modifySubscriptionsCompletionBlock = ^(NSArray * _Nullable savedSubscriptions, NSArray * _Nullable deletedSubscriptionIDs, NSError * _Nullable operationError) { dispatch_async(dispatch_get_main_queue(
Hi everyone, I'm currently experiencing an unusually long time for my app to be reviewed. I'm curious to know if other people are experiencing the same problem, since I don't remember it ever taking this long for a submission to be reviewed. I first submitted my app for review on February 9th, and resubmitted it on February 16th (one week later), requesting an expedited review. On the 18th, I contacted support (2 days ago). I still haven't had any changes to my submission, and haven't heard from support either. A client of mine has had their submissions reviewed as usual. I'm not sure if there's a specific issue with mine that's causing the delay. I haven't found any phone numbers I can call, and I'm quite anxious about this because we are trying to fix a critical bug, and all our campaigns are on hold until we fix this. Has anyone experienced this before? How did you get it resolved? Any help is greatly appreciated 😊
Hi there, I’ve been having ongoing issues with my Apple Watch. Last week I updated it to watchOS 26.3. The next day it accidentally ran out of battery, and since then it has been randomly restarting, showing an overheating message. I suspected it might be related to the update, so I researched online and on the official Apple forums. People recommended resetting the Apple Watch and unpairing it from my iPhone. I did both procedures, but the problem persists, even when the watch is in a cool environment. I’ve been using it normally, but it still restarts multiple times a day. Yesterday I even updated to the public beta of watchOS 26.4 hoping it would fix the issue, but it didn’t help — the random restarting continues. Today I also unpaired and paired it again with my iPhone, and the problem is still happening. This has been very disruptive and frustrating. I’m following up on my previous message because I’ve found additional diagnostic information that may help identify the cause of the issue
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.
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
I'll try to ask a question that makes sense this time :) . I'm using the following method on NSFileManager: (BOOL) getRelationship:(NSURLRelationship *) outRelationship ofDirectoryAtURL:(NSURL *) directoryURL toItemAtURL:(NSURL *) otherURL error:(NSError * *) error; Sets 'outRelationship' to NSURLRelationshipContains if the directory at 'directoryURL' directly or indirectly contains the item at 'otherURL', meaning 'directoryURL' is found while enumerating parent URLs starting from 'otherURL'. Sets 'outRelationship' to NSURLRelationshipSame if 'directoryURL' and 'otherURL' locate the same item, meaning they have the same NSURLFileResourceIdentifierKey value. If 'directoryURL' is not a directory, or does not contain 'otherURL' and they do not locate the same file, then sets 'outRelationship' to NSURLRelationshipOther. If an error occurs, returns NO and sets 'error'. So this method falsely returns NSURLRelationshipSame for different directories. One is empty, one is not. Really weird behavior.
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?
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
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
Topic:
Machine Learning & AI
SubTopic:
Apple Intelligence
Tags:
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.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only) I unpaired/removed the Watch in Xc