I have an app that has been on the App Store for a few months now with about 6 previous updates that have gone very smoothly. I use Test Flight to test the app on my device before submitting. This time around everything looked fine on Test Flight as usual so I went ahead and submitted the app for review. It was approved and the status switched to ready for sale, however, when I tried to download the App from the App Store it said it was unable to downlaoad again with the options to try again or done. I have tried it on numerous devices and it appears to be a problem for everyone, not just myself. This happens even though the same build worked great with Test Flight. Can anybody help? A lot of people have failed to download or update their app and it is affecting us a lot.
Now, i understand that you have checked several devices and all got the same installation issue.
But i think, it is important for you to know,
You might face issue in installing app from App Store, with TestFlight build still installed in your device.
Please try uninstalling the Test Flight build first and then install app from App Store.
Related
I have a strange problem with my app. I have finished the design and I am ready to update it on the store however, when I do that and I test my app using test flight the app is completely different from the version installed from xcode.
Some colors are different the are bugs that are not present when testing it on xcode and even the status bar that I have hidden is now visible..
I have other apps on the store and i never experienced this isuues and I am sure that I am uploading them right version of their app..
What could be going wrong?
So I have two apps successfully submitted for TestFlight Beta Testing (See image below).
For the first one, installation works as expected. For the second one, the app appears "stalled" at around 90%. Never gets passed what's shown in the image. However, if I return to the home screen the app has installed (no install progress indicators on app icon) and appears to be functioning normally.
I receive no errors within TestFlight and no error logs are produced. TestFlight just never shows the "OPEN" icon for this particular app.
Some other External Testers are also seeing this so it leads me to believe it has something to do with my build and it could be something I can fix. (I do not know if all external users are seeing this issue). Biggest concern is this will happen to some users when the app is released in the App Store and they will end up losing their data.
I have tried deleting and re-installing the app with no success. I have also tried killing the TestFlight app process. "Stopping" the install simply shows "INSTALL" and reselecting gets to what's shown below. Version updates also display the same issue.
Anyone have any ideas on what may be wrong with this particular app?
#kanso already posted the solution. So be aware of using bad app version numbers ;-)
The issue was resolved using a build number that does not contain a '0' following a '.'
for example,
Build Version: 1.1.002 # no good
Build Version: 1.1.2 # WORKS
Ive seen this, and it seems a bug in the test flight app, since the applications seem to install properly as you mention.
You don't need to worry, it is a bug by Test Flight. People have registered their complaints. Hopefully, they will fix it soon.
I have done everything specified by Facebook. I even validated the sim build using the ios-sim tools and it runs fine on my Mac. There are no crashes. Has anyone had this problem before? What am I missing. here is a screenshot :
Edit I gave it another try and I got the same results. Even for the Android build. I was thinking tht maybe i sent them a zip by mistake but this time I double checked that I'm sending them a link to a .apk file to download from Mega.nz. Testing the iOS sim build on my end yields nothing since the game runs fine. I'm in dire need of some sage advice from someone who has gone trough this process. Here is another screenshot from todays rejection.
In my case I just set the app in facebook to be active for the public. This allowed my users to log in and share post, from the app to facebook. I'm Only missing the publish_actions permission. Just get your app approved on the app store and send facebook the link for that. Simulation builds just dont work for them
Dude I never tried it before but I read somewhere that if you are getting trouble to get approved by selecting iOS on submitting you can select Android as platform on submission and after approved your facebook integrations will be working fine for iOS apps too.
Doesn't cost too much to have a try ;)
I have a serious issue which I cannot seem to solve.
Recently I have made an update to an IOS app, and when testing in XCODE as both Ad-Hoc, Debug, and installing via the .IPA on a device the issue cannot be replicated. However when I download the app from the App Store, it crashes.
Does anyone know how this could happen, and any potential solutions? I am getting lots of complaints from users, and not sure what to do?
Could part of the binary upload have got corrupted?
Probably you always compiled your app in debug mode. But when sent to App Store you made a release compile. click the arrow in the run button select scheme and chose "release mode" and run your app it will probably crash.
check if you used NSParameterAssert as they are not called in release mode
I cannot say why your live App Store application is crashing and the debug version is not. Two possible solutions:
Crash reports:
To find out why your application crashed, you might want to check if there are any crash reports available on iTunes Connect. Log in on iTunes Connect and click on your application. Scroll down to Crash Reports. You will find out more about why your application is crashing here.
More information about crash reports here at Apple's own iOS Developer Library.
Prerelease your app with TestFlight: For in the future: test your application by uploading it on iTunes Connect and testing it with TestFlight first before submitting the application to the iTunes Store. This will save you a lot of (review) time if you find a error.
I realize this is an old thread but I had the same issue with my App that I released. Meaning it worked fine in testing, but when I released it it would crash. The culprit ended up being the fact that I am using In App Purchases. I have two items that can be "bought" but I had only enabled one of them. In testing it was able to read both of them, but with the release version, it was only pulling the one that was enabled down, creating the crash. The fix was simply enabling the disabled item. I didn't even have to redistribute the app, though I had to wait for it to "percolate" through... Anyway this may help someone in the future.
Check if your app is looking for too many IAPs.
I just had this problem and my problem was I had deleted an IAP from the App Store, but didn't remove it from the app code.
For some reason it only crashed when downloaded; I used a promo code to do this before launching my app.
Thanks to Tornado for the inspiration to try this variation.
I read in this Stackoverflow question that to simulate an app upgrade on an iPhone, you should install a new Ad Hoc IPA of the file via iTunes.
You can therefore check if the users data is still intact after an update.
I use TestFlight and quite often install new development versions of the app from there. Does this also simulate an app update?
You can test this by saving some data from the app, and doing the TestFlight upgrade. If the data are still there, then I think that shows that it does behave like an app upgrade.
When I did these sorts of updates, I think the data stayed, but I recommend testing to be sure.