Overview

Hello App Review team, Our new app (Apple ID 6826152478, iOS 1.0.0) has been in "Waiting for Review" since October 23, 2026 and has not moved to "In Review". Timeline: October 23: Submitted for review (first submission) November 1: Contacted App Review about the submission status (case 103015644818), received only the automatic confirmation Last week: Requested an expedited review, no response November 5: Requested an expedited review again, no response yet There are no messages from App Review in App Store Connect, and all agreements are active. Could you please check whether the submission is queued correctly and let us know if anything is needed from our side? Thank you

My Apple Developer Program enrollment has been stuck for several weeks and I can't get a response through any channel. Hoping someone from Apple can flag this internally. Situation: The enrollment fee is already paid — authorized and showing as completed on my card. My government-issued photo ID was uploaded earlier, before I made the payment. Developer Support (Case #102982502169) emailed asking me to re-upload my ID via https://developer.apple.com/contact/file-upload/ — but that link redirects to /contact/file-upload/ineligible and shows "Sorry, you don't have access. Your account isn't authorized to upload files", even when I'm signed in as the account holder. So I physically cannot complete the step they asked for. What I've tried: Replied to the email thread (Case #102982502169, Case #103012285256, Case #103015741490) multiple times — no response. No phone/callback option is offered for my account. Apple Support chat confirmed they have no way to escalate to the developer team. Could someone please either enable the file upload for my case, or confirm my ID is already on file so enrollment can be completed? Case #102982502169. Happy to provide any details. Thank you.

Hello Apple Developer Community, We are experiencing a significant delay with our first production release and would appreciate guidance from anyone who has faced a similar situation or can help escalate this to the appropriate Apple team. Our app, PriceEasy Enterprise, has been stuck in "Waiting for Review" for over 4 days, and the review process has not started yet. App Details: App Name: PriceEasy Enterprise Apple App ID: 6822673059 Version: 1.0 Build: 4 (1.0.3) Current Status: Waiting for Review What we have tried so far: Submitted 4–5 expedited review requests through Apple's official channel. Contacted Apple Developer Support requesting manual escalation. Sent follow-up emails explaining the business impact. Requested a callback from the support team and provided contact details for our Senior Developer and CEO. Unfortunately, we haven't received any meaningful response or update, and the submission remains in the same status. Business Impact: Our company's headquarters is in Houston, Texas, USA, and we serve clients across the US and internationally. This release is important for our business operations and client commitments. The delay is affecting our planned launch. We would appreciate help with the following: Has anyone experienced a similar delay recently? Were you able to get your submission moved into review through Developer Support or another escalation channel? Is there any way to get direct assistance from the App Review Operations team? Can an Apple representative help investigate why the submission has not yet been picked up for review? We understand that Apple needs sufficient time to review every submission. However, given the repeated expedited requests and lack of response, we would really appreciate some guidance or assistance. Thank you for your time and help.

Hey, I waited 2 weeks almost for my app to be reviewed and then it was rejected for 4.8 which I fixed that evening and re-submitted the updated version, now almost a week on nothing has happened. No replies to support tickets either. This is just not good enough, we all pay our yearly fees and this service!! And then you see that other apps (new and updates) are approved in a day or 2. Some transparency would be really helpful! App ID - 6812923427 Come on Apple sort this nightmare out!

My app Gaft (Apple ID 6798040496) was rejected on October 27 under 5.1.1(i)/5.1.2(i). I fixed the issues and resubmitted build 60 on October 28, 2026 (submission ID 7a53fa92-fcea-43fb-a0f6-37620fe0eb77). An expedited review was approved on November 2, but the submission (app version, two subscriptions and one in-app purchase) is still in "Waiting for Review" with no messages. Developer Support case: 103002520980. Agreements and banking are active. Could the App Review team please check whether this submission is stuck? Thank you.

Hello everyone, I am looking for assistance or guidance regarding my Apple Developer Program enrollment. My Apple Developer Support Case ID is 102993829177. Timeline of my enrollment and communications with Apple Developer Support October 8, 2026 - Paid the $99 Apple Developer Program membership fee and received an official payment confirmation from Apple. On the same day, I submitted my Russian international passport for identity verification. Apple confirmed receipt of the document. However, my enrollment remained Pending, and the system continued asking me to purchase the membership again. October 12 - Contacted Apple Developer Support for the first time regarding my pending enrollment. Support case 102993829177 was created. October 16–17 - Received a response from an Apple Developer Support representative explaining that my international passport confirmed my country, but additional documentation was required to verify my city of residence in Russia. October 17 - Replied to the support representative and submitted photographs of my Russian internal passport, including the identification page and the residential registration page showing my current address. No response received. October 22 - Sent a follow-up email asking for confirmation that the documents had been received and requesting information about the next steps. No response received. October 29 - Contacted support again to request an update on my enrollment and document verification. No response received. In summary, I have sent three messages since the additional documents were requested - on October 17, 22, and 29 - without receiving any response. As of November 5, 2026, it has been 28 days since my payment and 19 days since I submitted the additional documents. My Apple Developer account still shows "Pending" and continues to display "Purchase your membership", even though the membership fee has already been paid. Phone support is not available to me. I understand that document verification may take additional time. However, I currently have no confirmation that my latest documents have been received and are being reviewed, or whether any further action is required from me. I would appreciate any guidance from Apple Developer Support representatives or community members on how to obtain an update on my enrollment status and determine the next steps. Apple Developer Support Case ID: 102993829177. Thank you for your assistance!

Hi an update to my app Central 365 was approved on 23/10/26 and my app is set to auto distribute. However it is still not visible in the store and i have raised 3 unanswered support tickets. There was an issue with signing update terms which i resolved on 26/10. Please advise this is poor service so hoping someone on this forum can advise.

On macOS 26.5.2 (build 25F84), which documented API and return conditions, if any, establish that a regular file on APFS has no extended access control list (ACL), using an already-open file descriptor? We tested three disposable regular files on an APFS volume reporting ACL support. For each file, we opened a read-only file descriptor and called: acl_get_fd_np(fd, ACL_TYPE_EXTENDED) fgetattrlist() requesting ATTR_CMN_RETURNED_ATTRS | ATTR_CMN_EXTENDED_SECURITY Before and after inspection, fstat() confirmed stable device, inode, mode, and change timestamp. Observed results: 1. Newly created file, no ACL explicitly assigned acl_get_fd_np() returned NULL with errno == ENOENT. fgetattrlist() succeeded but omitted ATTR_CMN_EXTENDED_SECURITY from the returned attribute mask. FSOPT_PACK_INVAL_ATTRS also left that bit clear. 2. File with an explicitly assigned empty ACL acl_get_fd_np() returned NULL with errno == ENOENT. fgetattrlist() returned the extended-security attribute with an ACL entry count of zero. 3. File with one explicit ACL entry acl_get_fd_np() returned a non-null ACL. fgetattrlist() returned the extended-security attribute with an ACL entry count of one. Apple's published XNU attribute-packing implementation appears to use the same omission branch when ACL metadata is unsupported or when the ACL pointer is null. My question: Is there a supported descriptor-based API sequence that reliably distinguishes: Genuine absence of an extended ACL Unavailable or unsupported per-file ACL metadata An ACL retrieval failure If so, which API, capability checks, return values, attribute bits, or error conditions should a caller rely on? Are there relevant APFS or macOS version limitations? If the public API cannot establish ACL absence unambiguously in this situation, confirmation of that limitation would also be helpful. Thank you for your guidance.

Hello, I am trying to enroll in the Apple Developer Program (Individual) from Turkey, but the payment is repeatedly declined at the final step. My bank confirms there is no problem on their side and that the charge is not being declined by them. What I have already tried, all with the same result: Multiple cards from 3 different banks 3 different browsers, plus Linux, Windows, and an iPhone The Apple Developer iOS app (as suggested by Apple Support over email) Matching the billing address exactly to my account address Removing Turkish characters from my name This looks like the known issue currently affecting Turkey-based enrollments, as many other developers are reporting the same problem in these forums. Could a member of Apple staff please review my account and manually process the enrollment if needed? Account email: omerfarukunlu@ proton.me Region: Turkey Enrollment type: Individual Support case ID (varsa): 102892859221 Thank you for your help.

Hello, My iOS game Trickshot (Apple ID: 6811020289) has been in "Waiting for Review" for more than 10 days. According to Apple's App Review documentation, 90% of submissions are reviewed in less than 48 hours, so this wait is far outside the stated timeframe. There are no messages in App Store Connect, and all agreements, tax, and banking forms are complete. I have already submitted an expedited review request and contacted App Review through the Contact Us form, with no response to either. Could someone from App Review please check whether this submission is stuck? Thank you.

Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.

Hi everyone, After my app was rejected, repeated contact attempts and an appeal have not led to any meaningful guidance. What should I do next? Apple ID: 6807882674 Review timeline (all dates are in 2026): September 7: First submitted the app for App Store review. September 16: The app was rejected. I then sent three messages through Contact Us and received no reply to any of them. I subsequently submitted an appeal, which also received no response. During this period: I continued developing the app, updating the review information and resubmitting. Multiple TestFlight external beta builds were also rejected. When I contacted Apple about those rejections, the replies were generic process information with no specific advice on what to change. October 20 (UTC): Resubmitted the app for App Store review. As of October 27, it is still Waiting for Review, with no further update. It has been 50 days since my first submission, including rejection, an appeal and resubmissions. I understand that reviews take time. However, the replies I have received feel mechanical and unhelpful: they repeat general process information without addressing my specific questions or explaining what needs to change. I still do not know how to move forward. Has anyone experienced a similar situation? How can I obtain case-specific guidance? If an Apple staff member sees this, could you help check my case or advise on the next step? I can provide the relevant case numbers through the support channel. Thank you for your help. I will update this thread daily until there is substantive progress with the review.

Hi everyone, I submitted my Digital Services Act trader information on October 30. I verified both my email and phone the same day and received the "We received your trader contact information" confirmation email. Since then, the status under Business → Compliance has stayed at "In Review". My app was approved on October 28 and has been "Ready for Distribution" since then. But under Pricing and Availability, Spain (the only country I've selected) shows "Trader Status Not Provided", so the app isn't available on the App Store. I've contacted Developer Support several times by email (no reply yet), and phone support says it's currently unavailable. Has anyone else experienced long DSA verification times recently? How long did it take for you? And is there anything else I can do on my side to speed it up? Thanks in advance!

Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!

Looking for experience from developers whose "4.3(a) Design - Spam" rejection was eventually explained or overturned. My situation: Our developer account has no other apps. This app is our own code, design and data. Nobody on the team is on any other developer account. The app is the iOS client of a web service that has been live since 2025 with an active community of a few thousand registered users. The same app got recently published on Google Play. The app allows logged-out browsing, though many features require a free account. Sign in with Apple, OAuth and email/password are all supported. Since this is largely a community app, we built proper moderation and privacy features: automated Amazon Rekognition screening and human moderation of all user-submitted media before it is published, plus block and report for users and content. The app is in the collecting / tracking hobby and covers niche material that mainstream apps do not carry. For several of the franchises we carry we are not aware of any App Store app at all. First version: rejected 4.3(a). We rewrote the subtitle, keywords and description. Second review: the same boilerplate 4.3(a) text, no explanation. Appealed to the App Review Board: upheld, no app named, same generic response. Second version (about a month later) a genuinely different release with new released: focus shifted to community features, messaging, full iPad support with proper design, new screenshots. We also attached a video walkthrough of the features no other app covers and gave the reviewer detailed instructions on where to find them and why they matter to users. Result: the same 4.3(a) text after about 15 days in review, again no app named. Our server records show the demo account we provided in App Review Information was never signed into during the second review (no auth event, no SDK session). Everything the review notes point to is behind sign-in. The codebase is Expo. The only stock pieces are the RevenueCat paywall and the social login buttons. Everything else is ours, including a large backend and data pipeline. What I would love to know from others who faced this: when your 4.3(a) was finally resolved, what was the actual cause? What did the journey look like? Anything concrete would help me know where to look.

We requested a transfer of our Apple Developer accounts to our organization several months ago. We've followed up multiple times by email but haven't received any response, and this is blocking our app releases. Is there a recommended way to escalate this, or is there a known processing delay for account transfers? Any help from Apple staff would be appreciated.

Hi, The Musickit SDK for Android seems to be broken after the Apple Music app update from last week. We are launching the intent like this: AuthIntentBuilder aib = authManager.createIntentBuilder(appleTokenProvider.getDeveloperToken()); Intent intent = aib.build(); authLauncher.launch(intent); A new Apple Music UI is shown. The user is asked to login with email and password. However, after succesfull login the intent returns the error USER_CANCELLED for authManager.handleTokenResult(data); This was not the case before the latest Apple Music app update. The only workaround is to logout in the Apple Music app, then retry to launch the intent in our app. This has to be done every time the music user token expires. Any ETA on fixing this issue?

When using AlarmKit (AlarmPresentation.Alert), the native system buttons (Stop / Open) successfully trigger the assigned AppIntent (e.g., implementing AppIntent with perform()) when running on the iOS Simulator. However, on physical devices (Real iOS Devices), these native buttons are completely dead. Even with a paid Apple Developer Program account, Production/Release-level code signing, and a clean build, tapping the native buttons on the Lock Screen / Full Screen alert results in zero calls to perform() (no logs, intent handler is never invoked). OS Version: iOS 27.0 Xcode Version: Xcode 27.1 (27A9275) Device: iPhone Air Provisioning: Paid Apple Developer Account (Production / TestFlight build) Is this a known system-level bug in AlarmKit where SpringBoard fails to route intent events to third-party apps on real devices? If so, is there any workaround to capture the action of the native Stop/Open buttons, or are developers expected to rely solely on custom Live Activities (.widgetURL) for navigation? Any guidance would be greatly appreciated!

Hello App Review team, Our first app, TCE Voyage Desk (iOS 1.0, build 18, Apple ID 6813479264), was submitted for review on October 16, 2026, together with its in-app purchases (Pro Annual subscription and Pro Lifetime). The submission is still pending, and there are no messages from App Review in App Store Connect. On our side: the Paid Apps agreement, tax and banking information are active; our EU trader status (DSA) was verified on October 23; we sent a status inquiry on October 28 (case ID 103011262463) and received only the automatic confirmation. Could you please check whether anything is needed from us to complete the review? We will provide any information right away. Thank you.

We would like to ask for an expedited review of our App Issue: Version 2.7.2 (build 2070302) was released on November 5, 2026 at 9:16 AM. It crashes immediately on launch on iOS 27 devices, every time (EXC_BREAKPOINT in _UIApplicationEvaluateRuntimeIssueForNoSceneLifecycleAdoption). Users on iOS 27 cannot open the app at all. Cause: The build was made with Xcode 27.2 (iOS 27 SDK), and the app had not yet adopted the UIScene lifecycle. That is now required for apps built with this SDK. Fix: Version 2.7.3 adopts the UIScene lifecycle. We tested launch, deep links and sign-in on iOS 27. This build changes nothing else: no new features and no content changes. So this crash blocks our business right now. A fast review would help a lot. Thank you for your help. Best regards.