Overview

Post

Replies

Boosts

Views

Activity

Organization enrollment pending for 24 days – no response from Developer Support
Hello Apple Developer Support Team, I submitted an Apple Developer Program organization enrollment on October 29, 2026. Our organization has a valid D-U-N-S number, but our enrollment remains stuck at "Your enrollment is being processed." I have already submitted two support requests and received no substantive response. The phone/callback option is not available in my region. We have not yet been able to proceed to payment, and our iOS app launch is blocked. Could someone from Apple Developer Support please help us establish the status of our existing enrollment and confirm whether any further verification is required? Enrollment ID: 6PBPK975D8 Thank you.
0
0
13
32m
Waiting for Review since Monday, Nov 16. Our expedited review request was accepted on Nov 16 as well. Need review by Nov 24, 2026 to meet critical release deadline of Nov 30, 2026.
Hi, Our app has been in the Waiting for Review state, with an accepted expedited review request, since last Monday, Nov 16, 2026. Request: If it is at all possible, could our app get reviewed in time for our release deadline of Monday, Nov 30, 2026? If reasonable, a review result by Tuesday, Nov 24, 2026 would leave us time to fix anything you flag and re-submit for review. Reason: Monday, Nov 30, 2026 is our studio’s fiscal year-end. The game has to be live by then to be included in this year’s Ontario Interactive Digital Media Tax Credit claim, which is administered by Ontario Creates, an agency of the Ontario government. Missing the date by even one day pushes that funding back a full year, which is very hard on a studio our size. We can send documentation if that helps. The expedited request we made through Developer Support had no place for an explanation, so I want to make sure the reason and the date reach the review team. I know this is a big ask during a busy period, and I’m grateful for any help you can give. Thank you, William App Apple ID: 6832757024 Version / build: 1.0.0 Submitted: Nov 16, 2026 Original Expedite Request Date: Nov 16, 2026 Requested Latest Review Date: Nov 24, 2026
0
0
4
33m
Account-wide TestFlight build expiration issue — Feedback ID: FB25656884
@DTS Engineer (Albert), I am experiencing the exact same issue across all 3 apps on our team account (TJ9KJ6WV99). Every newly uploaded, validated build (Binary State: Validated, beta-reports-active: true) automatically changes status to Expired within 30–60 minutes of upload and disappears from TestFlight, despite all agreements (Paid Apps, Free Apps), Tax Forms, and DSA Compliance being verified Active (since account reactivation on Oct 29, 2026). Apple Support performed a backend process restart 48 hours ago which temporarily resolved the issue, but all new builds reverted to Expired again today within an hour (matching the BETA_CONTRACT_MISSING / backend state desync reported earlier in this thread). Feedback Assistant Ticket: FB25656884 (includes Team ID TJ9KJ6WV99 and all 3 numeric App IDs). Thanks in advance for routing this to the TestFlight / App Store Connect team!
1
0
96
33m
macOS: supported absolute deadline at final network egress, including queued bytes?
Hi, I’m assessing feasibility before implementing a small macOS HTTPS snapshot client. The requirement is strict: every request-bearing byte must cross the final controlled network-egress boundary before an absolute deadline. A byte crossing at or after the deadline fails. For context, the intended deadline is 07:41:00 Europe/London on a specified date, converted to UTC. This concerns request transmission, not response completion. An application precheck or a deadline to begin sending would not satisfy it. Is there a supported macOS API or mechanism with a documented guarantee covering this requirement? Specifically: Where is the enforcement boundary? Does expiry cover request bytes already queued in TLS/TCP, kernel, driver or NIC buffers, partially transmitted requests, and retransmitted request payload? Does enforcement remain fail-closed if the client or enforcement process is suspended, hangs or crashes, or the Mac sleeps and wakes? Can queued bytes resume transmission after expiry? What clock and deadline semantics apply, including equality, uncertainty, clock steps/regression and unavailable or unreliable time? Can connection reuse or buffering bypass expiry? Application retries, redirects and additional requests would be prohibited. How could an implementation observe and qualify the actual controlled egress boundary, rather than an earlier callback or queue? I have reviewed documentation for: NWConnection.ContentContext.expirationMilliseconds, which describes expiry for beginning transmission; NWConnection.SendCompletion.contentProcessed; Network Extension packet filtering, delayed-packet verdicts and provider lifecycle; TN3134 and TN3165. I have not found a documented end-to-end guarantee covering the cases above. I am not assuming that filters, cancellation, timers or socket timeouts provide it. Could an Apple engineer point to the applicable supported contract and platform restrictions, or clarify that this strict guarantee is not provided? If a mechanism is applicable, please identify supported macOS versions, required entitlements and any relevant interface or hardware limitations. This is a documentation/feasibility question only. No external service, account, credentials or capture is involved. An authoritative reference—or an explicit statement of unsupported cases—would be helpful. Many thanks in advance.
0
0
3
34m
iPhone Duo: Dual-display output and tent mode detection
I’m developing Foma, a design app with a full-screen gallery, and have two questions about iPhone Duo: In tent mode, can a third-party app show its gallery on the outer display while presenting noninteractive content on the inner display, without an active camera session? I tried ExternalNonInteractiveAccessory on a physical iPhone Duo running iOS 27.3 beta, but the inner display stayed dark. Is there a public API that detects tent mode directly? If not, does Apple recommend combining hinge angle with device orientation or gravity? Thanks!
0
0
3
35m
Unable to renew Apple Developer Program membership — no response to support case 30000011940191
Hello, I’m unable to renew my Apple Developer Program membership. My membership expires on November 26, 2026. I opened a support case with Apple Developer Support on November 11, 2026, case ID 30000011940191, but I haven’t received any response yet. I’m very worried that my membership will expire before this is resolved and my apps will become unavailable on the App Store. Could someone from Apple Developer Support please look into my case and get back to me? I would be very grateful for any help. Thank you
2
0
92
35m
Review submission stuck in "Canceling" for 12 days: version locked, can't cancel or resubmit
Our iOS review submission has been stuck in CANCELING since 10 Nov 2026. Every action on it is refused, so we haven't been able to ship an update for 12 days. App ID: 6809173786 Stuck submission: 0c25955e-e5d8-4835-8605-79f8115c9992 Developer Support cases: 103018649498, 103018648320 App Review case: 30000012887740 The submission has 4 items, all still "Ready for Review": iOS App 1.0.14 (app version) Lifetime-Flybud (our first non-consumable IAP) retention-3840x2160.png (Asset Library image) Flybud_Orbit_Header_3840x164… (Asset Library video) What the App Store Connect API returns (22 Nov): Cancel the submission: "Resource state is invalid – Resource cannot be canceled at the moment, please try again later." Remove an item: "Resource state is invalid – Item was already submitted." Add 1.0.14 to a new submission: "Asset Library validation error – Asset is locked by a standalone review submission." Submit the IAP on its own: "The first Non-Consumable In-App Purchase for this app must be submitted for review at the same time that you submit an app version." The version is locked by the stuck submission, and the IAP can only ship with a version, so everything is blocked. New builds upload and process normally. Given error 3, I suspect the Asset Library items are what's preventing the cancellation from completing. Since 10 Nov I've written to App Review four times, opened two Developer Support cases, filed a bug report and emailed the App Store team. Phone support has been unavailable, and App Review can't see the submission in their queue. Could someone at Apple escalate this to App Store Connect engineering to clear or complete the cancellation? Thank you.
0
0
3
36m
First app Waiting for Review since 1 Nov, support case has no reply
Our first app, PerCent: Personal Finance (Apple ID 6826506651), has been Waiting for Review since 1 Nov 2026 (submission 52e16f91-b3f5-4bfd-bdb5-babb9706518c). We requested an expedited review on 3 Nov and opened Developer Support case 30000005014098 on 4 Nov. We have received no reply, and there are no messages in App Store Connect. Could someone from Apple please check whether this submission is stuck or whether anything is needed from us? Thank you.
4
0
110
36m
Can an XPC receiver verify that App Sandbox is active for the sender?
We are designing a macOS launcher that waits for a one-use reply before starting a child process. Two instances of the same signed launcher may be running. Before replying, the receiving service needs to verify that App Sandbox is active in the specific process instance that sent the request. We can check the sender’s signed App Sandbox entitlement. Is there a supported public API or documented procedure that also lets the receiver verify the sender’s active runtime sandbox? If so, what evidence ties that observation to the sender of this XPC message, including if the sender exits and its PID is reused? Please identify the documentation and applicable macOS versions. If the supported check establishes only the signed entitlement, confirmation of that limit would also help.
0
0
8
37m
TestFlight dead on new accounts (Oct-Nov 2026): no invite emails, Beta App Review 422 "Please try again later". Collecting all cases here
This thread collects every account with the fault below in one place, so Apple sees one issue across many accounts instead of many lonely threads. If you have it, please reply. What to include is at the end. The fault Builds upload and process fine. Then two things never work: No TestFlight invite email is ever sent. Every tester, internal or external, stays "Invited". Reinvite does nothing: POST /iris/v1/betaTesterInvitations returns 201 Created and no email arrives, not in spam either. A build cannot be submitted for Beta App Review. "There was an error processing your request. Please try again later." POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE with only that sentence and no further reason. So internal testing is blocked by the missing emails and external testing by the refused review. Agreements, tax, banking and DSA are Active, Test Information and export compliance are complete, and nothing a developer can change makes a difference. The accounts reporting it are mostly new, enrolled around October 2026. My case Account enrolled 31 October 2026. Fault since 5 November 2026, every day. Region: Türkiye. No invite email reaches any of my six testers. Beta App Review submit returns the 422 every time. On 13 November I reset everything to rule out my side: removed every tester and both groups, expired the old builds, uploaded a fresh build, added everyone again. Nothing changed. The fresh build is VALID. Its internal state is IN_BETA_TESTING with "automatically notify testers" on, yet its record says the testers were not notified. Its external state is READY_FOR_BETA_SUBMISSION and the submit is refused. Feedback Assistant: FB25540791 (two HAR logs). Developer Support cases 30000005155573 and 30000005989992: only automatic receipts since 4 November, no human reply. Phone support shows as unavailable. Others reporting it https://developer.apple.com/forums/thread/856330 (@Hopeforge): internal invite emails never delivered, testers stay "Invited". Recreating groups, resending and new builds did not help. An App Store Connect Engineer replied there and asked for Feedback Assistant tickets with HAR logs. https://developer.apple.com/forums/thread/857012 (@Kirnuvirsta): tester stuck on "Invited" with no email, Beta App Review submit fails, same on a second app record. FB25399719, case open since 28 October. https://developer.apple.com/forums/thread/856896 (@medlzd, @ganderbite): new internal testers show "Invited" and never get the email, Resend Invite does nothing, on all apps. https://developer.apple.com/forums/thread/856592 (@EmlakBaseDev): Beta App Review submit returns 422 "Please try again later" on three apps since 24 October, build VALID and READY_FOR_BETA_SUBMISSION. https://developer.apple.com/forums/thread/854803 (@SefaAygun, @JanuaryTwelfth): adding a build to external testing fails with "try again later". https://developer.apple.com/forums/thread/854106 (@BWGTrading): new organization account, TestFlight stopped working for all apps on 27 October. If you have this too, please reply with When your account was enrolled, and since when the fault shows Which of the two you have: no invite emails, 422 on Beta App Review, or both Your country or region, to see whether it is tied to one Your Feedback Assistant number (FB...) and Developer Support case ID Anything Apple told you, and above all whether it got fixed, and how If you have not filed a Feedback Assistant ticket yet, please do: steps, a HAR log of the failing request, your App ID. The engineer in thread 856330 asked for exactly that. To Apple Could someone from the App Store Connect or TestFlight team tell us whether this is a known fault in how TestFlight is set up for newly enrolled accounts, and whether each account needs a change on your side? We are paying members who cannot use TestFlight at all, and our support cases stay unanswered for weeks. Thank you.
18
8
830
37m
Is viewController in authenticateHandler always nil now?
I set an empty handler that never presents the view controller: GKLocalPlayer.local.authenticateHandler = { _, _ in }When the player isn't signed in, the Game Center sign-in sheet still appears, apparently presented by a separate system process rather than through the viewController parameter. Is viewController now effectively always nil, with sign-in fully owned by the system? Or should apps still handle a non-nil view controller, as the current documentation describes?
0
0
13
1h
MKMapItem addressRepresentations fullAddress singleLine does not always work and provides the address in multiline
Hello, I’m trying to display in my app the full address of an MKMapItem in a single line. I notice the following function does not always return single line but contains newlines. https://developer.apple.com/documentation/mapkit/mkaddressrepresentations/fulladdress(includingregion:singleline:) I provide the list of some identifiers so you can check what’s wrong. "I39866265D4A8562A", // 🟢 works "IF233A1E949A5566C", // 🟢 works "ICA31B6B98E02A528", // 🔴 does not work "ICA31B6B98E02A528", // 🔴 does not work "I9E00A04BFCB9718D", // 🔴 does not work "IFACDC4BC25712413", // 🔴 does not work "I74135A4F7C7FE654", // 🔴 does not work "IFE4A3BC4FEFA53E0", // 🔴 does not work You can check this FB25681688 Thank you, Regards, Axel
0
0
8
1h
Three rejections in a week for errors on the reviewer’s iPad, and a reviewer who couldn’t find the subscription the notes describe
I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.
5
0
208
1h
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
0
0
73
11h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
1
0
67
12h
Asked to resubmit after being offered bug fix approval, now 7 days in "Waiting for Review" with no response
Hello, We'd appreciate help from the App Review team with our app update. App: AI Video Generator - Bunsy (Apple ID 6762499422) Version: 1.0.13 (build 350) Submission ID: 644c0463-bcb1-44c5-a0bb-b91ccf1860c2 Timeline: Nov 4: submitted version 1.0.13. Nov 12: App Review identified a Guideline 4 issue (Sign in with Apple logo artwork) under Bug Fix Submissions. The message said the issue could be resolved in our next update, and that if we replied, the submission could be approved without resubmitting. Nov 12: we replied the same day and asked to approve the submission as a bug fix, committing to address the issue in the next update. Nov 13: App Review asked us to resubmit anyway. Nov 14: we resubmitted with build 350, which already includes the fix (native Sign in with Apple button). It has been in "Waiting for Review" since then. Nov 16: we requested an expedited review. Nov 19: we contacted App Review about the status (Case ID 103018616391) and have received only the automated confirmation. We followed every instruction we received, and this version has now been waiting for 17 days in total. It fixes a crash on first launch that affects users of the current version. Could you please check whether anything is holding this submission or whether anything else is needed from us? Thank you.
1
0
153
14h
First app stuck in "Waiting for Review" since Nov 13, after Guideline 2.1 info response
Hello App Review team, My first app, Rental Records, has been in "Waiting for Review" since November 13, 2026, and I'd appreciate it if someone could check whether it needs any action from me. App: Rental Records (iOS 1.0) Apple ID: 6832051224 Platform: iOS, Organization account Timeline: Nov 7: First submission Nov 8: Rejected under Guideline 2.1 (Information Needed) Nov 13: I added everything requested to the App Review Notes (app description, demo logins for both account types, list of external services, regional statement, and a screen recording) and resubmitted. Status has been "Waiting for Review" ever since. What I have already done: Submitted an Expedited App Review request days ago Called Developer Support twice and was told there is no fixed timeline Sent an App Review status inquiry (Case ID: [30000019474998]) The demo accounts work and the notes are complete. I'm happy to provide anything else you need. Thank you for your time.
1
0
143
14h
Concern Regarding App Review Timeline After Months of Organization Enrollment Delays – Fixit Employee Portal
Hello Apple Developer Community, I am reaching out to seek guidance and express our concern regarding our iOS application, Fixit Employee Portal, which is currently showing "Waiting for Review" in App Store Connect. Application Details: • App Name: Fixit Employee Portal • App Apple ID: 6834282511 • Version: 1.0.4 (Build 2) • Submission Date: November 13, 2026 • Current Status: Waiting for Review Before reaching this stage, our company had already spent several months completing the verification and approval process for our Apple Developer Program organization enrollment. We appreciate Apple's commitment to security, compliance, and quality throughout the enrollment and application review processes. However, after experiencing such an extended enrollment process, we are concerned about the possibility of further significant delays before our application becomes available to our employees. Our application is intended to provide essential employee services to our manpower workforce, including access to employment-related information and company resources. Many of our employees are awaiting its availability on iOS, and timely deployment is important to our daily operations. While we understand that our application was only recently submitted for review, we would sincerely appreciate clarification on the following: Is the current waiting period normal for a newly submitted application under a recently approved organization account? After several months of organization enrollment delays, should we anticipate another extended waiting period for the application review process? Is there a way to confirm that our application has no outstanding requirements that could delay its review? Given our employees' operational need for this application, would an expedited review request be appropriate? We are not requesting that Apple bypass its standard review requirements. We simply hope to understand the expected process and avoid further unnecessary delays after the lengthy organization enrollment experience. We sincerely appreciate the efforts of the Apple Developer and App Review teams and would be grateful for any guidance or assistance. Thank you for your understanding and support. Best regards, Fixit Development Team
2
0
131
14h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
1
0
145
14h
Organization enrollment pending for 24 days – no response from Developer Support
Hello Apple Developer Support Team, I submitted an Apple Developer Program organization enrollment on October 29, 2026. Our organization has a valid D-U-N-S number, but our enrollment remains stuck at "Your enrollment is being processed." I have already submitted two support requests and received no substantive response. The phone/callback option is not available in my region. We have not yet been able to proceed to payment, and our iOS app launch is blocked. Could someone from Apple Developer Support please help us establish the status of our existing enrollment and confirm whether any further verification is required? Enrollment ID: 6PBPK975D8 Thank you.
Replies
0
Boosts
0
Views
13
Activity
32m
Waiting for Review since Monday, Nov 16. Our expedited review request was accepted on Nov 16 as well. Need review by Nov 24, 2026 to meet critical release deadline of Nov 30, 2026.
Hi, Our app has been in the Waiting for Review state, with an accepted expedited review request, since last Monday, Nov 16, 2026. Request: If it is at all possible, could our app get reviewed in time for our release deadline of Monday, Nov 30, 2026? If reasonable, a review result by Tuesday, Nov 24, 2026 would leave us time to fix anything you flag and re-submit for review. Reason: Monday, Nov 30, 2026 is our studio’s fiscal year-end. The game has to be live by then to be included in this year’s Ontario Interactive Digital Media Tax Credit claim, which is administered by Ontario Creates, an agency of the Ontario government. Missing the date by even one day pushes that funding back a full year, which is very hard on a studio our size. We can send documentation if that helps. The expedited request we made through Developer Support had no place for an explanation, so I want to make sure the reason and the date reach the review team. I know this is a big ask during a busy period, and I’m grateful for any help you can give. Thank you, William App Apple ID: 6832757024 Version / build: 1.0.0 Submitted: Nov 16, 2026 Original Expedite Request Date: Nov 16, 2026 Requested Latest Review Date: Nov 24, 2026
Replies
0
Boosts
0
Views
4
Activity
33m
Account-wide TestFlight build expiration issue — Feedback ID: FB25656884
@DTS Engineer (Albert), I am experiencing the exact same issue across all 3 apps on our team account (TJ9KJ6WV99). Every newly uploaded, validated build (Binary State: Validated, beta-reports-active: true) automatically changes status to Expired within 30–60 minutes of upload and disappears from TestFlight, despite all agreements (Paid Apps, Free Apps), Tax Forms, and DSA Compliance being verified Active (since account reactivation on Oct 29, 2026). Apple Support performed a backend process restart 48 hours ago which temporarily resolved the issue, but all new builds reverted to Expired again today within an hour (matching the BETA_CONTRACT_MISSING / backend state desync reported earlier in this thread). Feedback Assistant Ticket: FB25656884 (includes Team ID TJ9KJ6WV99 and all 3 numeric App IDs). Thanks in advance for routing this to the TestFlight / App Store Connect team!
Replies
1
Boosts
0
Views
96
Activity
33m
macOS: supported absolute deadline at final network egress, including queued bytes?
Hi, I’m assessing feasibility before implementing a small macOS HTTPS snapshot client. The requirement is strict: every request-bearing byte must cross the final controlled network-egress boundary before an absolute deadline. A byte crossing at or after the deadline fails. For context, the intended deadline is 07:41:00 Europe/London on a specified date, converted to UTC. This concerns request transmission, not response completion. An application precheck or a deadline to begin sending would not satisfy it. Is there a supported macOS API or mechanism with a documented guarantee covering this requirement? Specifically: Where is the enforcement boundary? Does expiry cover request bytes already queued in TLS/TCP, kernel, driver or NIC buffers, partially transmitted requests, and retransmitted request payload? Does enforcement remain fail-closed if the client or enforcement process is suspended, hangs or crashes, or the Mac sleeps and wakes? Can queued bytes resume transmission after expiry? What clock and deadline semantics apply, including equality, uncertainty, clock steps/regression and unavailable or unreliable time? Can connection reuse or buffering bypass expiry? Application retries, redirects and additional requests would be prohibited. How could an implementation observe and qualify the actual controlled egress boundary, rather than an earlier callback or queue? I have reviewed documentation for: NWConnection.ContentContext.expirationMilliseconds, which describes expiry for beginning transmission; NWConnection.SendCompletion.contentProcessed; Network Extension packet filtering, delayed-packet verdicts and provider lifecycle; TN3134 and TN3165. I have not found a documented end-to-end guarantee covering the cases above. I am not assuming that filters, cancellation, timers or socket timeouts provide it. Could an Apple engineer point to the applicable supported contract and platform restrictions, or clarify that this strict guarantee is not provided? If a mechanism is applicable, please identify supported macOS versions, required entitlements and any relevant interface or hardware limitations. This is a documentation/feasibility question only. No external service, account, credentials or capture is involved. An authoritative reference—or an explicit statement of unsupported cases—would be helpful. Many thanks in advance.
Replies
0
Boosts
0
Views
3
Activity
34m
iPhone Duo: Dual-display output and tent mode detection
I’m developing Foma, a design app with a full-screen gallery, and have two questions about iPhone Duo: In tent mode, can a third-party app show its gallery on the outer display while presenting noninteractive content on the inner display, without an active camera session? I tried ExternalNonInteractiveAccessory on a physical iPhone Duo running iOS 27.3 beta, but the inner display stayed dark. Is there a public API that detects tent mode directly? If not, does Apple recommend combining hinge angle with device orientation or gravity? Thanks!
Replies
0
Boosts
0
Views
3
Activity
35m
Unable to renew Apple Developer Program membership — no response to support case 30000011940191
Hello, I’m unable to renew my Apple Developer Program membership. My membership expires on November 26, 2026. I opened a support case with Apple Developer Support on November 11, 2026, case ID 30000011940191, but I haven’t received any response yet. I’m very worried that my membership will expire before this is resolved and my apps will become unavailable on the App Store. Could someone from Apple Developer Support please look into my case and get back to me? I would be very grateful for any help. Thank you
Replies
2
Boosts
0
Views
92
Activity
35m
Review submission stuck in "Canceling" for 12 days: version locked, can't cancel or resubmit
Our iOS review submission has been stuck in CANCELING since 10 Nov 2026. Every action on it is refused, so we haven't been able to ship an update for 12 days. App ID: 6809173786 Stuck submission: 0c25955e-e5d8-4835-8605-79f8115c9992 Developer Support cases: 103018649498, 103018648320 App Review case: 30000012887740 The submission has 4 items, all still "Ready for Review": iOS App 1.0.14 (app version) Lifetime-Flybud (our first non-consumable IAP) retention-3840x2160.png (Asset Library image) Flybud_Orbit_Header_3840x164… (Asset Library video) What the App Store Connect API returns (22 Nov): Cancel the submission: "Resource state is invalid – Resource cannot be canceled at the moment, please try again later." Remove an item: "Resource state is invalid – Item was already submitted." Add 1.0.14 to a new submission: "Asset Library validation error – Asset is locked by a standalone review submission." Submit the IAP on its own: "The first Non-Consumable In-App Purchase for this app must be submitted for review at the same time that you submit an app version." The version is locked by the stuck submission, and the IAP can only ship with a version, so everything is blocked. New builds upload and process normally. Given error 3, I suspect the Asset Library items are what's preventing the cancellation from completing. Since 10 Nov I've written to App Review four times, opened two Developer Support cases, filed a bug report and emailed the App Store team. Phone support has been unavailable, and App Review can't see the submission in their queue. Could someone at Apple escalate this to App Store Connect engineering to clear or complete the cancellation? Thank you.
Replies
0
Boosts
0
Views
3
Activity
36m
First app Waiting for Review since 1 Nov, support case has no reply
Our first app, PerCent: Personal Finance (Apple ID 6826506651), has been Waiting for Review since 1 Nov 2026 (submission 52e16f91-b3f5-4bfd-bdb5-babb9706518c). We requested an expedited review on 3 Nov and opened Developer Support case 30000005014098 on 4 Nov. We have received no reply, and there are no messages in App Store Connect. Could someone from Apple please check whether this submission is stuck or whether anything is needed from us? Thank you.
Replies
4
Boosts
0
Views
110
Activity
36m
Can an XPC receiver verify that App Sandbox is active for the sender?
We are designing a macOS launcher that waits for a one-use reply before starting a child process. Two instances of the same signed launcher may be running. Before replying, the receiving service needs to verify that App Sandbox is active in the specific process instance that sent the request. We can check the sender’s signed App Sandbox entitlement. Is there a supported public API or documented procedure that also lets the receiver verify the sender’s active runtime sandbox? If so, what evidence ties that observation to the sender of this XPC message, including if the sender exits and its PID is reused? Please identify the documentation and applicable macOS versions. If the supported check establishes only the signed entitlement, confirmation of that limit would also help.
Replies
0
Boosts
0
Views
8
Activity
37m
TestFlight dead on new accounts (Oct-Nov 2026): no invite emails, Beta App Review 422 "Please try again later". Collecting all cases here
This thread collects every account with the fault below in one place, so Apple sees one issue across many accounts instead of many lonely threads. If you have it, please reply. What to include is at the end. The fault Builds upload and process fine. Then two things never work: No TestFlight invite email is ever sent. Every tester, internal or external, stays "Invited". Reinvite does nothing: POST /iris/v1/betaTesterInvitations returns 201 Created and no email arrives, not in spam either. A build cannot be submitted for Beta App Review. "There was an error processing your request. Please try again later." POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE with only that sentence and no further reason. So internal testing is blocked by the missing emails and external testing by the refused review. Agreements, tax, banking and DSA are Active, Test Information and export compliance are complete, and nothing a developer can change makes a difference. The accounts reporting it are mostly new, enrolled around October 2026. My case Account enrolled 31 October 2026. Fault since 5 November 2026, every day. Region: Türkiye. No invite email reaches any of my six testers. Beta App Review submit returns the 422 every time. On 13 November I reset everything to rule out my side: removed every tester and both groups, expired the old builds, uploaded a fresh build, added everyone again. Nothing changed. The fresh build is VALID. Its internal state is IN_BETA_TESTING with "automatically notify testers" on, yet its record says the testers were not notified. Its external state is READY_FOR_BETA_SUBMISSION and the submit is refused. Feedback Assistant: FB25540791 (two HAR logs). Developer Support cases 30000005155573 and 30000005989992: only automatic receipts since 4 November, no human reply. Phone support shows as unavailable. Others reporting it https://developer.apple.com/forums/thread/856330 (@Hopeforge): internal invite emails never delivered, testers stay "Invited". Recreating groups, resending and new builds did not help. An App Store Connect Engineer replied there and asked for Feedback Assistant tickets with HAR logs. https://developer.apple.com/forums/thread/857012 (@Kirnuvirsta): tester stuck on "Invited" with no email, Beta App Review submit fails, same on a second app record. FB25399719, case open since 28 October. https://developer.apple.com/forums/thread/856896 (@medlzd, @ganderbite): new internal testers show "Invited" and never get the email, Resend Invite does nothing, on all apps. https://developer.apple.com/forums/thread/856592 (@EmlakBaseDev): Beta App Review submit returns 422 "Please try again later" on three apps since 24 October, build VALID and READY_FOR_BETA_SUBMISSION. https://developer.apple.com/forums/thread/854803 (@SefaAygun, @JanuaryTwelfth): adding a build to external testing fails with "try again later". https://developer.apple.com/forums/thread/854106 (@BWGTrading): new organization account, TestFlight stopped working for all apps on 27 October. If you have this too, please reply with When your account was enrolled, and since when the fault shows Which of the two you have: no invite emails, 422 on Beta App Review, or both Your country or region, to see whether it is tied to one Your Feedback Assistant number (FB...) and Developer Support case ID Anything Apple told you, and above all whether it got fixed, and how If you have not filed a Feedback Assistant ticket yet, please do: steps, a HAR log of the failing request, your App ID. The engineer in thread 856330 asked for exactly that. To Apple Could someone from the App Store Connect or TestFlight team tell us whether this is a known fault in how TestFlight is set up for newly enrolled accounts, and whether each account needs a change on your side? We are paying members who cannot use TestFlight at all, and our support cases stay unanswered for weeks. Thank you.
Replies
18
Boosts
8
Views
830
Activity
37m
Is viewController in authenticateHandler always nil now?
I set an empty handler that never presents the view controller: GKLocalPlayer.local.authenticateHandler = { _, _ in }When the player isn't signed in, the Game Center sign-in sheet still appears, apparently presented by a separate system process rather than through the viewController parameter. Is viewController now effectively always nil, with sign-in fully owned by the system? Or should apps still handle a non-nil view controller, as the current documentation describes?
Replies
0
Boosts
0
Views
13
Activity
1h
MKMapItem addressRepresentations fullAddress singleLine does not always work and provides the address in multiline
Hello, I’m trying to display in my app the full address of an MKMapItem in a single line. I notice the following function does not always return single line but contains newlines. https://developer.apple.com/documentation/mapkit/mkaddressrepresentations/fulladdress(includingregion:singleline:) I provide the list of some identifiers so you can check what’s wrong. "I39866265D4A8562A", // 🟢 works "IF233A1E949A5566C", // 🟢 works "ICA31B6B98E02A528", // 🔴 does not work "ICA31B6B98E02A528", // 🔴 does not work "I9E00A04BFCB9718D", // 🔴 does not work "IFACDC4BC25712413", // 🔴 does not work "I74135A4F7C7FE654", // 🔴 does not work "IFE4A3BC4FEFA53E0", // 🔴 does not work You can check this FB25681688 Thank you, Regards, Axel
Replies
0
Boosts
0
Views
8
Activity
1h
Three rejections in a week for errors on the reviewer’s iPad, and a reviewer who couldn’t find the subscription the notes describe
I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing. Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView. What has happened: 30 Oct: submitted. 3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day. 5 Nov: rejected on three points: 5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then; 2.1(b): the reviewer couldn’t find the In-App Purchase; 2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27. We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track. 8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests. So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours. The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved. Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things: When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting? Could every issue be raised in one review, rather than a new one appearing after each fix? Could reviewers read the review notes? For us they answered the question the rejection asked. Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it. The quality of the testing effort has been pretty poor. Thank you.
Replies
5
Boosts
0
Views
208
Activity
1h
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
Replies
0
Boosts
0
Views
73
Activity
11h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
Replies
1
Boosts
0
Views
67
Activity
12h
Recursive Intelligence
post quantum cryptography primer https://nicholaskouns-create.github.io/e47-casimir-filter/unified-pqc.html
Topic: Design SubTopic: General
Replies
0
Boosts
0
Views
75
Activity
14h
Asked to resubmit after being offered bug fix approval, now 7 days in "Waiting for Review" with no response
Hello, We'd appreciate help from the App Review team with our app update. App: AI Video Generator - Bunsy (Apple ID 6762499422) Version: 1.0.13 (build 350) Submission ID: 644c0463-bcb1-44c5-a0bb-b91ccf1860c2 Timeline: Nov 4: submitted version 1.0.13. Nov 12: App Review identified a Guideline 4 issue (Sign in with Apple logo artwork) under Bug Fix Submissions. The message said the issue could be resolved in our next update, and that if we replied, the submission could be approved without resubmitting. Nov 12: we replied the same day and asked to approve the submission as a bug fix, committing to address the issue in the next update. Nov 13: App Review asked us to resubmit anyway. Nov 14: we resubmitted with build 350, which already includes the fix (native Sign in with Apple button). It has been in "Waiting for Review" since then. Nov 16: we requested an expedited review. Nov 19: we contacted App Review about the status (Case ID 103018616391) and have received only the automated confirmation. We followed every instruction we received, and this version has now been waiting for 17 days in total. It fixes a crash on first launch that affects users of the current version. Could you please check whether anything is holding this submission or whether anything else is needed from us? Thank you.
Replies
1
Boosts
0
Views
153
Activity
14h
First app stuck in "Waiting for Review" since Nov 13, after Guideline 2.1 info response
Hello App Review team, My first app, Rental Records, has been in "Waiting for Review" since November 13, 2026, and I'd appreciate it if someone could check whether it needs any action from me. App: Rental Records (iOS 1.0) Apple ID: 6832051224 Platform: iOS, Organization account Timeline: Nov 7: First submission Nov 8: Rejected under Guideline 2.1 (Information Needed) Nov 13: I added everything requested to the App Review Notes (app description, demo logins for both account types, list of external services, regional statement, and a screen recording) and resubmitted. Status has been "Waiting for Review" ever since. What I have already done: Submitted an Expedited App Review request days ago Called Developer Support twice and was told there is no fixed timeline Sent an App Review status inquiry (Case ID: [30000019474998]) The demo accounts work and the notes are complete. I'm happy to provide anything else you need. Thank you for your time.
Replies
1
Boosts
0
Views
143
Activity
14h
Concern Regarding App Review Timeline After Months of Organization Enrollment Delays – Fixit Employee Portal
Hello Apple Developer Community, I am reaching out to seek guidance and express our concern regarding our iOS application, Fixit Employee Portal, which is currently showing "Waiting for Review" in App Store Connect. Application Details: • App Name: Fixit Employee Portal • App Apple ID: 6834282511 • Version: 1.0.4 (Build 2) • Submission Date: November 13, 2026 • Current Status: Waiting for Review Before reaching this stage, our company had already spent several months completing the verification and approval process for our Apple Developer Program organization enrollment. We appreciate Apple's commitment to security, compliance, and quality throughout the enrollment and application review processes. However, after experiencing such an extended enrollment process, we are concerned about the possibility of further significant delays before our application becomes available to our employees. Our application is intended to provide essential employee services to our manpower workforce, including access to employment-related information and company resources. Many of our employees are awaiting its availability on iOS, and timely deployment is important to our daily operations. While we understand that our application was only recently submitted for review, we would sincerely appreciate clarification on the following: Is the current waiting period normal for a newly submitted application under a recently approved organization account? After several months of organization enrollment delays, should we anticipate another extended waiting period for the application review process? Is there a way to confirm that our application has no outstanding requirements that could delay its review? Given our employees' operational need for this application, would an expedited review request be appropriate? We are not requesting that Apple bypass its standard review requirements. We simply hope to understand the expected process and avoid further unnecessary delays after the lengthy organization enrollment experience. We sincerely appreciate the efforts of the Apple Developer and App Review teams and would be grateful for any guidance or assistance. Thank you for your understanding and support. Best regards, Fixit Development Team
Replies
2
Boosts
0
Views
131
Activity
14h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
Replies
1
Boosts
0
Views
145
Activity
14h