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.

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

Hello Apple Developer Support, We are experiencing an issue with TestFlight Internal Testing. Our internal testers can see the app and the assigned build in the TestFlight app, but when they try to install it, the installation fails with the following error: "Could not install [App Name]. The requested app is not available or doesn't exist." This issue happens with Internal Testing, so Beta App Review should not be involved. We have already checked the following: The build was uploaded successfully through Xcode using App Store Connect distribution. The build processing is completed. The build is assigned to the correct Internal Testing group. The testers are added as App Store Connect users and have access to the app. The app appears in TestFlight for the testers. Agreements, Tax, and Banking do not show any pending actions. Export Compliance / Missing Compliance does not show any pending actions. The issue happens on multiple devices. We have tried removing and reinstalling TestFlight, and uploading a new build number, but the issue still occurs. App details: App Name: WearNow AR Try-On Bundle ID: com.yakovchuk.wearnow Apple Developer Team ID: 6G4QX44Y4A Could you please check whether there is an account-level, app-level, or TestFlight backend issue that prevents this build from being installed by internal testers? This looks similar to multiple recent Apple Developer Forums reports where the app is visible in TestFlight, but installation fails with "The requested app is not available or doesn't exist." Thank you.

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?

Hi,i am trying to provide my newest build to my testers.I have to provide some information in the invitation mail, since many of them are new to the process.But after inviting my self as a test, Testflight keeps sending the outdated app description in the invitation mail.For the specific build, i changed the "What to Test" content and i also changed the "Beta App Description" in the "Test Information" Tab.But Testflight still sends the old text, which is nowhere to be found anymore.Am i doing something wrong? How can i fix this?

Has anyone seen Managed Background Assets get stuck before any download progress is reported on iPadOS 26.3 / TestFlight? We are using Apple-hosted managed asset packs for a large on-demand model download. The app can resolve the asset pack metadata: we can show the asset pack’s download size in the UI, so AssetPackManager.assetPack(withID:) appears to work. But when we call ensureLocalAvailability(of:), the UI stays at 0% indefinitely. We also do not receive any useful terminal state from statusUpdates(forAssetPackWithID:): no .began, .downloading, .failed, or .finished. The app remains responsive. The issue also appears persistent on the affected device/account. Reinstalling the app does not help, reinstalling TestFlight does not help, logging out and back in does not help, and restarting the device does not help. After each attempt, the app can still resolve the asset pack metadata/download size, but the actual download remains stuck before any progress or failure status is delivered. The suspicious part of the device log is that the managed helper starts normally, fetches/installs the manifest from TestFlight, but repeatedly fails to create its helper directory inside the app container: OurApp Initializing the asset-pack manager… OurApp Creating a proxy object for the helper service… OurApp activating connection ... name=com.apple.backgroundassets.managed.helper.service kernel Sandbox: no system container path found for ID "com.apple.backgroundassets.managed.helper.service" Managed Background Assets Helper Service Starting the Managed Background Assets Helper Service… Managed Background Assets Helper Service Configuring the directory suffix… Managed Background Assets Helper Service The directory suffix was successfully configured. Managed Background Assets Helper Service The extension token "<...>" was consumed. kernel Sandbox: Managed Background Assets Helper(...) deny(1) file-write-create /private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service Managed Background Assets Helper Service mkdir: path=/private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service/ mode= -rwx------: [1: Operation not permitted] After that, manifest fetching still seems to work: OurApp The asset-pack manager has been initialized. OurApp The system download-manager delegate has been assigned to the download manager. OurApp The app was installed for internal beta testing; checking for updates automatically… OurApp Refreshing the manifest… Managed Background Assets Helper Service The app with the bundle ID "..." is configured to use Apple hosting. Managed Background Assets Helper Service Asking the TestFlight extension via the App Store Daemon for the URL request... Managed Background Assets Helper Service Fetching the download manifest ... from TestFlight… Managed Background Assets Helper Service Installing a manifest at ".../Library/Application Support/.../Manifest.json"... But during/after manifest install, the same mkdir failure appears again: Managed Background Assets Helper Service Installing a manifest at ".../Manifest.json"... Managed Background Assets Helper Service mkdir: path=/private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service/ mode= -rwx------: [1: Operation not permitted] kernel duplicate reports for Sandbox: Managed Background Assets Helper(...) deny(1) file-write-create /private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service So the behavior seems to be: TestFlight/internal beta install Apple-hosted managed asset pack Manifest fetch succeeds Asset pack metadata resolves, including download size Actual local availability request never starts reporting progress No visible Background Assets failure reaches the app Logs show repeated sandbox file-write-create denial for the Managed Background Assets Helper trying to create /tmp/com.apple.backgroundassets.managed.helper.service inside the app container Reinstalling the app/TestFlight, logging out and back in, and restarting the device do not clear the stuck state On devices with 26.4, the issue doesn’t seem to exist Has anyone else seen this on iOS/iPadOS/macOS versions before 26.4? Is this a known issue in the Managed Background Assets helper/runtime? I noticed 26.4 added more local status APIs for asset packs, so I’m wondering whether this area changed in 26.4. Any hints on whether the sandbox denial is expected/noisy, or whether it could explain ensureLocalAvailability(of:) never progressing, would be appreciated.

I’m experiencing an issue with subscriptions that behave differently between Xcode builds and TestFlight. Subscriptions work correctly when running the app directly from Xcode in a sandbox environment, but they do not work as expected when testing the same build through TestFlight. Has anyone experienced a similar issue with subscriptions working in Xcode but failing in TestFlight? Any guidance on what to check or debug would be appreciated. Additional details: iOS version: [ IOS 26] StoreKit version: [ StoreKit 2] TestFlight: When attempting to load the subscription products, the app returns “Product not found”. In some cases, it also shows the error “The subscription is unavailable in the current storefront”. This happens consistently in TestFlight, even though the same products load and work correctly when running the app from Xcode in the sandbox environment. Thanks

Error in TestFlight: “The requested app is not available or does not exist.” This happens on multiple iPhones and Apple IDs. Important: Builds from OTHER Apple Developer accounts install fine on the same devices. We tried new apps, new bundle IDs, new certificates, new provisioning profiles. Internal testing fails. External testing also fails. All Agreements, Tax, Banking, and membership requirements are completed and active. When configuring external testing in App Store Connect, we also get: “There was an error processing your request. Please try again later.” This has been happening for 3 weeks. Has anyone seen an Apple Developer account / TestFlight backend issue like this? Any solution besides contacting Apple Developer Support?

Hello, I'm experiencing a critical issue with my Flutter iOS app on TestFlight where the app shows a completely black screen immediately after launch. The app does NOT crash (no .ips logs in iOS Settings → Analytics & Improvements), but Flutter Engine appears not to start at all. The same code runs perfectly on Android. PROJECT INFO: App Name: CNC AI Assistant Bundle ID: com.beratech.cncassistant Team ID: 958PPWZD27 Provisioning Profile UUID: 8122ca65-b15f-4daa-b0d2-1da5409c6859 Build CI: Codemagic Flutter Version: 3.41.5 iOS Deployment Target: 14.0 Test Device: iPad15,3 running iOS 26.x ISSUE BEHAVIOR: Build succeeds on Codemagic without errors IPA is signed with valid distribution certificate TestFlight processes and accepts the build Tester downloads/updates from TestFlight successfully App opens → completely BLACK SCREEN immediately LaunchScreen.storyboard does not appear App does not auto-close (must be manually killed) NO crash logs generated in iOS Settings Same exact codebase works on Android (Google Play Internal Testing) DEBUGGING ALREADY ATTEMPTED: Replaced main.dart with MINIMAL code (only Firebase init + single Scaffold with white background and Text widget) - still black screen Removed flutter_secure_storage package (had a known iOS 26 keychain init crash) - still black screen Updated IPHONEOS_DEPLOYMENT_TARGET from 13.0 to 14.0 in pbxproj to match Podfile platform - still black screen Tried both empty entitlements and entitlements matching the provisioning profile (com.apple.developer.applesignin + keychain-access-groups) - still black screen Verified GoogleService-Info.plist is registered in pbxproj Verified LaunchScreen.storyboard exists and is valid Verified Info.plist has UILaunchStoryboardName = LaunchScreen and ITSAppUsesNonExemptEncryption = false AppDelegate.swift contains only GeneratedPluginRegistrant.register PROVISIONING PROFILE ENTITLEMENTS: application-identifier: 958PPWZD27.com.beratech.cncassistant com.apple.developer.applesignin: Default keychain-access-groups: 958PPWZD27.*, com.apple.token com.apple.developer.team-identifier: 958PPWZD27 get-task-allow: false (production) INSTALLED PLUGINS (from GeneratedPluginRegistrant.m): firebase_auth, firebase_core, firebase_storage, cloud_firestore purchases_flutter, purchases_ui_flutter (RevenueCat) sign_in_with_apple, google_sign_in_ios shared_preferences_foundation, path_provider_foundation webview_flutter_wkwebview, video_player_avfoundation url_launcher_ios, image_picker_ios, file_picker permission_handler_apple, package_info_plus, device_info_plus app_links, open_filex QUESTIONS: What could cause a Flutter iOS app to silently fail to launch on iOS 26 with no crash logs? Is there a known incompatibility between iOS 26 and certain entitlement configurations? Could there be a mismatch issue between the provisioning profile entitlements and the app's actual entitlements that causes silent termination on iOS 26 specifically? How can I obtain detailed launch/crash logs from the test device when no .ips file is generated? (sysdiagnose only shows system services like BackgroundShortcutRunner, not my app) Are there any iOS 26-specific changes related to TestFlight builds or Flutter Engine initialization that I should be aware of? I have full access to: Complete pbxproj Info.plist, Runner.entitlements, Release.entitlements Codemagic build logs Generated IPA file Provisioning profile (.mobileprovision) Screenshots of black screen on test device Any guidance on diagnostic next steps or known iOS 26 issues would be greatly appreciated. Thank you in advance.

I was invited to join development team. so after receiving mail to my account I clicked accept invitation button in email. but the page of appstoreconnect shows that link is expired or invalid. however admin Is inviting me 2 min ago. how can I solve this problem? what should I do?

I'm experiencing a persistent issue where my app uploads successfully to TestFlight and appears in App Store Connect, but internal testers (including myself) receive the following error when attempting to install: "Could not install xxxxxxxxx. The requested app is not available or doesn't exist." What works: The build archives and exports successfully via Xcode (local build, Release configuration) The IPA uploads to App Store Connect without errors via eas submit The build appears in TestFlight and passes processing I can add the build to my Internal Testing group Testers receive the TestFlight notification and can see the app What fails: When any tester taps "Install" or "Update," the download begins briefly, then fails with the "not available or doesn't exist" error This affects all internal testers on the account, not just one device Troubleshooting already completed: Verified code signing is correct: Release configuration uses CODE_SIGN_STYLE = Manual, CODE_SIGN_IDENTITY = "iPhone Distribution", with a valid App Store distribution provisioning profile (UUID: 39bc4c63-bc64-403a-a2a6-6737b3d33115) 2. Distribution certificate is valid: Serial 4838CD7571DE5361B98A5FB2F769F74D, not expired (expires 2027-04-16) 3. Regenerated provisioning profile via EAS credentials, removed stale profiles, and rebuilt — same result 4. Incremented build numbers correctly across multiple submissions (3004 → 3005 → 3006) 5. Previously resolved a signing misconfiguration (build 3005 was incorrectly signed with "Apple Development" instead of "iPhone Distribution" due to expo prebuild reverting settings) — this was corrected for build 3006, but the install error persists 6. Confirmed the build is not stuck in processing — it shows as ready for testing in App Store Connect 7. Tested on multiple devices running current iOS versions 8. Cleared TestFlight app cache and reinstalled TestFlight on test devices Why I believe this is a server-side issue: Multiple developers in the Apple Developer Forums have reported the identical symptom — valid builds that upload and process correctly but fail to install with this exact error message. In those cases, Apple Support resolved the issue on their end within 48 hours with no action required from the developer. The signing, provisioning, and build configuration were not the cause. This one is very specific to what I am dealing with https://developer.apple.com/forums/thread/778597 One developer stated you fixed it on your side, without any real reasoning which also leads me to believe this is not something I can fix on my end https://developer.apple.com/forums/thread/778597?answerId=884241022#884241022 I've exhausted all client-side troubleshooting and believe this may require intervention on Apple's side. Has anyone been able to fix this on their end and not only when App Development called? I went through tons of the feedback and tried it all and it doesn't seem to be fixed. It's been a month or so like this. I can't get any info on who to call. I sent in a report to feedback assistant and through app developer support

Hi there, In the last few days ALL TF builds i has been flagged as Expired. Uploading new builds to TF seems to be successful but we get a 404 on the download link. It doesn't exist! Client side we have seemingly exhausted all our lines of enquiry. All certification seems to be correct and intact, and we can publish to the store. We cannot distribute builds through TF - which is highly problematic and inconvenient. These issues seems to be happening to many developers but I've not seen Apple comment on this yet. https://developer.apple.com/forums/thread/823347 https://developer.apple.com/forums/thread/778597 https://developer.apple.com/forums/thread/778597?answerId=885232022#885232022 I offer this as a sidenote. We transferred an app from this store, successfully to another store. The timing at first seemed linked, but now having seen other reports, it may just have been coincidence. Thankyou for your attention.

Hi everyone, I’m currently implementing Tap to Pay on iPhone following Apple’s official documentation. I’ve completed all the required configurations (entitlements, capabilities, merchant setup, etc.) on the Apple Developer portal. However, when I archive the app and attempt to upload it to TestFlight, I receive the following error: "Profile doesn't support Tap to Pay on iPhone. Profile doesn't include the com.apple.developer.proximity-reader.payment.acceptance entitlement." From what I understand, this seems related to the provisioning profile not including the required entitlement, even though I believe everything has been configured correctly. I have already tried: Regenerating provisioning profiles Verifying App ID capabilities Ensuring the correct entitlements are added in the project But the issue still persists. Has anyone encountered this issue before? Is there any additional approval step required from Apple to enable the Tap to Pay entitlement? I’d really appreciate any advice or experience you can share. Thanks in advance!

Dear TestFlight Team! I am observing an increasing misuse of TestFlight public and private invites to distribute scam, spam, and potentially malicious builds: I had reported this already in December last year via Feedback assistant, but since the malicious behavior has not stopped, I hope that you can forward my bug reports to the right team: FB21379977, FB21845307 In multiple cases, these builds impersonate well-known apps (e.g. ChatGPT, OpenAI, Meta) by changing the app name and icon after an initial TestFlight approval, misleading users into installing software from unrelated developer accounts. I believe this represents a systemic weakness in the TestFlight review and update flow, enabling targeted phishing or malware distribution outside the App Store review process. My bug reports have attached: TestFlight invitation emails (.eml) Screenshots from TestFlight documenting impersonation behavior ⸻ Steps to reproduce Create a new Apple Developer account. Upload an initial, benign app (e.g. a calculator) as version 1.0.0 and obtain TestFlight approval. Upload a second build: without changing the version number increase build number Change the app name to a well-known product (e.g. “ChatGPT”) Change the app icon to match the impersonated product Invite targeted email addresses to the TestFlight group. Recipients receive an official TestFlight invite and are prompted to install the impersonating app. ⸻ Expected results TestFlight builds that significantly change app identity (name, icon, branding) should: Require additional review, or Be blocked from distribution without re-approval. Developer accounts should not be able to impersonate well-known companies (e.g. “OpenAI Platforms LLC”) without verification. Users should be protected from installing TestFlight builds that materially differ from what was originally reviewed. ⸻ Actual results App name and icon can be changed between TestFlight builds without triggering additional review. TestFlight invites can convincingly impersonate trusted brands. Targeted users may reasonably believe they are installing a legitimate beta. This creates a credible vector for: Phishing (credentials, payment details) Data exfiltration Social engineering attacks I did not install the builds to avoid personal risk, but the attached artifacts should allow Apple’s internal teams to reproduce and analyze the behavior safely. Some more examples:

Hi, We're experiencing inconsistent and unexpected values returned by Storefront.current?.countryCode when running our app via TestFlight. In our case: The device region and locale are set to Poland The App Store account (Media & Purchases) is also set to Poland However, when running a TestFlight build, Storefront.current?.countryCode sometimes returns a completely different value (e.g. "NO" for Norway), which does not match the current App Store account configuration. Here's the code we're using: if #available(iOS 15.0, *) { let code = await Storefront.current?.countryCode print("Storefront countryCode:", code ?? "nil") } What's particularly confusing: Across different devices logged into the same App Store account, we sometimes receive different countryCode values The returned value does not seem to reflect the current App Store region or device settings We understand that Storefront reflects the App Store storefront and not the device locale, but in this case the value appears stale or incorrect even with a properly configured App Store account. Questions: Is Storefront.current?.countryCode expected to behave differently in TestFlight vs. production builds? Are there known caching or propagation delays for storefront updates across devices? Can TestFlight builds return outdated or inconsistent storefront values? What is the recommended way to reliably determine the user's App Store region in this scenario? We rely on storefront to determine regional availability of features, so understanding this behavior is important for us. Thanks in advance for any clarification!

Hello, I'm experiencing an issue with accepting testflight invitations. The workflow: Developer invites me through Connect I am receiving the email and clicking Accept Invitation The link opens testflight, however I am immediately prompted with a "Couldn't Load App: This invitation has been revoked or is invalid. Request a new invitation from the developer." I hope this gets resolved quickly, I need to join the app testing. Thanks

Hi all, I have a build in "Waiting for Beta App Review" that has been stuck for more than three days, well beyond the typical 24-48 hour window. Context: • Internal-use app distributed via TestFlight only (no App Store release). • Uploaded approximately April 18, 2026. • No ITMS warnings, no rejection notice, no request for additional information. • A newer build was uploaded today (April 21, 2026). It processed correctly and is also now awaiting Beta App Review behind the older one. • I noticed another forum thread referencing FB22543589 / Case ID 102872835864, reporting TestFlight builds being flagged as Expired/unavailable overnight between April 20 and April 21, 2026. I would like to rule out whether my submission was affected by that incident. Questions: Has anyone else experienced Beta App Review delays during the week of April 20, 2026? Beyond filing a Feedback Assistant report, is there a recommended escalation path for stuck beta reviews? If my pending build was affected by the April 20-21 TestFlight incident, does re-uploading resolve it, or does the new build simply re-enter the same queue with the same delay? I have also submitted a support request via the Contact Us form, but wanted to check with the community in case others are seeing the same pattern this week. Thanks,

Hi everyone, I’m facing a persistent issue where App Store Connect invitations are marked as "Invalid" or "Expired" the moment the recipient clicks the link, even if it was sent just minutes prior. I have already tried the following troubleshooting steps without success: Removed and re-added the user multiple times. Sent invitations to different email addresses (different domains). Changed the assigned Roles (tried Developer and Support). Tried opening the invitation link in Incognito/Private mode and different browsers. Despite these attempts, the link remains invalid. Is there an ongoing server issue or a specific workaround for this? Thanks in advance for any help!

I have an app that has suddenly gotten a non-public API error after uploading the archive to TestFlight. The error is posted in full below, and has never occurred before. I'm not using the _UIDeviceOrientationDidChangeNotification symbol but I do have two extensions that use UIDevice.orientationDidChangeNotification. However those extensions are not included in the target for the two watch extensions where the error occurs. Has anyone seen this problem before or have some advice? 90338: Non-public API usage. The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/watchkitappExtensionBeta: _UIDeviceOrientationDidChangeNotification,The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/PlugIns/watchkitappWidgetExtensionBeta.appex/watchkitappWidgetExtensionBeta: _UIDeviceOrientationDidChangeNotification. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

Hi everyone, I'm currently experiencing an issue when trying to submit my app/build via App Store Connect. Details: App name: Daily Habit Tracker 2026 Bundle ID: com.DailyHabitTrackerPro.2026 Case ID: 102871415765 Issue: Whenever I try to submit the build (TestFlight / App Review), I get the following error: "There was an error processing your request. Please try again later." This issue has persisted for several days. What I've tried: Retried submission multiple times Waited and tried again later Checked app metadata and settings Contacted Apple Developer Support on April 17, 2026 (no response yet) Question: Has anyone encountered this issue recently? Is this a known backend issue on Apple’s side, or is there anything else I should check? Thanks in advance.

I am unable to receive an invite email on my apple account in order to accept and get access to testflight for testing apps