To the Apple Review and Developer Support Teams, I am writing to request guidance and assistance regarding a persistent rejection my React Native application is facing under Guideline 2.1 - Performance (In-App Purchases). My app has been rejected multiple times with the following specific note: "The In-App Purchase products in the app still exhibited one or more bugs which create a poor user experience. Specifically, the subscription screen failed to load any subscription plans. Review the details and resources below to troubleshoot this issue." The screenshot provided by the review team shows a completely black screen where our paywall options are intended to populate, indicating that the product array is returning completely empty during the review process. The Dilemma: We are completely unable to reproduce this behavior on our end. Everything functions flawlessly within our TestFlight builds across multiple physical test devices and various sandbox tester accounts. On TestFlight, the paywall renders instantly, local pricing fetches immediately via SKProductsRequest, and test transactions process without a single error. Our Current Implementation & Verification: Product Status: All subscription products are explicitly marked as "Waiting for Review" in App Store Connect with one In-App product Rejected for not being attached with a bin but I've since submitted the app once again. All the subscriptions and the in-app product have been actively attached to this specific app submission version. Agreements: The Paid Apps Agreement is active, signed, and fully up to date within our Agreements, Tax, and Banking configurations. Identifiers: We have strictly verified that the hardcoded product identifiers in our React Native codebase match the App Store Connect product IDs exactly. Because this error only occurs within the App Review environment and never in TestFlight or local sandboxes, we are at a loss for how to debug or resolve this issue. Could the App Review team or the Developer Support technical team please clarify if there is a known environment mismatch, storefront routing discrepancy, or specific network configuration (such as IPv6 handling in the review sandbox) that would cause production-ready StoreKit products to return an empty array exclusively to the reviewer? Any direct guidance, logs, or steps on how we can successfully surface our plans to your review team would be deeply appreciated. Review Environment Submission ID: 5a35279c-1621-4972-b6c6-7c1fb202b2f0 Review date: May 20, 2026 Review Device: iPad Air 11-inch (M3) Version reviewed: 1.0.2 (8) Thank you for your time and assistance.

Hi friends, Since yesterday, I'm not able to download any of my apps from TestFlight (while I can for others developers). I'm searching since 2 days now about the reason and I think I've tried everything, so I'm asking if you might have an idea... It occured after adding subscriptions to one of my apps, then I did all of these: Check all contracts on my apple developer account Verify my apple ID in internal testers Install / Uninstall TestFlight app Remove / Re-add myself as tester Try new builds My apps are listed on the Apple Store and not removed from Sales. Did I miss something? The error is mysterious... I also contacted Apple, I'm waiting for their answer. Thank you 🙏

Hello, My Apple ID 6766831703 My case ID102894773917 I have sent an email to Apple support to report that my app cannot be installed in TestFlight for 4 days. The app build has been successfully uploaded and processed in App Store Connect. The build status currently shows "Ready to Submit" ‘Testing’. I have uploaded 2 versions, 0.1.0 0.1.1, but both show this requested app isn't available or doesn't exist. I have tried to click stop testing, re-invited tester, re-download TestFlight app, and check all agreements, All export compliance questionnaires have been completed. There is no problem. The developer account has also been registered recently. Because the inability to test has seriously delayed our project timeline and business launch in Global. Could Apple team escalate this case for me right now please?

Adding application ID to .pkg file seemed to work Original My modified version I created a .pkg file which installed to Applications folder and the app worked fine, but when I uploaded the app with transporter I got the message 'executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true'

Hello, I’m experiencing the same issue described in other threads: all TestFlight actions fail with ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING, while production uploads work normally. There are no pending agreements in App Store Connect. I already contacted Apple Support (case ID: 20000112300245). They told me it would resolve within 48 hours, but it hasn’t. The TestFlight Beta contract appears to be missing or detached on Apple’s backend. Is there any way to have it manually reattached or reprovisioned? This is blocking my app submission — any help would be greatly appreciated. Thank you.

We’re unable to add external testing groups to our new builds for our app, Nox AI Wingman (https://apps.apple.com/in/app/nox-ai-wingman/id6753078092), because we keep facing a persistent, unexplained error. Some details: 3 calls + email updates with the team so far, we received no explanation other than directions to wait 48 hours and try again. We’re still unable to submit builds, with no word of any escalation or explanation for where the problem’s coming from. All agreements are signed, the build says “Ready to Submit”, all privacy related and other necessary fields have been filled out properly Browser Console shows the following error on submission: "errors" : [ { "id" : "112b2d19-6105-45c3-b941-3217d905fafc", "status" : "400", "code" : "PARAMETER_ERROR.REQUIRED", "title" : "A required parameter was not provided", "detail" : "The parameter 'filter[build]' is required but was not provided", "source" : { "parameter" : "filter[build]" } } ] } Direct beta review submission gives us the following API error from apple: { "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } We're helpless. Dev support has no idea what's causing this or how we can prevent this in the future even if they do fix it. We’re in the middle of a crucial launch week, and cannot afford 48 hour windows with no response or communication. Any help at all would be clutch.

Hello, I'm having trouble installing my app via TestFlight. Current Status: The app build has been successfully uploaded and processed in App Store Connect. The build status currently shows "Ready to Submit" All export compliance questionnaires have been completed. The Issue: Even though everything looks ready on the dashboard, I cannot install the app on my phone via TestFlight. • (Specifically, the app is visible but throws an error when I click install-‘this app doesn’t exist or not available’). What I've Tried: • Checked that the testing group is properly linked to the build. • Re-signed into the TestFlight app on my device. Could App Store Connect Team Adviser help me with this issue please as soon as possible!

Hi, My external TestFlight build has been waiting for review for over 2 days with no update or response. App details: App name: Propzo Bundle ID: com.propzo.ai Version: 1.0.0 Build 2 Developer Apple ID: eswarpropzo Submitted: May 14, 2026 I have also tried contacting Apple Developer Support via the contact form but the dropdowns are not working. Has anyone experienced this delay? Is there anything I can do to expedite the review? Thank you

I am implementing device authentication for a macOS app. Our iOS app uses App Attest, but App Attest is not available on macOS, so we are evaluating StoreKit's AppTransaction plus AppStore.deviceVerificationID as the macOS equivalent signal. The issue: in a macOS app installed through TestFlight, AppStore.deviceVerificationID is available, but AppTransaction.shared throws StoreKitError code=2. I reproduced this in a focused standalone macOS test app with no backend and no custom dependencies. Environment: Platform: macOS Distribution: TestFlight App Store Connect app ID: 6769568350 Bundle ID: com.soundcity.AppTransactionProbe App version: 1.0 Build: 1 Observed output from the TestFlight-installed app: Bundle ID: com.soundcity.AppTransactionProbe App version: 1.0 Build: 1 deviceVerificationID available: true deviceVerificationID prefix: CA91ED5D... AppTransaction.shared threw error: StoreKitError; domain=StoreKit.StoreKitError; code=2 The relevant code path is essentially: import StoreKit let deviceVerificationID = try? AppStore.deviceVerificationID let appTransaction = try await AppTransaction.shared In the TestFlight-installed build: AppStore.deviceVerificationID succeeds. AppTransaction.shared throws StoreKitError code=2. Questions: Is AppTransaction.shared expected to work for macOS apps distributed through TestFlight? If yes, what does StoreKitError code=2 indicate in this context, and what setup might be missing? If no, is there an Apple-supported way to obtain an AppTransaction JWS, or equivalent signed App Store/TestFlight app-install assertion, for macOS TestFlight builds? For macOS apps that need a device-bound trust signal comparable to iOS App Attest, is AppStore.deviceVerificationID intended to be used without AppTransaction.shared, or should these APIs be used together? I have a focused Xcode test project that demonstrates the issue and can share it if helpful.

Hello everyone, I've been unable to install any TestFlight build on my device for over a week. Every build shows "Complete" in App Store Connect, but installation always fails with the same error. I also submitted a support ticket to Apple Developer Support over a week ago but have not received any response. I'm posting here hoping someone from the community or Apple team can help. Error Message "The requested app is not available or doesn't exist" (Turkish: "İstenen uygulama kullanılamıyor veya yok") Environment Device: iPhone 17 Pro Max iOS: 26.4.2 App: Easyway Digital Library Bundle ID: com.abacusai.turkishsocialme.t1777823268 Build Framework: React Native (Expo SDK 54) What I've Tried (Nothing Works) ✅ Multiple builds uploaded (build 4, 5, 6, 7, 8) — all show "Complete" ✅ Deleted and reinstalled TestFlight app ✅ Signed out and back into Apple ID on device ✅ Restarted iPhone ✅ Tried different browsers (Safari, Chrome, Firefox) ✅ Tried Internal Testing — receive email but can't install ✅ Tried External Testing — same error ✅ Tried creating Public Link — same error ✅ Cleared browser cache, tried Incognito mode ✅ Verified Export Compliance (ITSAppUsesNonExemptEncryption: false) ✅ Paid Apps Agreement: Active ✅ Free Apps Agreement: Active ✅ Bank & Tax info: Complete Build Status in App Store Connect Version & Build: 1.0.1 (8) Status: Complete Date Created: May 15, 2026 Timeline May 8, 2026: First build uploaded — same error started May 10, 2026: Paid Apps Agreement activated May 15, 2026: Still the same error after 8 builds Apple Support — No Response Submitted a support ticket on approximately May 8, 2026 Category: App Store Connect & TestFlight Issue: Cannot install builds via TestFlight Status: No response received after over 1 week No case number update, no email reply Questions Has anyone experienced this with a new app on TestFlight? Is there a known issue with TestFlight and new Bundle IDs? Could this be related to the Paid Apps Agreement activation delay? Is there a way to reset the TestFlight state for a Bundle ID? How can I escalate my support ticket if there's no response? I'm completely stuck — I cannot test my app at all. Any help or guidance would be greatly appreciated. Thank you!

Hello, I'm experiencing a persistent issue with TestFlight and app reviews on App Store Connect, and I hope someone else has encountered this before. About a week ago, when trying to add external testers to test the initial TestFlight builds, I received the following error: There was an error processing your request. Please try again later. Since there were no other details, it was impossible to know the source of the problem. After doing some research, I found the root cause of the problem in the browser console; "errors" : [ { "id" : "c7300330-93d7-4aee-af8e-1aeffeff81ae", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] Since then: I've researched everything needed for TestFlight, including contracts, bank details, and so on, but I can't create external TestFlight tests. Internal TestFlight builds appear, but they can't be downloaded ("Requested application not available or present"). My applications just won't get past the review process. I've been trying to find a solution for about 10 days now. I've checked everywhere. We even checked with AI, but there's no reason. Important details: This is an individual developer account. I am the account holder. All contracts appear active and valid. This is my first and only application. I've contacted Apple Developer Support, but unfortunately, I haven't received a real solution yet, which makes it unclear how to proceed. Suggestions include checking forums, etc. Has anyone experienced this problem or found a solution? Any information would be greatly appreciated. What should I do? Please help. Thanks!

Hello juice community. firts of all, i'm brazilian dev, soo this conversation will be a lot errors of english. but i'm think is a nice to prove is not a AI generate post here. hehe I want a big tip, how i integrate my app in the fruit ecosystem. Soo, i launch a AI prompt plataform, the idea is make users your own prompt, you make a context for him, like " you are a food master chief", and configure the inputs, like a photo of your freezer, to the AI take the ingredients e make a recipe with AI. The aplication is infinite! The integration, now, is with AI provider. the idea is not make a context with complex Skills.sh, but the common user create your own Prompt/AI and feel a prompt engineer master. i'm think the is a powerful plataform for native apple system. the plataform has url, and if any one has interesting a will chat in the comments the name for see how beaut is.

Hi everyone, I'm experiencing an unusually long wait time for my TestFlight external build review and wanted to see if others are facing similar issues in 2026. Current Status: Platform: iOS App Version: 1.2.90 (Build 24) Build Type: TestFlight External Testing Current Status: In Review - not "Waiting for Review" Time in Current Status: Over 2 weeks Submission Timeline: Current Submission: Wednesday at 9:49 AM (iOS 1.2.90 Build 24) Previous Submission: March 9, 2026 at 2:20 PM (iOS 1.2.90 Build 11) - Status: Completed (Rejected) Full History: March 9, 2026 2:20 PM - Initial submission (Build 11) March 15, 2026 5:25 AM - Rejection from Apple March 24 - April 15, 2026 - Multiple back-and-forth communications (5 messages total) April 15, 2026 2:22 PM - Last response from Apple Recent (Wednesday 9:49 AM) - Resubmitted new build (Build 24) Current - Still "In Review" after 2+ weeks What I've Tried: ✅ Addressed all rejection issues from the previous review ✅ Submitted a new build with higher build number (11 → 24) ✅ Submitted expedited review request through App Store Connect ✅ Contacted Apple Developer Support via email ✅ Requested phone callback for escalation What Concerns Me: The build has been stuck in "In Review" status for over 2 weeks This is AFTER already going through a full review cycle (rejection + resubmission) Normal review times are supposed to be 24-48 hours, even with the 2026 backlog The previous review cycle took over 1 month (March 9 → April 15) This is completely blocking our beta testing program Questions for the Community: Is anyone else experiencing 2+ week "In Review" times for TestFlight external builds in 2026? Does a previous rejection cause indefinite review delays on resubmission? Has anyone successfully resolved this by canceling and submitting a brand new build? Are there effective escalation paths beyond standard support channels? Could this indicate an account-level review issue? What I Understand: Review times have increased in 2026 due to higher submission volumes Previous rejections can lead to more thorough reviews However, 2+ weeks "In Review" (not even "Waiting") seems abnormal This delay is severely impacting our development timeline and beta testing plans. Any advice or shared experiences would be greatly appreciated! Thanks in advance for your help.

Hi, I have been using Testflight iOS app to test my apps before releasing to production. Over the past few weeks, I am unable to install any of my apps through Testflight. I also don't get any email notification that my app is live on Testflight. This is really important and it would be really helpful if I can find any solution to this. Thank you so much.

Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?

Hi I uploaded the zenweb mac app for review in TestFlight and it was rejected - after that I uploaded a new version - which was reviewed and approved. Since then all version I upload (TestFlight or App Store) are displayed in TestFlight but the Distribution - App Review is displaying only the link to the first app that was rejected. I have no way of submitting to app to review before publishing. Opened a cse with apple - 102876729124 - received a response from SB - to which I answered on 30 April 2026 since then - nothing - we re keen to deploy, Safari is lagging after Chrome and Edge solution now.

"Could not install . The requested app is not available or doesn't exist." when installing app from TestFlight" I've tried uninstalling and reinstalling the app, and even removed older versions. I emailed support, but I still haven't found a solution. Does anyone know the solution to this problem?

Hi Our team is not able to install the app from testflight after April 30. Install stops with the following error The requested app is not available or doesn't exist." This is a blocker for us. Please help resolve this.

Hello everyone, We recently noticed a sudden and unexplained increase in our app's download and install sizes on App Store Connect. The jump happened literally overnight between April 2 and April 3. After auditing our commit history and running some isolation tests, it appears this increase is artificial and related to a change in App Store Connect's post-processing or size attribution logic, rather than our actual codebase. The initial observation: Build A (April 2): Download: 174 MB | Install: 380 MB Build B (April 3): Download: 179 MB | Install: 386 MB To figure out what caused the ~5 MB download and ~6 MB install jump, we looked at the diff between the two builds. We ran a local size analysis on the IPAs for both commits and the diff was just 18,287 bytes. Such a difference in the compiled binary absolutely does not account for a 5-6 MB jump in the final App Store Connect estimates. To completely rule out our code, we took the exact source tree from Build A (which originally processed at 174 MB / 380 MB) and pushed a fresh upload to App Store Connect. Re-uploaded Build A increased in size to 179 MB / 386 MB. Since re-uploading the exact same commit now results in the larger size estimates, it seems the discrepancy is not originating from our code. Has anyone else experienced a similar bump in their app sizes recently? Could an Apple engineer provide any insight into what might be causing this?

Hi everyone, We are investigating a possible iOS permission state issue after a device previously installed our app through TestFlight and later installed the production version from the App Store using the same Bundle ID. Environment: Device: iPhone 15 iOS version: 26.2.1 App distribution history: The app was previously installed through TestFlight and later installed from the App Store Permissions involved: Camera / Photos Issue: When the user opens the App Store version of the app and tries to access a feature that requires Camera or Photos permission, the iOS permission prompt does not appear as expected. Also, the app does not appear under: Settings > Privacy & Security > Camera or: Settings > Privacy & Security > Photos Because of this, the user cannot manually enable the permission. Another user on iOS was able to grant the permissions normally, so the issue appears to be isolated to the device that previously used the TestFlight build. Expected behavior: When the App Store version requests Camera or Photos permission, iOS should display the permission prompt, or the app should appear under Settings > Privacy & Security > Camera/Photos so the user can manage the permission manually. Actual behavior: The permission prompt does not appear, and the app does not appear in the corresponding privacy permission list. Possible cause: It seems like the device may be preserving or reusing a stale privacy permission state from the previous TestFlight installation, since both the TestFlight build and the App Store build use the same Bundle ID. Steps to reproduce: Install the app through TestFlight. Open the app and trigger a Camera/Photos permission request. Grant or deny the permission. Stop testing or remove the TestFlight version. Install the production version from the App Store using the same Bundle ID. Open the App Store version. Trigger the same Camera/Photos permission request flow. Go to Settings > Privacy & Security > Camera/Photos. The app does not appear, or the permission prompt does not behave as expected. Workarounds attempted or suggested: Close and reopen the app. Restart the iPhone. Delete and reinstall the app from the App Store. Stop testing the app from TestFlight. Reset Location & Privacy settings. Question: Has anyone experienced a similar issue where iOS does not show the permission prompt or does not list the app under Privacy & Security after switching from a TestFlight build to the App Store version with the same Bundle ID? Is there a recommended way to fully clear the previous TestFlight permission state, or should this be reported as a possible iOS/TestFlight permission state bug?