Our latest version passed review yesterday, and the beta testers (~10 people) received their notification that the build is ready to test on iOS. When they click the TestFlight link in the e-mail, it opens a screen that says: "Couldn't Load App. This build is no longer available." With a "Try Again" button. I have tried removing and re-adding all testers, and that didn't do much if anything. Also, a NEW tester that was only added to the new version could download it with no problem. This only appears to affect users that have an older version already installed?
Please help!
Instead of adding individual testers to the build, we started using the "External Groups" functionality in TestFlight. This seems to have resolved the issue for us, however there is still clearly an issue with individual testers getting access to successive builds.
Related
We have already deployed a number of versions of our app to Playstore when I tried to release a build a week ago , They Showed me a waring to declare the REQUEST_INSTALL_PACKAGES because it was present in our first Internal test build due to openFile: package.
But we have already removed it from our code atleast 3 months ago and the playstore is asking us to fillout a form explaining why we need the Install Package Permission and where we use it in our App. We don't actually use it on our app. can any of you help me with this I'm also attaching the form that they showed inorder to declare the REQUEST_INSTALL_PACKAGES permission.
I tried to release the latest version of our app to production just like I always do but they are preventing the release until I solve the issue sown in App Contents for sensitive permission declaration.It didn't happen like this before.
I'm trying to create interval test for my flutter app.
But Google Console is not publishes the new version of the app for testers.
I'm NOT publishing the app for the first time.
I have a previous version of the app that was approved.
However this is my first test for the app.
I strictly followed the instructions provided by Google.
What I did:
made a new release that I want to test
created internal test
added list of internal testers (all of them are approved now).
published the new version to internal test
copied the link and tried to get the test version of the app as an internal tester.
However I've downloaded the old version of the app.
I've also tried to create alpha and beta testing after that and provided them with new version.
But still got this problem.
What's more, I did some extra step to solve this problem:
cleaned Play Market cache on the device
downloaded another simulator to test the app
changed the version of the app and downloaded it again
deleted and added again tester list in Google play console
Screenshots:
https://github.com/asg1997/qu/blob/main/Screenshot_1639590890.png
https://github.com/asg1997/qu/blob/main/Screenshot_1639591139.png,
https://github.com/asg1997/qu/blob/main/Screenshot_1639591150.png,
https://github.com/asg1997/qu/blob/main/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202021-12-15%20%D0%B2%2020.53.20.png,
https://github.com/asg1997/qu/blob/main/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202021-12-15%20%D0%B2%2020.54.18.png
I searched a lot on StackOverflow and Googled a lot but I didn't find the exact answer I was looking for.
I recently submitted my application to the App Store review after several weeks of testing with TestFlight.
My application has been accepted on the App Store, and I indicated that I would like to do a manual release. So my application currently has the status "Pending Developer Release".
My build 1 is now ready to be released on the App Store.
The launch of my app is in a few weeks and I would like to have my build 2 (which already contains bug fixes) validated by the AppStore before the launch of my application. However, if my build 2 doesn't pass the App Store review before the launch of my app, I would like to be able to launch my build 1 anyway.
On the AppStore, I can't upload a new build if my old one hasn't been released. I have to cancel the already released build.
So I was wondering how to do this.
Can I, for example, validate my build 1 on the AppStore and set the availability to "no country"? and the day I launch, I just change the availability to "all countries"?
I hope I made myself clear!
Thanks,
Viktor
First things first , if you have a build with state Pending Developer Release for version (ex: 1.0.0)
you cannot upload a new build with same version (ie 1.0.0)
Or Else if you want to upload a new build with same version 1.0.0 you should cancel already approved build for version (ie 1.0.0) which changes the state of the build to Developer Rejected , in this state you can upload new build ( with probable bug fixes ) on same version (1.0.0)
If for some reason apple rejects your new build ( They inform why they rejected though), you cannot go back to already approved build.
Now if you want to release the build and make it Ready for Sale state then it's visibility in Appstore depends on Availability in Countries.
If you make Availability to none , then the build state for version 1.0.0 changes to Developer Removed From Sale ( No need to panic , if you add one or more countries in Availability the state would change to Ready for Sale state again)
However this makes you restricted from using 1.0.0 version again , so you need to use 1.0.1 or any new version greater than previous one.
If versioning is not an issue , you can release 1.0.0 and remove countries , so even if newer build (1.0.1) is rejected by apple , you can still release your app on the pre-decided date.
Hope this is helpful information.
Yesterday have I uploaded 2 builds to iOS beta testing platform - TestFlightApp. Unfortunately none of the testers, including me, can access those builds. It was working for us fine before.
I receive following message:
This device cannot install this build
TestFlight couldn't find the build you are looking for - perhaps it was removed
enter code here or you were sent an incorrect url. Check out your dashboard to see all your installable builds
Anyone received similar message ? Is it internal testflight problem, or something is wrong with my build ? How to fix that ?
It's happened to me as well, I got the message This device cannot install this build and the green button said Contact Developer.
After making sure that the user had register his device with test flight and that the device is also on the provisioning profile, I've removed the profile from the Settings app (by going to Settings>General>Profiles) and removed the Safari browsing data (by going to Settings>Safari>Advanced>Testflightapp.com)
Then I went back to the email and clicked on the link to install the app and that worked.
It may seem counter-intuitive (it was to me anyway) - even if you provision someone's device, you still have to check off each user on the permissions page and click "just update" before they can install an app, EVEN IF you already provisioned their device in the iOS provisioning portal.
I have a script working well for creating ad hoc iPhone builds. I can drop the app and mobileprovision file on iTunes (Mac version), and it installs to the device without a problem. But if I generate a new build and drop the files on iTunes a second time, I always get the dreaded "could not be verified" error on sync.
The only thing that fixes the problem is to delete the app and profile from the desktop and device, sync, and then drop the new copy and sync again. I've tried every variation of deleting the profile or app on only the device or desktop, and nothing other than cleaning out both will fix it.
Does anyone know if this a bug in the installation process for ad hoc apps, or am I missing something?
Are you changing your version for each build?
I don't remember getting an error message, but I found that if I did not change the version information each time, I could not drag and drop to install the new version. I would need to delete the app first.
Not sure if this will help, but it is the only thing I can think of so far.