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 channelyou can share your TestFlight Public Links with the developer communityto gather valuable feedback on crucial elementslike technical implementationuser experiencedesignand more. To maximize the benefits of posting TestFlight Public Links in the Developer Forumshere are some best practices to keep in mind: Provide details: Give comprehensive information about your applike new features and test casesand note specific areas where you seek feedback. The more detailed your post isthe 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.

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?

Hi everyone, I’m currently implementing Tap to Pay on iPhone following Apple’s official documentation. I’ve completed all the required configurations (entitlementscapabilitiesmerchant setupetc.) on the Apple Developer portal. Howeverwhen I archive the app and attempt to upload it to TestFlightI 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 understandthis seems related to the provisioning profile not including the required entitlementeven 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 scamspamand potentially malicious builds: I had reported this already in December last year via Feedback assistantbut since the malicious behavior has not stoppedI hope that you can forward my bug reports to the right team: FB21379977FB21845307 In multiple casesthese builds impersonate well-known apps (e.g. ChatGPTOpenAIMeta) by changing the app name and icon after an initial TestFlight approvalmisleading users into installing software from unrelated developer accounts. I believe this represents a systemic weakness in the TestFlight review and update flowenabling 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 initialbenign 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 (nameiconbranding) should: Require additional reviewor 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 (credentialspayment details) Data exfiltration Social engineering attacks I did not install the builds to avoid personal riskbut 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 Howeverwhen running a TestFlight buildStorefront.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 accountwe 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 localebut 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 featuresso understanding this behavior is important for us. Thanks in advance for any clarification!

HelloI'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 testflighthowever 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 quicklyI 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 dayswell beyond the typical 24-48 hour window. Context: • Internal-use app distributed via TestFlight only (no App Store release). • Uploaded approximately April 182026. • No ITMS warningsno rejection noticeno request for additional information. • A newer build was uploaded today (April 212026). It processed correctly and is also now awaiting Beta App Review behind the older one. • I noticed another forum thread referencing FB22543589 / Case ID 102872835864reporting TestFlight builds being flagged as Expired/unavailable overnight between April 20 and April 212026. 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 202026? Beyond filing a Feedback Assistant reportis there a recommended escalation path for stuck beta reviews? If my pending build was affected by the April 20-21 TestFlight incidentdoes re-uploading resolve itor 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 formbut 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 linkeven 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 attemptsthe 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 belowand 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 abovealtering your method names will help prevent this app from being flagged in future submissions. In additionnote that one or more of the above APIs may be located in a static library that was included with your app. If sothey must be removed. For further informationvisit 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 172026 (no response yet) Question: Has anyone encountered this issue recently? Is this a known backend issue on Apple’s sideor is there anything else I should check? Thanks 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 Connectbut 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 buildRelease 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 brieflythen fails with the "not available or doesn't exist" error This affects all internal testers on the accountnot just one device Troubleshooting already completed: Verified code signing is correct: Release configuration uses CODE_SIGN_STYLE = ManualCODE_SIGN_IDENTITY = "iPhone Distribution"with a valid App Store distribution provisioning profile (UUID: 39bc4c63-bc64-403a-a2a6-6737b3d33115) 2. Distribution certificate is valid: Serial 4838CD7571DE5361B98A5FB2F769F74Dnot expired (expires 2027-04-16) 3. Regenerated provisioning profile via EAS credentialsremoved stale profilesand 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 3006but 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 casesApple Support resolved the issue on their end within 48 hours with no action required from the developer. The signingprovisioningand 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 sidewithout 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

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

Hi, I’m having an issue where my auto-renewable subscriptions keep detaching from my app version after I submit the build in App Store Connect. Details: App ID: com.growthsync.app Platform: iOS (Capacitor build) Using auto-renewable subscriptions What’s happening: I attach all subscriptions to the app version under “In-App Purchases” Everything looks correct before submission After submittingthe subscriptions become detached or require localisation to be re-entered again This happens every time I resubmit Additional issue: Subscriptions are not working in TestFlight either It feels like they are not properly linked to the binary What I’ve already checked: Product IDs match exactly in code and App Store Connect Subscriptions are in the correct group All localisation fields are filled within character limits Products show as “Ready to Submit” before attaching I reattach them before every submission Questions: Why would subscriptions repeatedly detach after submission? Is this a known App Store Connect issue? Is there a specific order required when creatinglocalisingand attaching subscriptions? Could this be related to the binary not recognising the products? This is currently blocking release so any help would be appreciated. Thanks.

Hi everyone, I’m currently facing an issue in App Store Connect when submitting a build to TestFlight. When I try to complete the “What to Test” section and submitI get the following error: “There was an error processing your request. Please try again later.” Case details: Case ID: 102871190604 Submitted: April 172026 (GMT+7) Status: No response after 3–4 days This issue is blocking me from submitting the build. What I’ve tried: Retried multiple times Switched browsers (ChromeSafari) Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked build is processed and not expired I have already contacted Apple Developer Support but haven’t received any response yet. Questions: Is this a known App Store Connect issue? Should I wait for supportor upload a new build? If any Apple staff could help check this caseI would really appreciate it. Thank you.

Hi everyone, I’m getting this error in App Store Connect when submitting a build in TestFlight: “There was an error processing your request. Please try again later.” Case information: Case ID: 102871415765 Contacted Apple Developer Support: April 172026 (GMT+7) It has been 3–4 days with no response so far Where it happens: App Store Connect During the “What to Test” step The build is already processed and available What I tried: Retried several times Switched browsers Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked that the build is not expired This issue has been blocking submission for several days now. Has anyone experienced this recently? Is there any workaroundor should I upload a new build? Thank you.

For the past couple of days having a problem with Xcode 26.4. When I try to upload an archive to App Store Connectit gets stuck on "Uploading". I see the progress bar about 70% fulland a "Preparing to upload xxxx.ipa" label below. Letting it sit overnightrestarting Xcodemachineetc. and the same result. Anybody else seeing?

Hi everyone, I’m an indie iOS developer working on Kleioan AI voice keyboard extension that lets you dictate text quickly anywhere you can type. I’m looking for a small group of beta testers who are willing to try it through TestFlight and share feedback about stabilityUXand accessibility. What Kleio does Adds a custom keyboard so you can press the mic button and dictate instead of typing. Uses AI to turn rough speech into cleaned‑upproperly punctuated text. Lets you pick different writing s (e.g. more formal vs more casual) for how your dictation should read. Supports a personal dictionary for custom words and names. Keeps transcript history on‑device by defaultwith optional cloud sync and improvement sharing. Includes a “Privacy Mode” toggle when you don’t want anything uploaded. What I’d love feedback on Onboarding flow for first‑time setup and keyboard enabling. The dictation experience inside real apps (MessagesNotesMailsocial appsetc.). Latencyaccuracyand how well the edited text matches what you meant to say. Keyboard layoutbutton placementand any confusing interactions. Accessibility and inclusion: How well it works with VoiceOver / Switch Control. Any issues with contrasttouch targetsor labels. Any specific needs for users who rely on voice input more than typing. TestFlight link You can join the beta here: https://testflight.apple.com/join/jGY1fZ7S External group: “Twitter” (currently around 9 testers). No login is required for basic dictation; some settings sync features use account sign‑in. How to send feedback Through TestFlight’s built‑in feedback / screenshots. If you run into crashesunexpected latencyor accessibility problemsdetails like device modeliOS versionand what app you were dictating into are extremely helpful. Thanks in advance to anyone who’s willing to try Kleio and help me make the keyboard more reliable and accessible.

Hi, I’m experiencing a server-side error in App Store Connect when trying to submit a TestFlight build for review. Details: App: Ngoc Rong 2 Platform: iOS Build status: Complete Distribution: External Testing App Store Connect Web (Safari / Chrome both tested) Steps: Go to TestFlight → Select build Click “Submit for Review” Fill in “What to Test” Click Submit Result: Popup shows: "There was an error processing your request. Please try again later." Notes: Build processing completed successfully Internal testing works External group already created Issue happens consistently Tried different browsers and cleared cache Same issue across multiple builds Is this a known App Store Connect issue? Is there any workaround? Additional information: I have already contacted Apple Developer Support. Case ID: 102871190604 If neededI can provide further details or logs. Thank you.

Hello, I have an issue with In-App Purchases during App Review. In TestFlight and Sandboxeverything works correctly: Products are loaded Subscriptions are visible Purchase completes successfully HoweverApple reports that the purchase fails during review. My subscriptions are: Created and active in App Store Connect Attached to the app version Paid Apps Agreement accepted I also added all required information (pricedurationEULAprivacy policy). Why would purchases work in TestFlight but fail during App Review? Thank you for your help.

Hello, I made my app icon with Icon Composer and added the .icon file directly to my Xcode project. I noticed that the icon preview in Icon Composer looks one waywhile the icon shown on the App Store looks different. Details: I am using the .icon file directly in the project I am not using an exported PNG for the app icon I did not add a separate background image The background was set with fill in Icon Composer The preview in Icon Composer looks as expected The App Store version has a different appearance I would like to ask whether this difference may come from: App Store processing caching or a recommended Icon Composer setup for background fill If anyone has seen something similarI would appreciate any guidance. I can also share screenshots of the Icon Composer preview and the App Store result.