Itunes connect / Testflight app always shows old version (even if we upload new one for testflight)

we scratch heads

we worked with a new testflight / itunes connection and were able to submit builds for internal users. anyway, it stops working and it always goes to the old build when we release.

in preleases, we see that all versions (1.0.7, 1.0.7.1 โ†’ 1.0.7.7) - all other versions are inactive. every time we release testflight the corresponding internal users receive an email (invite to use the latest build), but when we open it with testflight it always allows us to install 1.0.7.3).

I asked an apple about it, but they didnโ€™t answer like a week and a half.

Has anyone else had this problem?

+3


source to share


3 answers


I was able to resolve this by clicking and turning off "TestFlight Testing" and then turning it back on.



+5


source


What worked for me was navigating to users -All in the left Testflight menu in Appstore connect and deleting the user there. Then go to the remote build and add them again.



0


source


Not sure if this helps, but I had a similar problem with my Testflight always loading the old assembly and it had to do with how I previously wrote the version.

The previous version was 0.58 and my last build was 0.7. For some reason, Testflight would recognize 0.7 as the newest version if it was written as 0.70. Seems to be an annoying error in my case.

0


source







All Articles