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.

Hello, I’m looking for some advice regarding a TestFlight Beta App Review issue. My app, MyStory, was rejected twice under Guideline 2.1(a) with the same general message: App Review was unable to successfully access all or part of the app. In the first review, Apple specifically asked us to provide a demo account with content demonstrating the app’s functionality. We followed those instructions for Build 3: • Created a dedicated demo account with sample content in all four sections. • Added the username and password under Beta App Review Information. • Added testing instructions. • Replied to App Review with the credentials and instructions. Build 3 was nevertheless rejected again under the same Guideline 2.1(a), without specifying which part of the app was inaccessible. We have tested the app and the demo account ourselves, and everything works as expected on our devices. The app can also be used without an account, and users can create an account directly within the app. We have now replied to App Review asking them to identify the specific screen, step, or functionality they were unable to access. We are currently waiting for a response. Has anyone experienced a similar situation? In particular, I would appreciate advice on how to get a more specific explanation from App Review, or whether there is an appropriate way to escalate the issue if they cannot identify what was inaccessible. I’m also wondering how reliable the 24-hour response timeframe is in practice. It has now been more than a day and a half since I replied to App Review. Should I expect a response within a few days, or can Resolution Center replies sometimes take considerably longer? Thank you.

BoltSense is a puzzle game where you tap bolts off a real 3D V8/inline-4 engine and sort them into color/shape-matched trays as it tears itself down layer by layer. Solo-built, first time opening it up to anyone outside my own family. I know this is flooded market; I got tired of pay to win platforms and wanted to build something better. Feedback I'm especially looking for: First few minutes — is it clear what to do with zero instructions? Where did you get stuck, if anywhere? Bolt shapes — can you tell hex bolts from round ones apart quickly while playing, or are you mostly going by color? Difficulty — does the first engine feel too easy, too hard, or about right for an opening puzzle? Considering that I have tested this with my 7 and 9 year old and they picked it up pretty easily following minimal instruction. Crashes, hangs, visual glitches — and what iPhone/iOS version you were on when it happened please! Public link: https://testflight.apple.com/join/YMpvN6bP Appreciate anyone willing to give it a shot — feedback straight through TestFlight works great for me. *I only have this set at 1000 testers I'm hopeful to see 10-20 maybe! Thank you!

Typical is an iOS app with a custom keyboard extension for high value salespeople: luxury real estate, yachts, cars, watches. The app stores clients, assets and conversation history. The keyboard shows the relevant client context inside WhatsApp while the user types, so they can answer specific questions without leaving the conversation. Feedback I am looking for: Keyboard onboarding: enabling the keyboard and granting Full Access. Is the warning off putting? Is the reason for Full Access clear enough? Client recap screen: is it understandable the first time it appears? Stability and performance: crashes, freezes, input lag in the keyboard. F eedback through TestFlight is preferred. https://testflight.apple.com/join/5yx5EDg5

I am testing a StoreKit 2 non-consumable IAP through TestFlight. Product ID: com.metabolla.plus.lifetime Type: Non-Consumable Environment: TestFlight / Sandbox Transaction.currentEntitlements keeps returning an active entitlement for this product even after: configuring a Sandbox Apple Account clearing Sandbox Purchase History reinstalling the app rebooting the device Important detail: the first TestFlight purchase was completed before configuring the Sandbox Apple Account on the device. If I temporarily change the Product ID in code, the entitlement disappears, so the issue seems tied to the original Product ID/account/receipt. Question: Can a non-consumable TestFlight purchase made before Sandbox Apple Account configuration remain associated with the original TestFlight/Apple ID identity? Is there any supported way to clear this entitlement for testing?

We are testing version 1.0 Build 29 through TestFlight after a Guideline 2.1(b) rejection: Purchase did not respond on iPad Air 11-inch (M3). Paid Apps Agreement is Active, and subscription price, availability, localization and review screenshot are present. Restores worked, but a fresh purchase is not yet verified. On iPhone 13, Build 29 is installed, Developer Mode is on, and Media & Purchases was signed out. The tester reports signing into Developer > Sandbox Apple Account, then trying to sign into the app. During this sequence an email verification prompt was followed by: "iTunes account creation not allowed. This Apple account cannot be used with iTunes Store at this time. Please try again later." The app uses Sign in with Apple separately from StoreKit. We have not isolated which system authentication flow produced the error. What is the supported sequence for regular iCloud/Sign in with Apple alongside a Sandbox Apple Account for TestFlight purchases? Which diagnostics distinguish account setup failure from app authentication or StoreKit failure? Should we escalate through Feedback Assistant or Developer Support, and which logs should accompany the report? We want to verify a fresh purchase on an 11-inch iPad before resubmission.

During dev time i've done some tests with app never releasedWhen i delete these apps, they move to "removed apps" and this prevent to reuse some App IDHow can I permanently delete an app so I can reuse an App ID?

Hi everyone, I'm encountering an issue where the storefront country code returns "USA" unexpectedly in TestFlight builds, and I'd appreciate any insights from the community. Issue Description When executing SKPaymentQueue.default().storefront?.countryCode in our TestFlight builds, the property returns USA. However, we expect it to return JPN because both the Sandbox test user account and the Apple Account region configured on the device are set to Japan. Behavior Across Environments Xcode Debug & Ad Hoc Builds: Returns JPN as expected. TestFlight Builds: Returns USA unexpectedly. Related Threads I've noticed several threads reporting similar issues without a clear resolution: https://developer.apple.com/forums/thread/660817 https://developer.apple.com/forums/thread/794932 https://developer.apple.com/forums/thread/800078 https://developer.apple.com/forums/thread/814178 https://developer.apple.com/forums/thread/810860 Questions Is this USA value a known TestFlight/Sandbox-specific limitation or bug? Will production users in Japan correctly receive JPN (and see JPY prices) once the app is approved and published on the App Store? Is there any workaround or project configuration fix required on our side prior to App Store submission? Has anyone experienced this recently or confirmed the behavior in the production environment after release? Thanks!

Hi, I'm completely blocked from TestFlight. Every attempt returns: "status": "422", "code": "BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." This is an older account that has used TestFlight fine before. Nothing changed on my end, no account changes, no agreement updates. What I've already checked: Business > Agreements: Paid Apps and Free Apps both Active Tax forms and bank account Active No pending banners anywhere in App Store Connect or developer.apple.com Test Information complete Export compliance answered Build processes to VALID with no warnings Same error on a brand new app with a fresh build, so it looks like the beta contract is detached on the backend rather than an app-level problem. I've filed a support request and haven't heard back. This is time sensitive, I have a client pilot waiting on an external TestFlight link. Is there any way to get this re-provisioned? Apple Support case ID: 20000118605424 Thanks.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. Around two weeks ago, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) My apps do not progress properly through review One app got stuck in “In Review” for ~10 days; I eventually withdrew it and resubmitted it At this point, I cannot update two existing apps, and I can’t start testing a new app at all Important details: This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

I've read several topics on cancelling subscriptions in sandbox environment, but it seems to me that it could not be applied to TestFlight. I can cancel sandbox subscriptions through Settings > App Store > Sandbox account But since TestFlight does not use sandbox account I cannot cancel a sub from there. Also, TF purchase does not appear in the list of regular subscriptions (Settings > Profile > Media & Purchases). So my question is: is there any way to manually cancel auto-renewable subscription bought in TestFlight build of the app?

A sandboxed Mac app with correct CloudKit entitlements fails to connect to com.apple.cloudd (the CloudKit daemon) when distributed via TestFlight (Mac Team Store Provisioning Profile). The identical binary works correctly when launched from Xcode (Mac Team Provisioning Profile also present). All entitlements are correctly embedded and the App ID is properly configured in Apple Developer Portal. Environment macOS 26.5.1 (25F80) Xcode 26.5 (17F42) SwiftData with NSPersistentCloudKitContainer / ModelConfiguration(cloudKitDatabase: .private(...)) Steps to Reproduce Create a sandboxed Mac app using SwiftData with CloudKit sync Enable iCloud + CloudKit in Signing & Capabilities Archive and distribute to TestFlight (Mac Team Store Provisioning Profile) Install via TestFlight on macOS 26 and launch Check Console for kernel sandbox messages Expected Result CloudKit connects to com.apple.cloudd and syncs data, matching behavior of the iOS version using the same container. Actual Result Console shows repeated kernel sandbox denials followed by CloudKit setup failure: kernel Sandbox: CheatSheet Mac(82347) deny(1) mach-lookup com.apple.cloudd kernel Sandbox: CheatSheet Mac(82347) deny(1) mach-lookup com.apple.duetactivityscheduler CheatSheet Mac CoreData+CloudKit: Failed to set up CloudKit integration for store Error Domain=CKErrorDomain Code=6 "Error connecting to CloudKit daemon." Key Diagnostic Finding When launched from Xcode, taskgated-helper validates both the Mac Team Store Provisioning Profile AND the Mac Team Provisioning Profile, and CloudKit succeeds: cloudd: TCC approved access for container containerID=iCloud.com.michaelendres.CheatSheet:Production When launched from TestFlight, only the Mac Team Store Provisioning Profile is present, and the sandbox denies com.apple.cloudd despite identical entitlements in the binary: codesign -d --entitlements shows: com.apple.developer.icloud-services: [CloudKit] com.apple.developer.icloud-container-identifiers: [iCloud.com.michaelendres.CheatSheet] com.apple.developer.icloud-container-environment: Production com.apple.security.app-sandbox: true Conclusion The Mac Team Store Provisioning Profile on macOS 26 does not appear to grant the sandbox exception for mach-lookup com.apple.cloudd, while the Mac Team Provisioning Profile (development) does. This prevents any Mac App Store / TestFlight app using CloudKit from syncing on macOS 26.

One build has version 1.0 the other has version 1.01. Both has status Complete. How to remove the version 1.0 one ?

Hi everyone, I’m looking for external TestFlight testers for Personal Finance, a SwiftUI app for managing accounts, payment cards, investments, and personal budgets in one place. The app does not connect to banks. Users enter and manage their financial information manually, and the data remains on the device. The current beta includes: • Account, card, and investment balance tracking • Personal budget calculations with recurring and one-time items • Automatic balance updates for card payments • Home Screen widgets for balances and budgets • Direct links from widgets to the relevant editing views • Optimized layouts for both iPhone and iPad • Finnish and English language support I would especially appreciate feedback on: • Overall usability and clarity • Calculation accuracy • Adding and editing financial information • Widget installation and behavior • iPad layouts in portrait, landscape, and Split View • Missing features or confusing workflows • Crashes, data issues, and visual bugs Public TestFlight link: https://testflight.apple.com/join/BZgZNnhn Feedback can be submitted directly through TestFlight. Thank you to anyone willing to try it and share their experience.

People have been abusing TestFlight's trusted distribution to distribute apps. Apple needs to improve their automated testing and maybe get human reviewers involved. Even a glance at the name or logo would raise flags. This comes from official Apple's testflight email, the logo, name is all Trademark ripoff.

Hi, I am seeing "Waiting for Review" for the past 10 hours, and I do not know why it is taking so long, some of my versions get approved quickly some versions taking a long time. General Information Bundle ID: com.salesforce.pronto.fooddelivery.ProntoFoodDeliveryApp SKU: com.salesforce.pronto.fooddelivery.ProntoFoodDeliveryApp Apple ID: 6756443629 App Name: ProntoFoodDeliveryApp Bundle Short Version String: 1.0.6 Bundle Version String: 2 Please let me know if you need any additional information. My testers are waiting to test the new features. Thank you

Hi everyone! I’m looking for external TestFlight testers for Kauppalista, a simple iPhone shopping list app that I’m currently preparing for its first public release. The app is available in English and Finnish. Kauppalista is designed to make everyday grocery shopping easier. You can: Save frequently purchased products and their preferred stores Organize your shopping list automatically by store Change quantities and stores while shopping Mark individual items or all items in a store as purchased Quickly add recently and frequently purchased products Get suggestions based on your actual purchase rhythm Reorder stores and products to match your usual shopping route Share your shopping list Use the app in English or Finnish I’m especially interested in feedback from people who are willing to use the app during a real shopping trip, rather than only trying it for a few minutes. I’d particularly like to know: Is anything confusing or difficult to discover? Does anything require too many taps? Are the shopping suggestions useful? Does organizing products by store work naturally for you? Did you encounter any bugs or unexpected behavior? Is there something you expected the app to do but couldn’t? Are there any problems with the English translations? The app does not require an account or sign-in. TestFlight: https://testflight.apple.com/join/HN5mehXp This is my first public beta, so feedback about the overall usability is particularly valuable. Thanks for testing! Feedback through TestFlight or here on the forum is very welcome.

Hello, I cannot submit a build for TestFlight external (Beta App Review). The UI shows a generic error; the API returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING. There is no pending agreement I can accept. App / account App: Siteopya Bundle ID: com.siteopya.mobile Version / build: 1.0.0 (15) — processing Complete, status Ready to Submit Platform: iOS Team ID: 6L5F59LRS7 Enrollment: Individual (I am the Account Holder) Membership: Active, renewal 25 Aug 2027, auto-renew On Agreements (all accepted / Active) Apple Developer Program License Agreement — accepted 24 Aug 2026 Apple Developer Agreement — accepted 23 Aug 2026 Free Apps Agreement — Active Paid Apps Agreement — Active Bank account — Active Tax forms (W-8BEN) — Active No yellow “Review Agreement” banner on developer.apple.com/account What works Uploading builds (12–15) completes normally Build 15 appears in TestFlight as Ready to Submit Build 15 is already assigned to the internal group What fails External group → Select build 15 → Submit for Review POST https://appstoreconnect.apple.com/iris/v1/betaAppReviewSubmissions 422: { "errors": [{ "id": "c1bcfddb-7bc5-4a17-a5c7-5363928b2afe", "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." }] } Internal testers: install fails in the TestFlight app “Couldn't install Siteopya. Try again later.” “Couldn't install Siteopya. The requested app is not available or doesn't exist.” Support cases (no reply yet) Case ID: 20000151012553 Case ID: 102951050062 Opened: 1 Sep 2026 Could an Apple engineer please re-attach / re-provision the TestFlight Beta Contract for this app? There is nothing pending on my side. Thank you.

I accepted an invite sent to everyone else on my team to join the development team we're all participating in to test our app. I'm sent to this page: "Sign in to accept your invitation You have been invited to join a team in the Apple Developer Program. As a member, you'll have access to resources, such as beta software and App Store Connect, for creating and distributing apps for Apple platforms." And attempt to click the button labeled "Sign in with Apple Account". Doing so simply reloads this page, though. with no apparent option to proceed. I'm unfortunately blocked from participating now. How do I get around this and successfully accept the invite?

Hi everyone! I'm looking for beta testers for Aimora, an intelligent personal assistant for iPhone designed to help you move forward when you're not sure what to do next. Aimora helps turn a goal or situation into one clear, practical next step, while learning from your progress over time. I'm especially interested in honest feedback about the UX, usefulness, and whether the concept actually helps in real life. The app is currently in beta and available through TestFlight. If you'd like to try it, I'd really appreciate your feedback! Thank you! https://testflight.apple.com/join/GdB6N39k