App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

Hi, We are seeing Apple-hosted Managed Background Assets download failures on macOS 26.6.1 and would appreciate confirmation of whether this is a known issue or a configuration problem. Environment macOS app using Apple-hosted Managed Background Assets Apple Silicon Macs: M1 and M4 App version: 1.0.2 (build 10) App and downloader extension are sandboxed and use the same App Group No ba-serve development URL override is configured: xcrun ba-serve url-override reports that no override is set. Observations On the same M1 Mac: On macOS 26.5.2, Background Assets began transferring an asset pack successfully. The log recorded 136,586,876 bytes received before I manually cancelled the download. After upgrading to macOS 26.6.1, Background Assets reaches manifest resolution and download scheduling, but the asset transfer fails. The macOS 26.6.1 logs show: NSURLErrorDomain -1200 The certificate for this server is invalid / secure connection failed kCFStreamErrorDomainSSL -9816 server closed session with no notification NSURLErrorDomain -3007 Download decoding failed A separate M4 Mac running macOS 26.6.1 also reproduces the issue. One relevant variable: both the working 26.5.2 log and the failing 26.6.1 log show the Background Assets traffic passing through a local HTTP/S proxy at 127.0.0.1:6152. I am now testing a direct route for odr.itunes.apple.com and amp-api.apps.apple.com, but this proxy path was also present in the 26.5.2 transfer that started successfully. The asset pack IDs in the two captured logs are not identical, so this is not a strict same-pack A/B comparison. However, the failure is reproducible for Apple-hosted packs on 26.6.1, while the pre-upgrade log shows a real transfer on the same M1 Mac. Has anyone seen either of these on macOS 26.6 / 26.6.1? NSURLErrorDomain -3007 (Download decoding failed) for Apple-hosted Background Assets TLS error -1200 / kCFStreamErrorDomainSSL -9816 during a Background Assets pack transfer A change in support or behavior for HTTP/S proxy routing of Apple-hosted asset-pack downloads I have filed Feedback Assistant report FB24301118 with the relevant logs and diagnostic attachment. Thanks.

Hello, We're evaluating Apple-hosted Background Assets for an app distributed on the public App Store. Is there any documentation or guidance on update latency, specifically: How quickly are asset updates propagated to devices once a new version is published? More specifically, is propagation near-immediate, or should we expect a delay (minutes/hours/days) before devices know they have to pick up the new version in the ideal condition of being connected to Wi-Fi, locked, charging and the app has been recently used? Are there any other factors other than the aforementioned ones that affect how fast an update reaches a device? Any official documentation, WWDC session, or guidance from the team would be appreciated, thanks in advance.

I'm angry — Apple’s support has been awful. I’ve been trying to get help from Apple for two weeks. Their replies feel canned and automated (they even sign with a first name only), and they only provide basic information that doesn’t address the problem. You put in a response and then a week later, some canned response comes back from someone with a single name (Lisenga) I’m now faced with two unacceptable options: stop supporting Apple Safari users or delete my account and start over. Both options punish my users. For a multi-billion-dollar company, Apple’s support is shockingly limited. I ran this issue past ChatGPT Codex, and it confirmed that this is something only Apple can fix. Recent Apple Developer Forum posts describe Xcode Cloud / App Store Connect requests returning null responses because backend team permissions were broken. One post even referenced a case where Apple confirmed the only remedy was an internal fix on their side. To be clear: I am NOT using Xcode. I’ll say it again in case it was missed: I am not using Xcode. Here’s what happens: In App Store Connect, when I click the Xcode Cloud link it prompts me to “upload archive file.” When I upload, I immediately get “Failed to Fetch.” This happens in Safari, Chrome, and Firefox, in normal and private windows. It happens on a different computer 400 miles away as well. My suspicion is this: if a build is created before agreeing to the developer agreements, and the agreements are answered afterward, the system goes out of sync and breaks — a problem that only Apple can resolve. How do you actually talk to a real human at Apple??

Hello, I am experiencing a serious TestFlight issue that began immediately after I removed some testers from an External Testing group. Right after removing those external testers, all existing TestFlight builds for my app were suddenly marked as Expired, even though they were still within the normal 90-day TestFlight validity period. I did not manually expire any build. Removing an external tester should only revoke that tester’s access and should not affect the status of any TestFlight build. After the mass expiration, I uploaded a replacement build. The new build uploaded and processed successfully in App Store Connect, but I could not add or submit it for External TestFlight Beta App Review. App Store Connect incorrectly displays the following message: Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership. However, my account currently shows: Account type: Individual — Account Holder Apple Developer Program membership: Active Apple Developer Program License Agreement: Accepted Free Apps Agreement: Active No pending Apple Developer Program agreements Replacement build uploaded and processed successfully I inspected the failed App Store Connect network request and found the actual backend error: POST /iris/v1/betaAppReviewSubmissions HTTP 422 Unprocessable Content { "errors": [ { "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] } The exact sequence was: External testers were removed from the External Testing group. All existing TestFlight builds suddenly became Expired. A replacement build uploaded and processed successfully. The build could not be submitted for External Beta App Review. The backend returned ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING. I have found reports from other developers describing the same sequence after removing external testers, including all TestFlight builds unexpectedly expiring and TestFlight distribution no longer working. This appears to be an account or team-level TestFlight backend issue in which the Beta Contract or distribution state becomes detached after modifying external testers. I have already contacted Apple Developer Support and provided the private account, app, request, and error identifiers through my support case. Could an Apple engineer please confirm whether this is a known backend issue and whether the TestFlight Beta Contract needs to be re-provisioned or re-attached? Has anyone else experienced this exact issue after removing external testers? If Apple resolved it, what action was required on the backend? Thank you.

Hi, our organization's Apple Developer Program enrollment was recently completed, but App Store Connect access has never been provisioned, and I'd appreciate help escalating this. Timeline: Organization enrollment verified and completed; "Welcome to the Apple Developer Program" email received more than 50 hours ago Membership shows as active on developer.apple.com under the correct team Apple Developer Agreement accepted; Apple Developer Program License Agreement accepted on August 11, 2026 - no pending agreements are shown on the account page I am the Account Holder, signing in with the same Apple Account that was used to enroll the organization Despite this, signing in at appstoreconnect.apple.com consistently returns: "Your Apple Account isn't enabled for App Store Connect." What I've already tried: signing out of both developer.apple.com and App Store Connect and signing back in via a private/incognito window, different browsers, and navigating to App Store Connect from the developer account page. The error is unchanged. I contacted Apple Developer Support by email (no phone option is available in my region) and am waiting on a reply - case number: 20000135517368 This looks like the known issue where App Store Connect provisioning doesn't trigger for a new organization enrollment. Could someone from Apple take a look or advise how to get the provisioning kicked off manually? Happy to provide the Team ID privately if needed.

Hello, My app submission has been waiting for review for 7 days. I've requested expedited review twice and contacted Developer Support; no response to either yet. Apple ID: 6789087223 Bundle ID: ai.spinsports.app Is there anything that can hold a submission in "Waiting for Review" before assignment that I should be checking on my end? If there's a common blocker at the pre-assignment stage, I'd rather find it myself than keep waiting. Or anything else I can do on my end? Thank you.

Hello, We are seeking guidance regarding our Apple Developer Program account, which is currently under a Pending Termination Notice related to Section 3.2(f) of the Apple Developer Program License Agreement. The notice stated that our account had repeatedly submitted apps with unresolved guideline violations and that Apple believed these submissions were attempting to evade the review process. We want to make it clear that we never intended to mislead Apple or bypass the review process. We understand the seriousness of Apple's concerns and have taken the matter very seriously. Following the notice, we submitted an appeal to the App Review Board on June 4, 2026. In our appeal, we acknowledged the issues raised, explained the circumstances that led to the repeated submissions, and committed to implementing stronger internal review and compliance procedures. We also expressed our willingness to remove the app involved if necessary to ensure full compliance with Apple's policies. We have been members of the Apple Developer Program for several years and have always aimed to build products that comply with Apple's guidelines. We value the App Store ecosystem and would like the opportunity to address any concerns and continue serving our users responsibly. We want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team or the community on the best way to confirm our materials are under active review, and on any additional steps that would help. Thank you. Thank you for your time and any guidance you can provide.

Hello, My app submission has been waiting for review for 8 days, and there has been no status update or request for additional information. Submission ID: f9cc5319-693b-4809-8bcb-5eb0e8ad28bd I understand that review times can vary, but this is considerably longer than I have experienced before. Could an Apple representative please check whether the submission is progressing normally or if any action is required from my side? Thank you.

My first app "Remote for Roku TV: RokuMote" (Apple ID 6795405234, iOS) was submitted for review on July 31, 2026. It has been in "Waiting for Review" ever since — 6+ days — and has never entered "In Review". No messages in App Store Connect, nothing in Resolution Center. What I've already done: Expedited review request on August 4 — no response. Email to App Review — no response. Developer Support case "App Review Status" on August 5 (Case ID 20000128844197) — pending. All metadata, review notes and a demo video were attached at submission. The account is new (created July 28, 2026) — if new accounts are queued differently, I'd appreciate knowing that. Is anyone from Apple able to look into this? Is there a known backlog right now for first submissions?

Hello, I submitted a request for Unlisted App Distribution about 5 days ago, but I haven’t received an approval or rejection yet. My app is a new app (Version 1.0). I submitted it to App Review and explained that it is intended for Unlisted App Distribution. The app was reviewed, but App Review rejected the submission and told me: “If you’ve already submitted your request for unlisted app distribution, then you should resubmit the app for review in App Store Connect if your request is approved.” So currently: The Unlisted App Distribution request has been pending for about 5 days. Version 1.0 was rejected while the Unlisted request is pending. App Review instructed me to resubmit once the Unlisted request is approved. I have not yet received any update regarding the Unlisted request. Has anyone recently gone through the same process? How long did your Unlisted App Distribution approval take? Also, is there anything I should do to follow up with Apple after waiting this long, or should I simply continue waiting for the Unlisted request decision? Thank you!

Hello, I purchased the developer account on August 6, 2026. My order number is W1738664505. It has been several days, and my account still has not been activated. I have contacted support multiple times, but I keep receiving strange and seemingly automated responses that do not address my issue. I paid for this account, and I have been trying for days to get it activated, but I still have not received a clear response or been able to communicate with someone who can actually help me. The payment was processed without any issue, but now I cannot get a proper response regarding the account I purchased. Please, can someone take a look at my order and tell me what is happening? Who can help me get my purchased account activated? I would appreciate a clear and direct response as soon as possible. Thank you.

Hello, Our StoneEx iOS app (Apple ID 6782465590) was submitted for App Review on August 2, 2026 and has remained in “Waiting for Review” for almost two weeks without any change in status. We have contacted Apple Developer Support multiple times. Our existing support case is: Case ID: 20000133276837 So far, we have received only confirmations that our requests were received, but no substantive response or status update. We have also made repeated attempts to contact Developer Support by phone, including extended hold times, without reaching a specialist. There are no messages in Resolution Center, and we have not received any request for additional information or indication that something is missing from the submission. Could someone from Apple please check whether this submission or support case is stuck and, if appropriate, escalate Case ID 20000133276837 to the relevant App Review or Developer Support team? App: StoneEx Platform: iOS Apple ID: 6782465590 Submitted: August 2, 2026 Current status: Waiting for Review Support Case ID: 20000133276837 Thank you.

Hello, My app Jewel Coloring Go! (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on July 31, 2026. However, today is Auguse 9, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.

Hello, I have a single app record where the macOS platform completed review promptly and the iOS platform has been In Review for nine days. Both were submitted at the same time. App name: ProjectKiller Apple ID: 6796546956 Platforms: macOS and iOS, same app record Timeline: Aug 5, 12:22 AM — macOS 1.0 submitted (7 items). Review Completed. Aug 5, 12:22 AM — iOS 1.0 submitted (1 item). Status: In Review, unchanged since. Aug 14 — still In Review, 9 days. There is an earlier iOS submission from Aug 4 showing as Removed. I developer-rejected that one and resubmitted the following day. There are no messages in Resolution Center, no rejection, and no request for information. I have contacted Developer Support twice by phone, including case ID 20000134815022 on Aug 14, and have not had a substantive update. What I am trying to establish is whether anything is required from me, or whether this submission is simply sitting in the queue. The macOS approval on the same code base and the same metadata suggests the build itself is not the issue, but I would rather be told I have something to fix than keep waiting on a queue. I am not requesting expedited review. Any guidance appreciated. Thank you.

My first App Store submission has been in "Waiting for Review" since August 6, 2026 and has not yet moved to "In Review." App: Rotation Pool Scorer Apple ID: 6780028774 Bundle ID: com.michaelmanuele.arscorer Platform: iOS (initial release, not an update) Version / build: 1.0.0 (30) Submitted: August 6, 2026 at 11:04 AM EDT Submission ID: 56d82316-f8f5-4125-b025-5c8f0bef41b2 Items in submission: iOS App 1.0.0 (30) and one non-consumable in-app purchase, both showing "Waiting for Review" Support case: 20000135569120 (emailed August 12, 2026; no reply yet) I understand review times vary and that Apple's published figures are averages rather than commitments. I have confirmed the following on my end before posting: No messages in Resolution Center, and no email from App Review. Paid Applications and Free Applications agreements both Active, and both predate the submission date. Banking, tax (U.S. Form W-9) and Digital Services Act information all Active and complete. App Review Information is filled in, including notes covering the in-app purchase. The app requires no account or login, so no demo credentials apply. Nothing else from this account is submitted or blocking. I have not requested an expedited review, as I do not believe this situation meets the stated criteria, and I have not removed the submission from review. Is there anything further needed from me, or is this simply queue time? Any confirmation of the submission's status would be appreciated.

Hello Apple Developer Community, I’m looking for guidance regarding an unusually long App Review process for my first iOS app, Zivoo. The overall review and resubmission process has now been ongoing for more than a month. During the previous reviews, we received feedback from App Review. In response, the application was completely redesigned and the latest version contains a substantially revised core experience. The latest build is: App: Zivoo Platform: iOS Version: 2.1.4 (34) Submitted: August 10, 2026 Current status: Waiting for Review The App Store description, screenshots, metadata, and Review Notes have also been fully updated to reflect the redesigned application. Detailed testing instructions have been provided for App Review. After more than a month of working through the review process, responding to feedback, redesigning the application, and preparing a new submission, the latest build is still waiting for review without any visible progress. I have also contacted App Review Status support to confirm whether any additional action is required from our side. Could someone from Apple please check whether this submission is progressing normally or whether it may require additional attention? I would also appreciate hearing from other developers who have experienced a similar delay after substantially redesigning an application following App Review feedback. Thank you for any guidance or assistance.

Estou com problemas para inserir um compilador a um grupo de tester externo. Ela da um erro que tenho que renovar mas não esta vencido. Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership.

I'm stuck on what looks like a backend / account-level TestFlight issue and want to ask if anyone has seen the same pattern. Symptoms (reproduced across three consecutive builds) App Store Connect ingests and processes each build successfully; it shows as "Testing" in TestFlight with no compliance warnings. Internal TestFlight install fails instantly on every tester device with: ▎ "The requested app is not available or does not exist." Device console (itunesstored) at install time: FAILED: TFBundleInstallation serverFailureReason="Error Downloading Install Data" userFailureReason="Requested app not available or does not exist" buildGroup=(null) phase=Failed previousPhaseDescription=ProcessingInstallInitiateResponse serverCode 200 Submitting the same build for external Beta App Review returns: 422 ENTITY_UNPROCESSABLE code: BETA_CONTRACT_MISSING buildGroup=(null) for builds that visibly show as "Testing", plus a persistent BETA_CONTRACT_MISSING, suggests the beta-contract / build-group record for the app is missing or corrupted on the backend. Already verified clean on the developer side Distribution certificate and provisioning profile valid; entitlements match the binary; codesign --verify --deep --strict passes. Free and Paid Apps Agreements both Active; no pending tasks (Banking, Tax complete). App Information, Pricing & Availability, Age Rating, Content Rights, Test Information all complete; build page shows no warnings. Reproduced with multiple testers on multiple iOS 17+ devices, in a fresh internal testing group, after device-side cleanup (sign-out / reinstall TestFlight). Re-uploading a fresh build does not clear it — so it is not bound to a specific binary. Questions Has anyone seen Error Downloading Install Data + buildGroup=(null) + BETA_CONTRACT_MISSING together on a single app? How did you resolve it? 2. Why does ProcessingInstallInitiateResponse return serverCode 200 while still failing with "app not available", for a build that shows as "Testing"? 3. Is there a documented path to request that engineering regenerate a corrupted beta-contract / build-group record, beyond a standard support case? Any pointers appreciated — happy to share device logs / sysdiagnose if useful.

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.