Below you can see that testing for external testers are turned off:
same for internal testing:
but when I transfer app, one of the criterias are not met:
Why?
I had the exact same issue, resolved by removing all Tester and Build from the TestFlight as discussed above also (!important) remove everything fields at the App Information - Test Information.
For me it was localised test descriptions. Make sure you check that drop down list on the right and clear out info for all languages.
I just solved the transfer issue, you just need to expire your build from tester by following the steps below. and then app will available for transfer..
open your app and click on testflight then click on the icon of your app as shown in below screenshot.
The click on expire build.
Now you can transfer your app :)
I've search for a long time and to me this worked:
Clean all builds inside: My Apps --> App Name --> TestFlight
Go to: Itunes Connect --> Users and Roles --> Tab "TestFlight Beta Testers" and click in the name from another user that isn't you.
Save.
Go back to the App in Itunes Connect: "Itunes Connect --> App Name --> Transfer App" and attempt to transfer again by clicking in "Transfer App".
To me this works. Hope help someone.
i had the same issue i deleted (mark expired) all the versions of app testing version in App TestFlight section and done the trick for me ;) attach is the screen shot of activity.
Another possible reason:
When you delete all test information from TestFlight, make sure you delete it for every language.
In the testinformation page, select every localised language and check if the form is empty.
I struggled with this for an entire day, I tried everything and finally found another workaround:
1) Expire all the builds
2) Delete all testers
3) Clear all the informations in the Testflight tab
4) Delete all langages except the main one
And finally the step which fixed the Testflight criteria for us
5) Create a new app version (no need to submit or even edit it)
now you check transfer.
Good Luck.
I know it's an old question, but it still bugs people to this day.
So the solution here, after you have removed all the testers, and expired all builds, go to TestFlight > Test Information and clear all the fields.
Also make sure you delete any localization you might have there. Give it 5 minutes, after which transfering will be possible.
Not sure if this is going to help,
Check Users and Roles > TestFlight Beta Testers
Do you have a tester who is testing the app that you want to transfer?
I have the exact same issue and I'm currently getting from Apple "our engineering team is still working diligently to have this resolved for you". I have been supplied with a workaround:
Enable TestFlight by adding a tester to a build
Then deactivate the build, by turning off TestFlight beta testing
Attempt to transfer again
unfortunately, I still haven't been able to resolve the issue.
We found that in addition to the other answers here, logging out and logging back in to iTunesConnect allowed us to continue after it was saying TestFlight was still enabled.
I was facing the same issue, going inside tranferring app console multiple times automatically fixed the issue and started showing all criteria as met.
Do the same step as #Imran Iqbal answer, if your app is Sign-in Required, uncheck Sign-in Required also, like:
then, you can transfer app.
I've exactly the same problem and could not solve it. The good news: After contacting Apple, they have confirmed a bug and they're working on a solutions. Apple confirmed also, that many developers ran into this.
Got that workaround from the support (that did not work for me):
1. Enable TestFlight by adding a tester to a build
2. Then deactivate the build, by turning off TestFlight beta testing
3. Attempt to transfer again
It looks like this is being done on purpose for new apps.
Now, A newly created app CANNOT be transferred into an account, until 14 - 21 days have passed.
An expiration period.
First, You must remove all build and user from TestFlight of that app. After its looks like below.
If you still not match last criteria than Sign Out and login again.
Creating new app version did it for me! Thanks!
The tricky solution is to enable testing again, add some tester in. The visit the TestFlight and under test flight users, you will see old active test flight users. Simple delete them.
Related
I have a Flutter developed App that I want to upload for App Store Review.
The App has been successfully uploaded through Xcode as you can see here— https://prntscr.com/26m7w94
Sadly, the Build doesn’t appear in my App Connect Build section as you can see here— https://prnt.sc/26no755
When I try to re-upload, it let’s me know that the Build is already uploaded to App Store Connect as you can see here— https://prnt.sc/26no84v
I have written to Apple and I don’t understand the answers they are giving me. They are just talking off-point.
Now I have waited for 8 days for this build to appear, but this uploaded build is not appearing.
Without this Build appearing, I cannot Submit to App Store Review.
Everything in the App Store Connect Form has been completely filled. Only Build remains to be added as you can see here— https://prntscr.com/26no94s
I can’t figure out what to do next, and this is 8(eight) wasted days gone by, with me not knowing what next to do.
Has anyone here faced this kind of problem before? How did you solve it?
Regards
Check in the TestFlight section. There might be a yellow triangle next to your build. You may need to answer some additional questions such as encryption usage etc. Just click on the triangle to answer and your build should be available afterwards.
Sometimes the answer to this issue is that there is actually a problem with App Store Connect (like right now).
You can check for issues on the Apple Developer System Status page.
For me changing the version from X.X.X to X.X.X+1 (2.2.2 -> 2.2.3) fixed the issue.
Sometimes it happens and I have also faced this problem .I successfully uploaded my bundle from Xcode but not found in connect.
I waited 30 minutes and refreshed .Then my bundle came in App Store connect.
Solution 1 : wait for some time & Refresh ,
Solution 2 : Create another Bundle and push to connect using Transporter (You can download transporter from appStore)
If the build doesn't show up on App Store Connect. You may want to check your email (the one you used as your Apple Id when uploading the build).
In my case Apple sent me an automatic email telling me that my build had some issues. Xcode didn't complain about anything and neither App Store Connect.
UPDATE: This might have boiled down to timing. After changing the version number to 1.0.0, that build showed up immediately. Half an hour later, the 0.0.1 build appeared out of the blue as well.
If you've set your version number to 0.0.1+X because you thought that makes sense while the app is still under development, change that back to 1.0.0+X. The upload will succeed, but app store connect won't list the build without a leading "1." in the version number.
Make sure no webviews are used in your app. It will not show builds in App Store Connect and neither XCode nor Apple will say that anything is wrong.
I have already published my app to the app store. I have already a couple of versions. I created an internal test group and an external test group.
Today, I published a new version of the app to App Store Connect, which I want to add to the internal test group. But somehow, I can't select it. When I go to the Internal Test Group, there is no (+)-Sign next to Builds. When I go to the external Test group, there is. And when I select the build and click on the (+)-Sign next to Groups, I can't select the internal test group.
I checked the build version. I should have incremented it correctly. I also tried to disable the other builds, but it still didn't work.
Here are some screenshots:
Any ideas what could be wrong here?
Okay, it seems the new build is added to Internal Testing automatically, and it just takes some time. So this can be closed.
Simply create a new internal Group with manual distribution mode. Then you can select Testers and Build to test easily.
Once you have a manual distribution group and testers received build, you can create a new group with automatic distribution.
If the build is taking too long to be made available, I've found it helpful to submit a new build to re-trigger App Store Connect flows.
Filling up the test information solved the problem for me. Go to > Test Flight > Test Information > Review Notes. Just added "Test" and saved it, the build magically appeared right after.
The same happened to me as well, looks like a bug in test-flight, what I had to do solve was following :
Create a New External Test Group with one or two internal users itself.
Assign the build to this new External Test Group.
Right away the same then reflects for internal users also ( wanted to achieve this only ).
Delete the External Test Group created in Step 1.
Berk's answer works on our case too. Thanks a lot!
After downloading the version now enabled for AS testers, i noted that Apple added a couple of new screens before our app is shown for testing. More like splash screens showing what the developers have said to testers in the Test Info box. In this case it's simply "test".
Looks like a bug on testflight that should have made this compulsory before allowing ppl to upload a build.
In my TestFlight, I have more than 50 builds for Internal & external testers as well.
Today I uploaded a new build ver 2.5.1 from Xcode (My last ver on Apple store is 2.5). The build has been upload & I can see my build has been processed under 'Activity' tab but when I am trying to load 'TestFlight' tab, I am getting a blank screen as below, none of the builds are visible.
I have tried to open iTunesConnect on Safari, Chrome with the different type of user access (Admin, developer) but still getting the same screen.
Is this something wrong with Apple (I am trying from last 3 hours) side or I have to make any provision from my end.
Please suggest.
I've had the same issue and could only fix it by contacting Apple directly. I've requested a call through their "contact us" (on iTunes connect, not the main website) and got a call within a minute.
After explaining to the attendant my case (mentioning that there's a javascript error on the developer console!) she immediately sent a ticket to the iTunes Connect team and it was fixed one day later.
I had build problem regarding Testflight.Once I uploaded on testflight the build could not been appear for a day.So I had contact with apple guy.
https://developer.apple.com/contact/#!/topic/select
Raise your queries here, they will definitely resolve your problem.
Hope this link will help you.
Here is my answer,
I tried for the whole day but Testflight was not loading.
I did try after 10 hours in midnight and I found all my builds are visible & Testflight is loading.
I think there was some issue from Apple side & they did fix within a day.
I also found a link discussing the same issue
https://apple.stackexchange.com/questions/308244/testflight-tab-doesnt-load-in-itunes-connect
I'm not able to transfer my application to iTunes connect. It is said that I have to disable my Beta testing of the application. Actually, I have stopped testing, deleted all builds from beta testing. App was set up for only internal testers. I have removed all testers as well. But still same issue. Here is the snap.
I spoke with an Apple representative on the phone regarding this issue. They are aware of this bug and working on it. That's all she could answer me.
Try again next week, if the issue is still there (which probably will be), I had to call again...
Pay attention to application localization. If your application has support multi language, then you could leave the information in the TestFlight menu.
You must delete the test information not only from the main language, but from other languages that are supported in your application. Go to TestFlight tab -> Test Information. Then click blue button with your language in right side of webpage. You shall choose other language supported in your application and remove all appeared information about testing. After this, click Save button (see attachment)
And try to transfer app. Next to the text TestFlight Beta Testing should be a green checkmark.
P.S. This solution was suggested by the Apple Support Team. Here is a part of their letter:
After checking your iTunes Connect account, we could see that you have
started to test a build internally, and you still have a feedback
email listed under Test Information in the English (U.S.)
localization. Therefore, I would kindly ask you to expire the build
and remove the feedback email.
After you have followed the information above, you should be able to
proceed further with your transfer.
Remove all testers and all testing information from the application in iTunesConnect on tab TestFlight.
You need to remove all testers, all builds (detail each one and expire it) and remove all information about how to test the app. I did this and worked for me.
I was able to fix this bug going to TestFlight section in Appstoreconnect and in Test Information switch to another language and clear all field also there.
Had the same problem.
If nothing helps, maybe these steps will help you.
You have to go to the TestFlight tab, then Test Information, and in the top right corner press language button. If you have more than one language, delete them from the list.
For this App, the first time that I uploaded the binary the 'External' column correctly presented the action 'Submit for Beta App Review'...
After clicking on it, the App got successfully reviewed...
After that, I sent another binary for a new version and now the column 'External' remains Inactive...
PS.: I have added external users(the status remains 'Added') and I have also filled in all information in 'Build Details'.
Other Apps in my account are working correctly, only this one has this issue.
How do I fix this? Is it a known issue in iTunes Beta Testing?
Any help or guidance is really appreciated... Thank you for your help in advance.
Apple have fixed the issue, my 1.1 version had the same issue but the submit for review button is now available again.
I asked apple developer center, and they confirmed it is true that external beta test can only be used for the first time currently.