When I submit the app to TestFlight beta review I get the error show on UI. (I filled all filed info in Beta Infomation) There was an error processing your request. Please try again later I was inspected Safari to see the detailed error and I got the below error. Failed to load resource: the server responded with a status of 422 () and the detailed javascript error componentStack: undefined errorCode: undefined message: "API Response Error: TF_BETA_APP_REVIEW_RESPONSE" stackTrace: "status code: 422 --- api correlation key: NZEKCTWMNANXDZVTRD3V4GNE3U" Anyone can tell me the problem and how to fix it. Many Thanks.

I'm the account holder I've using test flight a long ago, but today I faced this problem for my forst time The group is there but inactive ?!

Since updating to 14.2 beta 2 I see the following error when trying to sign in to the TestFlight App on macOS. "Password reuse not available for account" It seems like it possibly affecting the AppStore too, from the device logs I see: Error Domain=AMSErrorDomain Code=2 \"Password reuse not available for account\" UserInfo={NSLocalizedDescription=Password reuse not available for account, NSLocalizedFailureReason=The account state does not support password reuse.}" I've tried signing out of the App Store to fix it but now I can't sign into either the store of TestFlight. I've also tried, multiple restarts and safe mode. Things seem fine on other platforms. Is this a known issue? Are others seeing it? Any ideas for how to reset things or what the error might be referring to?

Does anyone know how TestFlight counts the number of installs, sessions and crashes? I'm seeing totally insane numbers. I don't understand. Right now for the latest beta it shows me: number of installs "-", number of sessions 19 and number of crashes 36. What's that supposed to mean? When I look at the individual testers, sometimes there's already complete crap there. For example, there is a user who has reached 1180 crashes in 13 runs. What? Can you imagine a person who runs an application 1180 times and it crashes? I don't. What's really best, TestFlight gives me almost no crash logs. There were a few from the early betas, but none the last few days. Do you know of any other tool from which I get consistent information on absolutely all crashes?

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 ?

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.

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.

Hi! I am creating a plugin that implements the In App Purchases and Subscriptions. I have done everything already and the only error I am debugging right now is with the validation of receipts. I always get status 21002 even the format is base64 already. I prefer to use the verifyReceipt as it is intended for my plugin. I have tried everything but still the response I get is status 21002 which is I know the data in receipt-data is malformed or missing. What can I do about this? Thank you so much in advance! This is my code too: (Objective-C) NSString *receiptString = [receiptData base64EncodedStringWithOptions:2]; if (!receiptString) { [self post_receipt_validation_result:@{@"status": @"error", @"message": @"Failed to encode receipt data"}]; return; } NSLog(@"Requesting to Sandbox: %@", receiptString); NSURL *storeURL = [NSURL URLWithString:@"https://api.storekit-sandbox.itunes.apple.com/verifyReceipt"]; NSMutableURLRequest *storeRequest = [NSMutableURLRequest requestWithURL:storeURL]; [storeRequest setHTTPMethod:@"POST"]; [storeRequest setValue:@"application/json" forHTTPHeaderField:@"Content-Type"]; NSDictionary *requestContents = @{@"receipt-data": receiptString}; NSError *jsonError; NSData *requestData = [NSJSONSerialization dataWithJSONObject:requestContents options:0 error:&jsonError]; if (jsonError) { [self post_receipt_validation_result:@{@"status": @"error", @"message": jsonError.localizedDescription}]; return; } NSLog(@"Request Data: %@", requestData); [storeRequest setHTTPBody:requestData]; NSLog(@"Store Request: %@", storeRequest);

Good afternoon, I have encountered a problem that I do not have the opportunity to select a build for external testing, but I can test the application through internal testing. How can we make testFlight let me choose the build I currently have?

Hi, I am trying to publish an update to my app, with security update which is a critical one, and to be published before Aug 2nd. I have uploaded required document for DSA, and it us under review. A build was uploaded to testflight and all process under QA is completed. Now I am trying to push the same build to publish as next version. I am unable to select the build from Testflight , which is valid for 58 more days. The radio button seems to be greyed out/disabled. Is it because documents of trader proof is still in review ? If not, What could be other reasons ? Please help to resolve this as we do not have much time left for publishing an update.

Hello, I have an issue with a build that was uploaded to TestFlight for internal testing, and now I am unable to select this build for submission to the App Store. Unfortunately, I do not have access to Xcode to create a new build. Is there a way to change the status of this build or submit it for review without needing Xcode access? Here are the details: The build was uploaded to TestFlight as an internal test build. When attempting to submit the build for App Store review, the build does not appear in the selection list due to its current status. I need to find a solution to either change the status of this build or use it for the App Store submission without generating a new build through Xcode. Any guidance or assistance on how to resolve this issue would be greatly appreciated. Thank you!

I can't update any apps unless I redeem a code for TestFlight. I have no idea where this code is. It hasn't been emailed to me. Can anyone help?

Hi Apple developer team, We contacted support and was asked to contact the developer technical team. We can provide Case ID if needed. We are having an issue we did not encounter before. Once we want to install or update our new test build in testflight we get the following error: App name could not be installed. The app is not availible or does not exist. We updated the app several times with new builds but the issue remains. Thanks Dieter

Hi, I have written my first iOS app, I would like some more testers though to find any potential issues or additional features which would be useful. I have put the public like below: https://testflight.apple.com/join/8xB5SEjs Thanks!

This is an ue5 generated xcode project that I have released to test flight. However the app isnt operating as it should. The app closes out when I try to open the main level. The tutorial opens with ease and my store to buy characters opens sometimes. I havent been able to get the main level to open without crashing but I have heard the sound of the main level opening sometimes before it crashes. The crashes aren't consistent and happen when trying to open levels in my game such as the store, tutorial, etc. This is what the crash log said on the right. Is it a shader issue?

I am getting an error when trying to install a new build via Testflight. The full error is: Could not install 'myApp'. Your request couldn't be completed. Try again. This has been happening for several hours. I tried to do a new build but I got the same error. I was able to download it on one phone but not the other so it isn't an issue with the build itself. Any ideas?

My game opens up find on the first playthrough. I can play on every map and level and everything is fine. However after closing out the app and going back in everything map/level crashes when I try to load into it. This also happens sometimes when I’m on the app for to long. Clearing the data for the app and restarting fixes the issue. What’s going on with my app is it using up to much ram? My app is made with ue5 and is on iOS 17.

We have an App in testFlight on internal testers. An admin user manages to install TestFlight, another Holder and Admin user is unable to install Testflight and has this message (TestFlight is currently unavailable. Please try again later.) Do you have any advice to give? Thank you

Is it possible to distribute apps using TestFlight with the distribution profiles created with Apple Developer Enterprise Program. If yes, can anyone provide the reference links. Thanks Abhilash Reddy

I'm seeing super weird behavior. The first build I distributed must have had some kind of glitch, because everyone who clicked a link was invited, but none of them accepted. (The users I added to the External testing group did accept and download.) So before I ship out a new build, I'm thoroughly testing the distribution, and I'm seeing really varied behavior. I'm in the internal testing group. So the new build -- if I understand correctly -- should just be in my testflight app. (I see the internal group listed under that build). But the build isn't in my app. I refreshed the app, still nothing. I waited a few hours and tried again. Nothing. (The new build has been approved, btw.) So, just as an experiment, I created a fake external testing group with just myself in it. Nothing. No email. Nothing new in the Testflight app. Then I added myself as an individual tester. I didn't get the build in the app, and I didn't get any emails. So I deleted myself from the individual list and re-added myself. That had worked once in the past, but this time, still nothing. I checked my box in the individual list. Hit the "invite" button. I did finally get an email! I opened the email on my laptop, and got the redemption code. But when I input the redemption code into Testflight, I got "Testflight is currently unavailable. Try again." (A few other experiments have also had this result.) (I've heard that this can be caused by a ")" in the app description. I don't have any weird characters in the description.) My mom offered to help, so I added her to my fake External group. She had had Testflight in the past, but had deleted it. So she redownloaded it, opened it. And the new build was just there!! No issue! She opened my app. No issues. So, I'm glad anyone can access it. But she's in the same fake external testing group as me. Why can she see it if I can't? (She also didn't get any emails. idk if that's the expected behavior.) So I deleted Testflight and redownloaded it. The new build isn't there. I added an old build to the fake external group, and I couldn't get it into my mom's phone. I opened the old invite email on my phone, followed the link (so no need to enter the code) "Testflight is currently unavailable. Try again." My iCloud isn't full. My email is the correct email associated with my account. My mom and my front end guy can access the app. But I can't, and my users who tried to use a public link couldn't. I enabled the public link in the test external group. It lead me to an old build (which I could already access) but not the new one. I deleted the old build from the group, and opened the public link. That gave me access to the new build! So, ok, progress!! But this is still a whole lot of weirdness. I'm not confident I'll be able to get the app into my users' hands. Any ideas? What the heck is going on with the external group? Am I missing something? And the "Testflight is currently unavailable. Try again." error? Also, does anyone know the expected behavior with emails? Thanks!