Overview

Hi, my app is stucked with the status "Waiting for review" for the last 4 days. It's crucial for me to get my app reviewed. Anything wrong ? Thanks for your answer.

Hello, I am hoping someone from Apple or the community can help escalate or advise on my situation. I submitted a Live Caller ID Lookup entitlement request for my app Zinfo (com.parastashvili.Mobile), Team ID: CNH4KYRW44. A support case was opened on February 17, 2026 (Case ID: 102823550184). Apple's documentation states entitlement review takes up to 2 weeks. It has now been over 3 weeks with no substantive response despite multiple follow-ups. Timeline: Feb 17: Case opened Feb 26: I provided all requested technical details in full — OHTTP endpoints, Privacy Pass token system, DNS TXT record, Apple test number (+1 408 555 1212 returning "Johnny Appleseed"), all fully deployed and ready for validation Feb 27: Apple replied with a generic "appropriate team will be in contact" message Feb 28, Mar 6, Mar 10: Follow-up emails sent — no meaningful response All technical requirements are fully implemented and operational. We are ready for Apple's validation at any time. Has anyone else experienced long delays with Live Caller ID Lookup entitlement reviews? Is there a better escalation path? I have also submitted a new escalation ticket (Case ID: 102840874265) under Development and Technical > Entitlements today. Any advice or visibility from Apple staff would be greatly appreciated. App: Zinfo (com.parastashvili.Mobile) Extension Bundle ID: com.parastashvili.Mobile.LiveCallerID Team ID: CNH4KYRW44

Thanks!

Hi App Review Team, I would like to raise a concern regarding the review process for our app update (Version 2.0.0), which has now been pending for over two weeks. We completely understand the importance of the review process, but the extended delay is starting to impact our business. This update is not a major change—the app already exists on the App Store, and Version 2.0.0 mainly includes UI improvements. The core functionality remains the same as the currently approved version. Additionally, the app has been rejected multiple times with the status “Information Needed.” We have been promptly providing all the requested information each time, but the repeated cycle is significantly extending the overall review timeline. We kindly request guidance on how to move forward more efficiently, or if there is anything specific we can provide upfront to avoid further delays. If possible, we would also appreciate support in expediting the review. Any help or clarification would be greatly appreciated, as this delay is leading to business loss. Thank you.

Hi Community, The Leverage macOS has with Bootstrap token is immense using the same for Software Updates, Erase Device and new Local Account Creation in System Settings While I refer From IT Deployment Guide Which States the below For a Mac with macOS 10.15.4 or later, when a secure token-enabled user logs in for the first time, macOS generates a bootstrap token and escrows it to a device management service. I even tested out the Statement using Automated Device Enrollment Workflow ( With AutoAdmin Account Only, With Both AutoAdmin Account , Primary Account ) and it Granted BootStrap Token Immediately upon login How ever with User-Initiated Enrollments it differs like below Sometimes upon installation of MDM Profile in macOS Immediately the BootstrapToken is sent to MDM Sometimes the BootStrapToken is not immediately sent, so I need to logout , login with the Secure Token enabled user for macOS to escrow BootStrapToken to MDM Sometimes Even when I followed the pointer as in 2) like logout / login from a SecureToken Enabled user the BootStrapToken is not escrowed to MDM , Which Affects the OSUpdates, Erasing Capabilities to be used precisely with MDM Protocol Can someone Please Help with the Flow for BootStrapToken Generation / issuance to MDM incase for User-Initiated Enrollment

Hi everyone, I observed a behavior with AirPrint from an iPhone and wanted to confirm if this is expected behavior from iOS. Scenario tested: File type: Photo Print-quality selected by the user: Normal Observation (from packet capture): When checking the PCAP for the request sent from the iPhone, the print-quality attribute is always sent as high, even though the user selected Normal in the UI. Question: Is this an expected behavior in iOS/AirPrint where photos are always sent with print-quality=high regardless of the user-selected print quality? Or could this be a bug?

I am trying to figure out why my app is not receiving background deliveries from Healthkit. I have a successfully implemented HKObserverQuery  which is being used to send data like step count to a server. I have a successful enableBackgroundDelivery (completes without errors). I have also checkmarked the HealthKit Background Delivery and Clinical Health Records options in my app's Signing and Capabilities configurations. I know the observer is functional because the health data gets sent to the server when the app is running. The problem is I haven't seen any evidence of the observer handler being triggered when the app is not running. What am I missing? And what is the best way to go about debugging what is going wrong?

I'm a developer from Nigeria trying to complete payment for the Apple Developer Program (organization enrollment). This has been ongoing for over 2 weeks with no resolution. My enrollment is fully approved. D-U-N-S verified. The only issue is the payment. Here's what I've experienced: Multiple payment attempts with two different USD cards (Grey, Chipper Cash) Payments either fail silently (no error shown, order acknowledgement email received, but no charge on card and account not activated) or return "Duplicate Order" error A $0.00 card verification charge went through on one attempt, but the actual $99 was never charged The enrollment page keeps showing "Complete your purchase" every time I log in I submitted a support email request over 3 weeks ago — zero response I have a completed app ready for App Store submission being delayed by this Organization enrollment, D-U-N-S verified, all enrollment steps completed. Only the payment step remains. I've seen many developers in these forums reporting the same issue since February 2026. Is there a known issue with the enrollment payment system? Can an Apple team member please look into my case or clear the duplicate order so I can retry with a fresh transaction? Any help from the community or Apple staff would be greatly appreciated. This is blocking my entire product launch.

hi, the email i used to create my apple store is no longer accessible by me... I need to change it, but have no way of contacting since when I click "contact for an issue" it defautls to that email that I can't see

I'm unable to notarize my macOS app — notarytool returns statusCode 7000 ("Team is not yet configured for notarization"). My Developer ID certificate is valid (expires 2031), code signing works fine. Timeline: March 4 — opened case 102832266798 via Developer Programs Support March 6 — Apple replied, but the email never arrived (not in spam either) March 9 — sent follow-up requesting the response be resent — no reply March 13 — opened new case 102840272497 via Program Enrollment form — waiting It's been 9 days with no resolution. DTS confirmed this is not a technical issue and referred me to Developer Programs Support. Team ID: 9NL8W3646T Bundle ID: com.traart.app How can I escalate this? Has anyone experienced a similar situation with a new account?

I am requesting a dedicated toggle in Settings > Display & Brightness (or Accessibility) to enable/disable the Liquid Glass UI effects so that I am able to get frosted glass thingy effect that was in iOS 18 back.

Our app's status has been completely frozen for both App Store Distribution and TestFlight. No status changes are occurring, which is preventing us from releasing updates to conduct beta testing. Or upload the app to App Store.  App Details: App Name: Memento - where you’ve been Apple ID of the app:  6758897827 Issue since: February 8, 2026 Current stuck status:  "Waiting for Review" for both distribution and TestFlight  Steps already taken: submitted more then 3 tickets to Apple support (No response) App review expedite ticket . we addressed some issues that could have been causing the delay in distribution (bugs and fixes) and uploaded the app for review again. We made sure any app information were clear in the review draft ( our data usage, features of the app, our privacy policy, support URL ) Given the duration and business impact of this issue, I am requesting that this be escalated to the appropriate review team for investigation. any help would be greatly appreciated

Recently I noticed that although my drive showed ~800Gb of usage, the folders within totally to around ~600Gb (and yes I was including hidden 'dot' files/folders. After some inspection I found that there are a whole set of Disk Media Images, that appear to be related to XCode simulators. Here's an extract from the command line diskutil list command: /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk5 Physical Store disk4s1 1: APFS Volume iOS 26.2 Simulator 17.1 GB disk5s1 /dev/disk6 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.2 GB disk6 1: Apple_APFS Container disk7 14.2 GB disk6s1 /dev/disk7 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.2 GB disk7 Physical Store disk6s1 1: APFS Volume XROS 26.2 Simulator 13.8 GB disk7s1 /dev/disk8 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.2 GB disk8 1: Apple_APFS Container disk9 17.2 GB disk8s1 /dev/disk9 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.2 GB disk9 Physical Store disk8s1 1: APFS Volume iOS 26.0 Simulator 16.7 GB disk9s1 /dev/disk10 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +8.5 GB disk10 1: Apple_APFS Container disk11 8.5 GB disk10s1 /dev/disk11 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +8.5 GB disk11 Physical Store disk10s1 1: APFS Volume XROS 2.5 Simulator B... 8.2 GB disk11s1 /dev/disk12 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +18.0 GB disk12 1: Apple_APFS Container disk13 18.0 GB disk12s1 /dev/disk13 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +18.0 GB disk13 Physical Store disk12s1 1: APFS Volume XROS 2.5 Simulator 17.5 GB disk13s1 /dev/disk14 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.6 GB disk14 1: Apple_APFS Container disk15 17.6 GB disk14s1 /dev/disk15 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk15 Physical Store disk14s1 1: APFS Volume iOS 26.1 Simulator 17.1 GB disk15s1 /dev/disk16 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +14.1 GB disk16 1: Apple_APFS Container disk17 14.1 GB disk16s1 /dev/disk17 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +14.1 GB disk17 Physical Store disk16s1 1: APFS Volume XROS 26.1 Simulator 13.7 GB disk17s1 /dev/disk18 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +17.6 GB disk18 1: Apple_APFS Container disk19 17.6 GB disk18s1 /dev/disk19 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +17.6 GB disk19 Physical Store disk18s1 1: APFS Volume iOS 26.1 Simulator 17.1 GB disk19s1 /dev/disk20 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +9.1 GB disk20 1: Apple_APFS Container disk21 9.1 GB disk20s1 /dev/disk21 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +9.1 GB disk21 Physical Store disk20s1 1: APFS Volume iOS 18.5 Simulator B... 8.8 GB disk21s1 /dev/disk22 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +20.7 GB disk22 1: Apple_APFS Container disk23 20.7 GB disk22s1 /dev/disk23 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +20.7 GB disk23 Physical Store disk22s1 1: APFS Volume iOS 18.5 Simulator 20.2 GB disk23s1 I am unable to unmount them, either from the command line or Disk Utility. How do I go about this?

The second time i start a workout session, the beginCollection instance method on HKLiveWorkoutBuilder freezes. To recreate run the Apple Sample Project Building a multidevice workout app. It looks like a bug with the HealthKit SDK and not the code but i could be wrong. The only workaround i found was erasing the simulator and reinstalling the app.

I want to localize the app name, user the String Catalog to set en, en-US, en-CA, however, when the phone language is set to English (United States), the app name is displayed in English, while when the phone language is set to French, the app name is displayed in English-United States. However, the base language of the app settings is English. How can I make it right?

Hi all, I need help with registering for the Apple Developer Program. I tried to purchase the membership from the web but the payments kept failing. I used different cards on both Chrome and Safari but none of them worked. Then I downloaded the Apple Developer app but on my account, it said the enrolment is not available. I sent support tickets to Apple several times but got no replies so far. I am stuck and ran out of options. What else can I do to enrol into the Apple Developer Program so that I can start publishing my app? Why does Apple make it so difficult at this step? Thanks

Hi everyone, My app has been stuck on "In Review" for about 3 days now. Before that, it also spent around 3 days in "Waiting for Review," so the total time has been close to 6 days. From what I’ve seen in the past, it usually takes 2–3 days to move from "Waiting for Review" to "In Review," and then only a few hours to get a decision once the review actually starts. However, this time it seems different. Based on my server/Firebase logs, it doesn’t look like the reviewer has opened the app yet or created a test account, so it seems like the review may not have actually started. This is my first app submission, so I’m not sure if that might affect the timeline. Has anyone experienced something similar recently? Is this normal, or is there something I should do (for example, contacting App Review or requesting an expedited review)? Any advice would be appreciated.

Hello, My app RecipePop seems to be stuck in the App Review process and I’m trying to understand if something might be wrong with the submission. App ID (Apple ID): 6758273317 Timeline: I have been submitting versions for a week and they remain in "Waiting for Review" for days.. Please help review this submission as soon as possible! My users are currently facing a bug that should have been fixed in this version. Any guidance would be greatly appreciated. Thank you.

Given that we can't use isEligibleForAgeFeatures property on macOS, the documentation states that In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. But in unsuitable region the requestAgeRange request always returns DeclaredAgeRange.AgeRangeService.Error.notAvailable which is vague, as it might stand for API being unavailable just as well as "You receive this error when the system prompts a person and they decide not to share their age range with your app. ", as per documentation. Unfortunately, this error fires immediately instead of showing any kind of prompt for user, so the description is definitely wrong (or incomplete) in here. Possible solutions: expand Error cases to separate not available API and not available response expand isEligibleForAgeFeatures to properly support macOS Moreover, unlike iOS, there is still no usable tool or algorithm to test given feature for macOS (mock region, mock age, mock source of approval, revoke declared range, etc). Now I get a review with rejection, stating that I don't have age verification mechanisms present in my app. Also I found out that after filling the App Information regarding Age Ratings it spreads to all fresh releases, so even though my newest macOS release doesn't contain age verification mechanisms yet, it should, as iOS release has got this functionality up and running already and I had to check this when filling Age Ratings questionnaire. Now I'm stuck between removing this capability from App Information, so the macOS release can pass and stalling macOS releases until there is a proper usable API to implement Declared Age Range verification properly (at least the same way as on iOS). How should I properly develop and test this feature for macOS before releasing it publicly?

I originally submitted a ticket on February 27th. My app was approved fairly quickly. I had it set for private distribution. Under private distribution I placed in all the organization information to ensure my app would show up on Apple Business Manager. I filled out all the agreements and tax information as well. The app was still not showing. I then went into country distribution and saw that all countries were disabled. I tried clicking into the USA option to enable it. It says ”Cannot Sell App”. It does not allow me to do anything else. it then directs me to contact Apple developer support For assistance. After waiting one week I got this reply from developer support. “Hello, Thank you for contacting Developer Support. My name is Yana, and I’ll be happy to help you. I would first like to apologise for this delayed answer. It is certainly not the normal waiting time for an answer from Developer Support. We are currently facing a huge number of request from our customers and your patience is well appreciated. I learned from the email that the app cannot be sold in the United States and Canada at present. You can go to App Store Connect to confirm the distribution method of the app. https://aninterestingwebsite.com/help/app-store-connect/manage-your-apps-availability/set-distribution-methods/ If you have additional questions related to this request, reply to this email or visit your recent cases. Your case number is 102833154976. Best regards, Yana Developer Support” After waiting a week, they referred me to an article (which I had already viewed) that did not resolve my issue. I replied that this was not helpful and that I still needed assistance. That was 9 days ago. I have not received any reply. I am at a total loss on how to resolve this issue. I cannot even get a reply to my messages. Please help!