I'm trying to distribute our app on TestFlight. Although I have enrolled to the developer program. I get this error: I tried logging off and logging in again in xcode. But it didnt solve the issue. How can I solve this problem?

Beta testers outside the US, for our MacOS App, are being told their ID is not valid in the US Store and that they must switch to a store in their country. Yet the store switch fails Essentially beta testers outside the US cannot do testflight sandbox eCommerce for the Mac version of our app. Note that eCommerce on the Mac works for US based testers and eCommerce for the iOS/iPadOS works for testers in all territories. Many of these testers are in India, the UK and Canada. We believe that this is incorrect, that storeKit is not correctly detecting the AppStore Region for mac based testflight eCommerce. At this point we have 382 testers, most outside the US and we can only Beta Test our app with US users. Attached are images of the messages that are coming from storeKit: Here is a link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser) https://youtu.be/kB818wfVld4 Here is another link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser). https://youtu.be/7uAZKo8wpfU We see that there is another post with a similar problem. Similar eCommerce Problem Because eCommerce works in all territories on iOS/iPadOS but ONLY in the US for Mac we suspect that this is an error that either a DBA or a coder will need to fix. Any insights from anyone would be appreciated.

We encountered a weird situation recently. Our daily build process upload an app with a daily incremental 4-digit build number, e.g. 4000, 4001, 4002, etc. Our release build number has a specific requirement to use the date, such as 20240719. In the past I have learned that in order to upload a new build for the same version number, the new build number needs to be greater than the old one. Thus, if I have uploaded 200.1.0 (20240719), I cannot upload 200.1.0 (4001) anymore, because the daily build's build number is smaller than the release build. I have to expire the 20240719 build in order for the daily build to continue, which is fine. The problem is, yesterday I submitted 200.1.0 (20240719) for App Store review then got approved. While today's daily build is 200.2.0 (4001) and when it is uploaded, it got rejected for the following error message: This bundle is invalid. The value for key CFBundleVersion [4001] in the Info.plist file must contain a higher version than that of the previously uploaded version [20240719]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion With error code STATE_ERROR.VALIDATION_ERROR.90061 for id [redacted] Asset validation failed (-19208) This befuddles me, because the 20240719 build submitted for review is in an older release version, while the daily build 4001 is using the newer release version number. It seems that TestFlight decided to compare build numbers while ignoring the version numbers?! Furthermore, after I canceled my approved submission for 200.1.0 (20240719), surprisingly the 200.2.0 (4001) can be uploaded without an error! 😲 It seems that the only factor is whether the build is submitted or not. If an older version number higher build (200.1.0 (20240719)) is not submitted, then TestFlight happily allows newer version number lower build (200.2.0 (4001)) to be uploaded. In contrast, if submitted, then 4001 is not allowed to be uploaded! Is it an expected behavior? Thank you for the patience.

We recently submitted an app for external testing via TestFlight, but it has been stuck at the "Waiting for Review" status for several weeks. This delay is blocking our testing process and impacting our development timeline. Could you please look into this issue and provide an update on the review status? Thank you for your support.

Hi can i get the test flight invitation code

Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “ZigBank.app” bundle should contain a NSLocationWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources. Apple Developer Relations I tried defining the string explaining why the app needs the data but the error persist. kindly seeking your assistance to resolve this error.

We had send an app to Appstore. It was live. We removed it. After a year we decided to change the name, the name is updating in Appstore web, Invitation email received from Testflight is also new name. But when we tap on [View in TestFlight] in the email or the app name in TestFlight iOS app still shows the old name. We update the app info and all the other places. Different name in Appstore and Testflight app for the updated name.

Hi, Do we have any known issue with internal builds not being tagged properly as internal on TestFlight? Is anyone else having the same issue? Our team is not being able to do internal builds anymore since the last week or so. The last build we have that was successfully tagged as internal was on Wed Jul 3 00:15:40. After that mark, we can upload the builds and they show up on TestFlight, but they are not marked as internal and they can technically be used for a public release even though they shouldn't. We thought this could be an issue with our CI workflow, as we did some changes around that time, but we tried reverting everything or building from an older commit and the problem isn't solved. We even tried building and uploading directly through Xcode, without going through our CI or any external tools, and even selecting the TestFlight Internal Only distribution method, the builds are still releasable (not internal). On the CI side, we have confirmed multiple times that our ExportOptions.plist contains the expected key/value pair: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>destination</key> <string>export</string> <key>generateAppStoreInformation</key> <false/> <key>manageAppVersionAndBuildNumber</key> <true/> <key>method</key> <string>app-store-connect</string> <key>provisioningProfiles</key> <dict> <key>(redacted)</key> <string>(redacted)</string> <key>(redacted)</key> <string>(redacted)</string> </dict> <key>signingCertificate</key> <string>Apple Distribution</string> <key>signingStyle</key> <string>manual</string> <key>stripSwiftSymbols</key> <true/> <key>teamID</key> <string>(redacted)</string> <key>testFlightInternalTestingOnly</key> <true/> <key>uploadSymbols</key> <true/> </dict> </plist> We're unsure on what else to do about it, but we definitely would prefer to have internal builds not being releasable to avoid human error. Any ideas on what else we might be missing? Or if is this an actual TestFlight issue? Thanks

Can I request the Testflight redeem here? iIf not, can someone assist me how to get it? Thx

Здравствуйте,хочу получить код в девелопер

For example: The transaction id obtained by the app is: 2000000625603237 The transaction id notified by Apple is: 2000000625603236 Why does this happen?

I've already done my test on development signed app locally, all in-app purchase runs well with sandbox tester Apple ID. Errors happens when make a purchase in distribution app from TestFlight. Detail Info: in Apple Store connect , make app available to China Electron project, packaging by electron builder using distribution sign upload to TestFlight, invite myself to test using my Apple ID(not the sandbox tester) to login and purchase dialog appears and said "Account not in this store" VPN is off Apple Store shows Chinese language and Chinese apps, not llikely to be u.s. store I'm suspecting that: Maybe shouldn't use my developer Apple ID to run TestFlight test? TestFlight locked app to be in u.s. store ?

Hi, I have an app that uses a firestore database, throughout testing I had no problems. However, I released my app and it crashes all the time.when i distribute my app to testflight this will working on the 3 ios devices with same version but the app is not working on one device which have also a same version of ios. when i open the app the app will crash and not open. Here is a crash report I have. I am struggling to find resources online on how to interpret it but no solution found, so any help would be appreciated. Thanks so much for any help, You can see the error here

We encounter a weired behaviour after distributing our app to Test Flight. When building locally, everything is fine on our 12.5 test devices. After launching the app via Test Flight the app goes into the app switcher screen and is stuck there showing the miniature splash screen. Anyone encountered a similar issue? The app was build with Cordova. Thanks!

Hi everyone, My testers are not receiving their TestFlight invitation emails. Is there a service outage at this time? Is anybody else experiencing this issue? -Tyler

Hi Apple Team, I am encountering an issue when trying to add a group of external testers in TestFlight. The process prompts me to fill out the testing information. However, upon submitting, the API /iris/v1/betaAppReviewDetails/:appId returns a 409 error, stating that the phone number must be a number. Here is the request and response for your reference: Request: { "data": { "type": "betaAppReviewDetails", "id": "001000010", "attributes": { "contactFirstName": "Name", "contactLastName": "Surname", "contactPhone": "00900090001", "contactEmail": "me@email.com", "demoAccountRequired": false } } } Response: { "errors" : [ { "id" : "4f29f252-2ae2-467d-856b-861d3940cb0b", "status" : "409", "code" : "ENTITY_ERROR.ATTRIBUTE.INVALID.INVALID_PHONE_NUMBER", "title" : "An attribute value has invalid phone number.", "detail" : "The format of the phone number is invalid", "source" : { "pointer" : "contactPhone" } } ] } Could you please assist in resolving this issue? Thank you! Best regards, Moisés B. Almeida

I can't deploy new build. It's just staying "Processing" infinitely. Also whenever I add myself as an internal tester, it says resent but date stuck with previous sent email dates and never send invitation again.

I can't download testflight for some reason. Anyone have same issue?

Reason provided by the reviewer： We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue. Review device details: Device type: iPad Air (5th generation) and iPhone 13 mini OS version: iOS 17.5.1 apple crash log However, the app we downloaded through TestFlight runs normally on all systems without any issues. May I ask what could be the reason for this?

Hi, Im trying to upload my app to testflight and keep getting the following errors. I'm unsure of what to do. Would really appreciate any help! Asset validation failed Invalid MinimumOSVersion. Apps that only support 64-bit devices must specify a deployment target of 8.0 or later. MinimumOSVersion in 'AppName-App.app/Frameworks/FirebaseAnalytics.framework' is ''. (ID: 5c2f4b25-3b18-4417-8ea1-3fbe1819b235) Asset validation failed The bundle 'Payload/AppName-App.app/Frameworks/FirebaseAnalytics.framework' is missing plist key. The Info.plist file is missing the required key: CFBundleShortVersionString. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring (ID: bdd9b49c-beb4-4aa0-b44e-39ca394523c6) Asset validation failed Invalid Bundle. The bundle AppName-App.app/Frameworks/FirebaseAnalytics.framework does not support the minimum OS Version specified in the Info.plist. (ID: 32b88c27-d56f-44f9-a478-4d93edf94356) Asset validation failed Invalid Bundle. The bundle AppName-App.app/Frameworks/GoogleAppMeasurementIdentitySupport.framework does not support the minimum OS Version specified in the Info.plist. (ID: 941946b9-a781-4890-9cda-3485a7ce7854)