TestFlight

RSS for tag

TestFlight within App Store Connect allows you to invite and manage testers who can install and beta test your iOS, iPadOS, tvOS, and watchOS apps using the TestFlight app on the App Store.

Posts under TestFlight tag

200 Posts

Post

Replies

Boosts

Views

Activity

TestFlight Public Links on the forums
TestFlight Public Links are a great way to share beta versions of your apps with other members of the Apple Developer Program. With this new channel, you can share your TestFlight Public Links with the developer community, to gather valuable feedback on crucial elements, like technical implementation, user experience, design, and more. To maximize the benefits of posting TestFlight Public Links in the Developer Forums, here are some best practices to keep in mind: Provide details: Give comprehensive information about your app, like new features and test cases, and note specific areas where you seek feedback. The more detailed your post is, the better equipped the community will be to provide insight. Select platforms: Select the platforms that your beta app supports. Enter categories: Enter the App category you’ve selected or plan to select for your app on the App Store. Categories are critical to ensuring your post can be easily found by interested users. Stay connected with notifications: Enable web and push notifications so you’ll know when you receive feedback on your post. Note: The TestFlight app is still the most comprehensive way to gather feedback. This space is meant as a helpful secondary channel.
0
0
5.7k
Aug ’23
TestFlight dead on new account: internal invites never sent, 422 ENTITY_UNPROCESSABLE on beta review
Since my first TestFlight upload on November 2, 2026, TestFlight does not work for my app at all. This looks like the same account-level issue many developers have reported since late October 2026. Region: Türkiye Account: individual, enrolled October 26, 2026; latest Program License Agreement accepted November 6 App ID: 6828238853, builds 1.0 (1) and 1.0 (2) Symptoms: Internal testers stay "Invited", the INVITES column stays empty and no invitation email is ever sent. Submitting a build for external beta review always fails: POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." Error ID: a254e078-e9a9-44c4-be23-3d75d6d8daad API correlation key: 4IHT4ZPBDXIOSMH6J2GPZTDU5E Even saving "What to Test" notes for an internal build fails with "Validation Error". Already checked: Free Apps Agreement and DSA are active, Test Information, privacy policy, App Privacy, age rating and export compliance are complete, ITSAppUsesNonExemptEncryption = NO. A new build, reinvites and removing/re-adding testers did not help. Developer Support case 30000005085209 has been open since November 4. A reply dated November 17 shows on the case but the email never arrived. Could someone from the TestFlight team please check and re-provision the TestFlight setup for my account?
1
0
130
36m
TestFlight - 422 ENTITY_UNPROCESSABLE
Enrolled: 10 Nov 2026. First builds uploaded 11–12 Nov 2026, fault seen from the very first build. Internal testers stay "Invited", the invitation e-mail never arrives (Resend, removing/re-adding testers and new builds did not help). Other Apple e-mails reach the same addresses normally. Beta App Review submit always fails with "There was an error processing your request. Please try again later." — POST betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE, both in the web UI and through the App Store Connect API. No betaAppReviewSubmission is created. Builds are VALID, external state READY_FOR_BETA_SUBMISSION. Same result from the Account Holder's own session and from the Admin's session. What we checked / tried, none helped: All agreements accepted (Program License Agreement, Free Apps Active), DSA compliance completed. Test Information, Beta App Review Information, What to Test, export compliance all complete. New builds with new build numbers. A brand-new app record with a NEW bundle ID in the same team: exactly the same two symptoms. Two observations that may help others: Another newly enrolled individual team that we manage (same week, same Admin user, same CI pipeline, same Test Information) works normally: invites arrive, external submission goes to Waiting for Review. So it looks team-specific, not setup-specific. App Store submission is NOT blocked: the same build went to "Waiting for Review" for App Store review without problems. Only TestFlight is affected. Two Developer Support cases are open (Membership and Account), automated replies only so far. Following b2mode's update, I will also file under Distribution > TestFlight. Will report back here when it is resolved.
0
0
5
40m
Beta testers wanted: Starbit Dash, retro pixel space shooter (iPhone, iOS 17+)
Hi everyone! I’m looking for beta testers for Starbit Dash, a twin-stick space shooter for iPhone with pixel art and a handheld console look. 6 acts, 18 bosses with their own attack patterns, endless mode with up to 4 bosses at once Perks after every boss, 30 pilot levels, unlockable rockets No ads, no tracking, no account; works offline What I’d most like feedback on: Is Act 1 too easy, too hard or just right? Anything confusing in the menus or the workshop? Join the beta: Starbit Dash Testflight Feedback via TestFlight screenshot or as a reply here. Thanks!
0
0
5
1h
Lily Money – beta testers wanted for a money management app (iPhone/iPad)
Hi all, I'm looking for beta testers for Lily Money. I started building it when my daughter went to college, to help her manage her own money while still giving us a way to help. You enter transactions yourself, with no bank connection. It has a transaction register, savings goals, Future Money for planning ahead, account reconciliation, and Available to Spend, which accounts for money you've already set aside. Shared Access lets you invite someone to view or help manage, with permissions you control. I'd like to hear what works, what doesn't make sense and what breaks. TestFlight: https://testflight.apple.com/join/vkFytBaz Requires iPhone or iPad on iOS 26.5 or later. Thanks!
0
0
125
10h
Looking for beta testers: Remolo, your Mac's screen on iPhone and iPad (iOS, iPadOS, macOS, watchOS)
Hi everyone, I'm Kiril, a solo developer. I'm looking for testers for Remolo, an iPhone and iPad app (with a small Mac companion) that puts your Mac's screen on your phone so you can control it right there. What it does the Mac's live screen above a trackpad with macOS gestures, a magnifier and full screen keyboard with modifiers and shortcuts, a shared clipboard, files both ways the Mac's Dock on the phone: switch apps, open their windows, snap windows Keynote from the phone with the next slide and notes; a clicker for any app; Apple Watch turns slides works at home directly and from anywhere through an end-to-end encrypted relay (Noise XX + CPace pairing), no accounts, no port forwarding Links TestFlight: https://testflight.apple.com/join/e4JNpMT4 Mac companion (free, notarized menu-bar app, macOS 15+): https://remolo.app/download Requires iOS / iPadOS 18 or later. Where feedback helps most Setup: how long from installing the Mac app to the first cursor move, and where you got stuck (Accessibility and Screen Recording permissions, pairing) Connecting from outside your home network: cellular, hotel or office Wi-Fi, CGNAT How the trackpad and screen feel: latency, scrolling, gestures, rotating to full screen iPad layout and Apple Watch slide control In the beta all Pro features are unlocked. Shake the phone to send a report from inside the app, or reply here. Thanks!
4
0
330
13h
StoreKit 2 returns USD product metadata in TestFlight while the storefront is FRA/EUR
Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.
11
1
1.6k
16h
SKPaymentQueue.default().storefront?.countryCode returns "USA" only in TestFlight
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!
3
1
661
18h
App Replacement - How to test in TestFlight
Has anyone gotten the App Replacement dialog to show up when launching an app configured with the replacement bundle identifiers in TestFlight? Per the documentation is says app [re]placement can be tested via TestFlight. https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.superseded-application-identifiers I've tried these two scenarios and have not gotten the system prompt to appear yet, all testing done on iOS 27.2 or 27.3 beta 1/2. Scenario A: App 1 installed via TestFlight, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". Scenario B: App 1 installed via App Store, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". In neither scenario did the system present the modal for me to transfer data or delete the previously installed app. Are there minimum usage or filesystem requirements that need to be present in the original and replaced app? FB25559759 - TestFlight / App Replacement: App Replacement did not trigger as described by documentation when installing from TestFlight
0
0
45
1d
TestFlight external Beta App Review fails with HTTP 422 across multiple apps on the same developer team
Hi everyone, I’m unable to submit builds for external TestFlight testing across multiple iOS apps on the same Apple Developer team. The builds upload successfully, but clicking “Submit for Review” in App Store Connect fails before the build enters Beta App Review. Here’s one example I reproduced and captured in Chrome DevTools: App: Benny Wallet App Apple ID: 6834886147 iOS version and build: 0.3.1 (104) Build status: Ready to Submit Request: POST /iris/v1/betaAppReviewSubmissions Response: HTTP 422 ENTITY_UNPROCESSABLE Error message: “There was an error processing your request. Please try again later.” Both the Free Apps and Paid Apps agreements show as active. I reproduced the error with “Automatically notify testers” turned off as well. Other apps on the same team show the same submission error in the UI. This looks similar to the reports in https://developer.apple.com/forums/thread/857429. Has anyone with the same HTTP 422 across multiple apps managed to get external TestFlight submissions working again? If so, what fixed it? If someone from the App Store Connect or TestFlight team is able to look into this, could you check whether there’s an issue with our team’s beta distribution authorization or Beta Contract association? I’ve filed Feedback Assistant report FB25625640. I can provide the Apple request UUID and UTC timestamp through that report if needed. Thanks, Frank
0
1
40
1d
Stuck in an infinite loop attempting to accept Developer Program invite
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?
4
3
835
1d
StoreKit returns USD prices instead of EUR in TestFlight, blocking app release (iOS 27.0.1)
We are experiencing the same issue with two independent native iOS apps on an iPhone running iOS 27.0.1, using TestFlight in France. Our annual subscription displays US$34.90 instead of €39.90, and our non-consumable purchase displays US$5.99 instead of €6.99. Both apps displayed the correct EUR prices during local Xcode testing. In TestFlight, Apple's native purchase sheets still show the correct EUR prices, and both purchases work successfully. We have contacted Apple Developer Support (case 103017935062). As this issue is delaying the time-sensitive release of our educational app, could Apple confirm whether a workaround is available or whether a fix is planned? https://developer.apple.com/forums/thread/845478 Thank you.
3
0
89
1d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
4
0
136
3d
TestFlight invitations not sent to any internal testers – account-level issue
Hello, I’m following up on case 30000013215244, opened 4 days ago, still without a response. TestFlight invitation emails are not being delivered to any internal tester on my account, including myself (Account Holder). The app does not appear in the TestFlight app for any of us. App name / Apple ID: Cosmine / 6825922062 Team ID: 5YFU7N787S Build 1.0.0 is processed and shows “Testing” in the internal group All testers are active App Store Connect users and are added to the internal group The Apple Account on each device matches the invited email Already tried: resending invitations, removing and re-adding testers, creating a new internal group, reinstalling TestFlight All agreements are active Since this affects multiple testers and not just one device or account, I believe this is an account-level issue on Apple’s side (possibly related to the beta contract). Could you please escalate this to the TestFlight team? Thank you.
0
1
80
3d
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
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.
60
8
7.1k
3d
TestFlight broken account-wide since accepting the Oct 29 PLA: invites not delivered, 422 on beta review
Hello, I am a member of the development team below, posting on behalf of the Account Holder. TestFlight stopped working for our whole team right after the Account Holder accepted the new Apple Developer Program License Agreement. It worked before that. Developer Support has not replied for two weeks, so I am posting here in the hope that someone from Apple can check the account. Account Individual account, Team ID: RWNM978YJZ Developer Support case: 103014923825 (Distribution > TestFlight), opened by the Account Holder on Oct 31, followed up Nov 3, no reply so far Timeline Oct 16: membership purchased Oct 22: first app uploaded to TestFlight, internal testers received invitations and installed the build. Everything worked. Oct 29: new Program License Agreement issued Oct 30: Account Holder accepted it. TestFlight has been broken since that day. Symptoms (all apps, including a newly created one) Invitations are not delivered. Neither App Store Connect user invitations nor TestFlight invitations reach any email address (several addresses and domains tried). New users stay "Invited" forever. The Account Holder is shown as "Invited" in the team's own internal testing group. "Reinvite" does nothing. First app: builds are visible in the TestFlight app, but Install fails with "The requested app is not available or doesn't exist." External testing: adding a build to an external group and pressing "Submit for Review" fails with "There was an error processing your request. Please try again later." The same via the App Store Connect API: POST /v1/betaAppReviewSubmissions -> HTTP 422 code: ENTITY_UNPROCESSABLE title: There was an error processing your request. detail: Please try again later. Error ID: aadd3917-d3ab-4199-be32-7e5a4d63b748 (Nov 7, 2026, 16:57 UTC) App used for the test Name: Байрон, bundle ID work.100m.byron, Apple ID 6831904523 Build 0.1.0 (1), build ID 566f41b9-5816-45f6-a653-cc3920d4dd36 processingState VALID, usesNonExemptEncryption false internalBuildState IN_BETA_TESTING, externalBuildState READY_FOR_BETA_SUBMISSION Beta App Review information, test information and privacy policy URL are filled in Already checked Membership active Program License Agreement accepted (Oct 30), Free Apps Agreement Active, DSA status set, nothing pending in Business > Agreements Export compliance answered The Apple Account on the test iPhone (App Store and TestFlight) matches the developer account Removed and re-created groups, testers and the app record; tried Safari; revoked all API keys The same builds install fine from Xcode and via Ad Hoc distribution, so the binaries are fine This looks like the account-level problem described in threads 814565, 815875, 856151 and 853895 (BETA_CONTRACT_MISSING / beta contract detached on the backend), in our case triggered by accepting the new agreement. Could someone from Apple please check the team-level beta contract record for Team ID RWNM978YJZ and re-provision it, or escalate case 103014923825? The Account Holder is available to confirm anything through the case. Thank you.
1
0
146
3d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
1
0
76
3d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
3
0
107
3d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
1
0
62
3d
TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds
153
13
11k
3d
TestFlight external testing: "Submit for Review" always fails with 422 ENTITY_UNPROCESSABLE "Please try again later"
Hello, Since November 8, every attempt to submit a build for TestFlight External Testing fails with the same generic error, both in the App Store Connect web UI and through the App Store Connect API: 422 ENTITY_UNPROCESSABLE - "Please try again later" Error id: 0c932f5d-b469-4fc3-bc16-99e223f17bb6 (no source / meta details in the error object) What is already done on our side: Apple Developer Program membership is active (Individual), and all agreements are accepted (Free Apps Agreement and DSA active) The build is VALID in App Store Connect and works in Internal Testing Test Information is complete (beta description, feedback email, contact info, privacy policy URL) "What to Test" is filled in for the build App Information is complete: category, content rights, age rating (including the new questions), privacy policy URL The error has stayed the same for over a week, with several builds and on different days, so it looks like something on the account side rather than in the build or the metadata. I also opened a support case (30000006592385) but have had no resolution yet. Could someone from Apple please check the account, or tell me what is blocking the external submission? Thank you.
0
0
51
4d
TestFlight Public Links on the forums
TestFlight Public Links are a great way to share beta versions of your apps with other members of the Apple Developer Program. With this new channel, you can share your TestFlight Public Links with the developer community, to gather valuable feedback on crucial elements, like technical implementation, user experience, design, and more. To maximize the benefits of posting TestFlight Public Links in the Developer Forums, here are some best practices to keep in mind: Provide details: Give comprehensive information about your app, like new features and test cases, and note specific areas where you seek feedback. The more detailed your post is, the better equipped the community will be to provide insight. Select platforms: Select the platforms that your beta app supports. Enter categories: Enter the App category you’ve selected or plan to select for your app on the App Store. Categories are critical to ensuring your post can be easily found by interested users. Stay connected with notifications: Enable web and push notifications so you’ll know when you receive feedback on your post. Note: The TestFlight app is still the most comprehensive way to gather feedback. This space is meant as a helpful secondary channel.
Replies
0
Boosts
0
Views
5.7k
Activity
Aug ’23
TestFlight dead on new account: internal invites never sent, 422 ENTITY_UNPROCESSABLE on beta review
Since my first TestFlight upload on November 2, 2026, TestFlight does not work for my app at all. This looks like the same account-level issue many developers have reported since late October 2026. Region: Türkiye Account: individual, enrolled October 26, 2026; latest Program License Agreement accepted November 6 App ID: 6828238853, builds 1.0 (1) and 1.0 (2) Symptoms: Internal testers stay "Invited", the INVITES column stays empty and no invitation email is ever sent. Submitting a build for external beta review always fails: POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." Error ID: a254e078-e9a9-44c4-be23-3d75d6d8daad API correlation key: 4IHT4ZPBDXIOSMH6J2GPZTDU5E Even saving "What to Test" notes for an internal build fails with "Validation Error". Already checked: Free Apps Agreement and DSA are active, Test Information, privacy policy, App Privacy, age rating and export compliance are complete, ITSAppUsesNonExemptEncryption = NO. A new build, reinvites and removing/re-adding testers did not help. Developer Support case 30000005085209 has been open since November 4. A reply dated November 17 shows on the case but the email never arrived. Could someone from the TestFlight team please check and re-provision the TestFlight setup for my account?
Replies
1
Boosts
0
Views
130
Activity
36m
TestFlight - 422 ENTITY_UNPROCESSABLE
Enrolled: 10 Nov 2026. First builds uploaded 11–12 Nov 2026, fault seen from the very first build. Internal testers stay "Invited", the invitation e-mail never arrives (Resend, removing/re-adding testers and new builds did not help). Other Apple e-mails reach the same addresses normally. Beta App Review submit always fails with "There was an error processing your request. Please try again later." — POST betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE, both in the web UI and through the App Store Connect API. No betaAppReviewSubmission is created. Builds are VALID, external state READY_FOR_BETA_SUBMISSION. Same result from the Account Holder's own session and from the Admin's session. What we checked / tried, none helped: All agreements accepted (Program License Agreement, Free Apps Active), DSA compliance completed. Test Information, Beta App Review Information, What to Test, export compliance all complete. New builds with new build numbers. A brand-new app record with a NEW bundle ID in the same team: exactly the same two symptoms. Two observations that may help others: Another newly enrolled individual team that we manage (same week, same Admin user, same CI pipeline, same Test Information) works normally: invites arrive, external submission goes to Waiting for Review. So it looks team-specific, not setup-specific. App Store submission is NOT blocked: the same build went to "Waiting for Review" for App Store review without problems. Only TestFlight is affected. Two Developer Support cases are open (Membership and Account), automated replies only so far. Following b2mode's update, I will also file under Distribution > TestFlight. Will report back here when it is resolved.
Replies
0
Boosts
0
Views
5
Activity
40m
Beta testers wanted: Starbit Dash, retro pixel space shooter (iPhone, iOS 17+)
Hi everyone! I’m looking for beta testers for Starbit Dash, a twin-stick space shooter for iPhone with pixel art and a handheld console look. 6 acts, 18 bosses with their own attack patterns, endless mode with up to 4 bosses at once Perks after every boss, 30 pilot levels, unlockable rockets No ads, no tracking, no account; works offline What I’d most like feedback on: Is Act 1 too easy, too hard or just right? Anything confusing in the menus or the workshop? Join the beta: Starbit Dash Testflight Feedback via TestFlight screenshot or as a reply here. Thanks!
Replies
0
Boosts
0
Views
5
Activity
1h
Lily Money – beta testers wanted for a money management app (iPhone/iPad)
Hi all, I'm looking for beta testers for Lily Money. I started building it when my daughter went to college, to help her manage her own money while still giving us a way to help. You enter transactions yourself, with no bank connection. It has a transaction register, savings goals, Future Money for planning ahead, account reconciliation, and Available to Spend, which accounts for money you've already set aside. Shared Access lets you invite someone to view or help manage, with permissions you control. I'd like to hear what works, what doesn't make sense and what breaks. TestFlight: https://testflight.apple.com/join/vkFytBaz Requires iPhone or iPad on iOS 26.5 or later. Thanks!
Replies
0
Boosts
0
Views
125
Activity
10h
Looking for beta testers: Remolo, your Mac's screen on iPhone and iPad (iOS, iPadOS, macOS, watchOS)
Hi everyone, I'm Kiril, a solo developer. I'm looking for testers for Remolo, an iPhone and iPad app (with a small Mac companion) that puts your Mac's screen on your phone so you can control it right there. What it does the Mac's live screen above a trackpad with macOS gestures, a magnifier and full screen keyboard with modifiers and shortcuts, a shared clipboard, files both ways the Mac's Dock on the phone: switch apps, open their windows, snap windows Keynote from the phone with the next slide and notes; a clicker for any app; Apple Watch turns slides works at home directly and from anywhere through an end-to-end encrypted relay (Noise XX + CPace pairing), no accounts, no port forwarding Links TestFlight: https://testflight.apple.com/join/e4JNpMT4 Mac companion (free, notarized menu-bar app, macOS 15+): https://remolo.app/download Requires iOS / iPadOS 18 or later. Where feedback helps most Setup: how long from installing the Mac app to the first cursor move, and where you got stuck (Accessibility and Screen Recording permissions, pairing) Connecting from outside your home network: cellular, hotel or office Wi-Fi, CGNAT How the trackpad and screen feel: latency, scrolling, gestures, rotating to full screen iPad layout and Apple Watch slide control In the beta all Pro features are unlocked. Shake the phone to send a report from inside the app, or reply here. Thanks!
Replies
4
Boosts
0
Views
330
Activity
13h
StoreKit 2 returns USD product metadata in TestFlight while the storefront is FRA/EUR
Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.
Replies
11
Boosts
1
Views
1.6k
Activity
16h
SKPaymentQueue.default().storefront?.countryCode returns "USA" only in TestFlight
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!
Replies
3
Boosts
1
Views
661
Activity
18h
App Replacement - How to test in TestFlight
Has anyone gotten the App Replacement dialog to show up when launching an app configured with the replacement bundle identifiers in TestFlight? Per the documentation is says app [re]placement can be tested via TestFlight. https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.superseded-application-identifiers I've tried these two scenarios and have not gotten the system prompt to appear yet, all testing done on iOS 27.2 or 27.3 beta 1/2. Scenario A: App 1 installed via TestFlight, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". Scenario B: App 1 installed via App Store, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". In neither scenario did the system present the modal for me to transfer data or delete the previously installed app. Are there minimum usage or filesystem requirements that need to be present in the original and replaced app? FB25559759 - TestFlight / App Replacement: App Replacement did not trigger as described by documentation when installing from TestFlight
Replies
0
Boosts
0
Views
45
Activity
1d
TestFlight external Beta App Review fails with HTTP 422 across multiple apps on the same developer team
Hi everyone, I’m unable to submit builds for external TestFlight testing across multiple iOS apps on the same Apple Developer team. The builds upload successfully, but clicking “Submit for Review” in App Store Connect fails before the build enters Beta App Review. Here’s one example I reproduced and captured in Chrome DevTools: App: Benny Wallet App Apple ID: 6834886147 iOS version and build: 0.3.1 (104) Build status: Ready to Submit Request: POST /iris/v1/betaAppReviewSubmissions Response: HTTP 422 ENTITY_UNPROCESSABLE Error message: “There was an error processing your request. Please try again later.” Both the Free Apps and Paid Apps agreements show as active. I reproduced the error with “Automatically notify testers” turned off as well. Other apps on the same team show the same submission error in the UI. This looks similar to the reports in https://developer.apple.com/forums/thread/857429. Has anyone with the same HTTP 422 across multiple apps managed to get external TestFlight submissions working again? If so, what fixed it? If someone from the App Store Connect or TestFlight team is able to look into this, could you check whether there’s an issue with our team’s beta distribution authorization or Beta Contract association? I’ve filed Feedback Assistant report FB25625640. I can provide the Apple request UUID and UTC timestamp through that report if needed. Thanks, Frank
Replies
0
Boosts
1
Views
40
Activity
1d
Stuck in an infinite loop attempting to accept Developer Program invite
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?
Replies
4
Boosts
3
Views
835
Activity
1d
StoreKit returns USD prices instead of EUR in TestFlight, blocking app release (iOS 27.0.1)
We are experiencing the same issue with two independent native iOS apps on an iPhone running iOS 27.0.1, using TestFlight in France. Our annual subscription displays US$34.90 instead of €39.90, and our non-consumable purchase displays US$5.99 instead of €6.99. Both apps displayed the correct EUR prices during local Xcode testing. In TestFlight, Apple's native purchase sheets still show the correct EUR prices, and both purchases work successfully. We have contacted Apple Developer Support (case 103017935062). As this issue is delaying the time-sensitive release of our educational app, could Apple confirm whether a workaround is available or whether a fix is planned? https://developer.apple.com/forums/thread/845478 Thank you.
Replies
3
Boosts
0
Views
89
Activity
1d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
4
Boosts
0
Views
136
Activity
3d
TestFlight invitations not sent to any internal testers – account-level issue
Hello, I’m following up on case 30000013215244, opened 4 days ago, still without a response. TestFlight invitation emails are not being delivered to any internal tester on my account, including myself (Account Holder). The app does not appear in the TestFlight app for any of us. App name / Apple ID: Cosmine / 6825922062 Team ID: 5YFU7N787S Build 1.0.0 is processed and shows “Testing” in the internal group All testers are active App Store Connect users and are added to the internal group The Apple Account on each device matches the invited email Already tried: resending invitations, removing and re-adding testers, creating a new internal group, reinstalling TestFlight All agreements are active Since this affects multiple testers and not just one device or account, I believe this is an account-level issue on Apple’s side (possibly related to the beta contract). Could you please escalate this to the TestFlight team? Thank you.
Replies
0
Boosts
1
Views
80
Activity
3d
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
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.
Replies
60
Boosts
8
Views
7.1k
Activity
3d
TestFlight broken account-wide since accepting the Oct 29 PLA: invites not delivered, 422 on beta review
Hello, I am a member of the development team below, posting on behalf of the Account Holder. TestFlight stopped working for our whole team right after the Account Holder accepted the new Apple Developer Program License Agreement. It worked before that. Developer Support has not replied for two weeks, so I am posting here in the hope that someone from Apple can check the account. Account Individual account, Team ID: RWNM978YJZ Developer Support case: 103014923825 (Distribution > TestFlight), opened by the Account Holder on Oct 31, followed up Nov 3, no reply so far Timeline Oct 16: membership purchased Oct 22: first app uploaded to TestFlight, internal testers received invitations and installed the build. Everything worked. Oct 29: new Program License Agreement issued Oct 30: Account Holder accepted it. TestFlight has been broken since that day. Symptoms (all apps, including a newly created one) Invitations are not delivered. Neither App Store Connect user invitations nor TestFlight invitations reach any email address (several addresses and domains tried). New users stay "Invited" forever. The Account Holder is shown as "Invited" in the team's own internal testing group. "Reinvite" does nothing. First app: builds are visible in the TestFlight app, but Install fails with "The requested app is not available or doesn't exist." External testing: adding a build to an external group and pressing "Submit for Review" fails with "There was an error processing your request. Please try again later." The same via the App Store Connect API: POST /v1/betaAppReviewSubmissions -> HTTP 422 code: ENTITY_UNPROCESSABLE title: There was an error processing your request. detail: Please try again later. Error ID: aadd3917-d3ab-4199-be32-7e5a4d63b748 (Nov 7, 2026, 16:57 UTC) App used for the test Name: Байрон, bundle ID work.100m.byron, Apple ID 6831904523 Build 0.1.0 (1), build ID 566f41b9-5816-45f6-a653-cc3920d4dd36 processingState VALID, usesNonExemptEncryption false internalBuildState IN_BETA_TESTING, externalBuildState READY_FOR_BETA_SUBMISSION Beta App Review information, test information and privacy policy URL are filled in Already checked Membership active Program License Agreement accepted (Oct 30), Free Apps Agreement Active, DSA status set, nothing pending in Business > Agreements Export compliance answered The Apple Account on the test iPhone (App Store and TestFlight) matches the developer account Removed and re-created groups, testers and the app record; tried Safari; revoked all API keys The same builds install fine from Xcode and via Ad Hoc distribution, so the binaries are fine This looks like the account-level problem described in threads 814565, 815875, 856151 and 853895 (BETA_CONTRACT_MISSING / beta contract detached on the backend), in our case triggered by accepting the new agreement. Could someone from Apple please check the team-level beta contract record for Team ID RWNM978YJZ and re-provision it, or escalate case 103014923825? The Account Holder is available to confirm anything through the case. Thank you.
Replies
1
Boosts
0
Views
146
Activity
3d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
76
Activity
3d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
Replies
3
Boosts
0
Views
107
Activity
3d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
Replies
1
Boosts
0
Views
62
Activity
3d
TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds
Replies
153
Boosts
13
Views
11k
Activity
3d
TestFlight external testing: "Submit for Review" always fails with 422 ENTITY_UNPROCESSABLE "Please try again later"
Hello, Since November 8, every attempt to submit a build for TestFlight External Testing fails with the same generic error, both in the App Store Connect web UI and through the App Store Connect API: 422 ENTITY_UNPROCESSABLE - "Please try again later" Error id: 0c932f5d-b469-4fc3-bc16-99e223f17bb6 (no source / meta details in the error object) What is already done on our side: Apple Developer Program membership is active (Individual), and all agreements are accepted (Free Apps Agreement and DSA active) The build is VALID in App Store Connect and works in Internal Testing Test Information is complete (beta description, feedback email, contact info, privacy policy URL) "What to Test" is filled in for the build App Information is complete: category, content rights, age rating (including the new questions), privacy policy URL The error has stayed the same for over a week, with several builds and on different days, so it looks like something on the account side rather than in the build or the metadata. I also opened a support case (30000006592385) but have had no resolution yet. Could someone from Apple please check the account, or tell me what is blocking the external submission? Thank you.
Replies
0
Boosts
0
Views
51
Activity
4d