When my app got accepted to the App Store, it would download the newest version 4.1, immediately after the download is complete, it shows an update is ready, but it shows the update to be 4.1 as well, This is not Apple's fault as I have read before, I assume it is my fault. Why? Well, because this isnt the first time it has happened to me, I uploaded this same app version 3.9 and it did the same thing, but I never found out how to fix it, so i worked on an update for some minor bugs and hoped that when I re-uploaded it, it would get fixed. Does anybody know of a reason for this?
Thanks
You may be downloading it too quickly. I have experienced that the meta data will update before your app in the store so if you download it right away you may be getting a previous version. After a little time passes it will update the download and then give you a notification that there is an update and download the recent version.
Related
My App is approved, but the updated version is not showing in the AppStore and in iTunes. It is still showing previous version(1.1). Can any one knows why this happens?
I too faced the same issue recently..
I requested the apple to fix my issue.
i received the responce as follows
However, as you've discovered, this process can sometimes take up to 24 hours to fully take effect. As such, I thank you for your patience.
We have submitted an update version of our existing applications in the App Store recently. But we have received a issue from one of the users, saying that the app is not functioning properly after the update. So in order to replicate the same, what are the steps to reproduce, so that i can analyse the issue?
Any help will be appreciated.
To simulate this before pushing yoru updated version to the AppStore you can:
Download the old version of your app from the appstore
Run the updated version of your app from XCode on the same device.
What will happen behind the scenes is that your app will be updated in a way similar to the Appstore. Your app will be partially updated while your doucments folder will stay the same. (what usually causes problems)
This solution is better because it lets you check for problems before and update was pushed to the Appstore.
Yeah, I get this a lot. The solution is a bit annoying, but you need to keep a history of IPAs you've submitted so you can put the on your phone through iTunes (so not the simulator) and then, run your code on your device putting a breakpoint on your applicationDidFinishLaunching handler in your app delegate, and start tracing from there. You should be able to find the old app store version in your organiser from the last time you submitted, or, go through your SVN/GIT history and checkout the version tagged to your release version.
Many times in the past that has happened to me where I test a new revision and everything looks fine but when I submit an update and is approved, users start complaining about a crash or lost data.
This is way I approach the problem.
(This is most important step) You need to either have your old code or old binary installed on your actual apple device. (Physical iPhone / iPad)
Now go to iTunes and install your new update.
Attach your physical iPhone / iPad to you computer, Launch Xcode and start debugging it.
NOTE: There have been many times when things work perfectly in the Simulator but break on the actual device. Its always important to test your code on the real thing as that is what the users are going to be on.
All that is required is to have the version of the app that is in the app store on your device, then install the updated version to your device. You can debug it using Xcode when you install the new version.
I have a big problem. My app got accepted for an update. It downloads the old version even though it is showing the new screen shot of the new version. (No biggie, I have read that it sometimes does this.) But as soon as i download it on my iphone4, the store gives the little red badge showing an update is needed, which is for my app. I download the new update, It gives the first page's new graphics, but as soon as i try to do anything in the app, it crashes. But it downloads the correct version for my iPhone 5!! D: I have tested everything on both devices. And everything worked perfect. Thanks in advance!!!
Kurt
Wait a day. It should adjust. Otherwise email apple support. Most likely won't take more than a few hours
It can take a bit of time for the new version to propagate through all the various Apple store servers. If you try it now, you're very likely to get the new version in all cases of downloading from all locations and stores.
I've just got an app in the app store and realised theres a spelling mistake on the first view! As the app is intended for an upcoming event occuring in 3 days I am nervous about uploading an update. If I upload new binary to iTunes Connect will that mean my previous version will not be available on the app store? Also, will I need to have Apple approve my latest version prior to releasing it?
Any advice would be awesome, thanks!
When you push a new update it has to be reviews but will likely take more than 3 days to do so. While it is waiting to be reviewed your current version will be live.
Don't worry, your previous version won't be affected. Just upload the new one, but know that it's gonna take more than 3 days (pretty much always 7, if you submit during work hours). You can file for an expedited review, but even that can sometimes take more than 3 days.
And you don't need to remove the old version to put in the new one. You just submit the new one. You can determine whether you want it to automatically become available on the app store as soon as it's approved, or give it a specific release date.
Just know this: If your update has issues and you're forced to remove it AFTER it has become available on the app store, then you can't just revert back to the old version. You have to resubmit the old version and wait a week for that to get reviewed again.
Our latest app was rejected by giving following reason
"when the user launches the app, a blank black screen is produced"
We had tested this many times and did not notice this issue. We tested again now, but it is working properly for us.
Can someone help us to find out the issue?
I don't think anyone can help you find this issue, My suggestion would be to follow up with the Review Team and try to obtain as much information as you can from them. Such as, what device was it tested on, what OS version and so forth.
Ah, the many woes of the app store process.
Make sure that you have tested your app not only on the simulator but also on a physical device.
Secondly the issue might be that you have made some (false) assumptions about the data on the device, that you might have put there manually, but isn't handled when installing anew.
Therefore a plan of attack might be to remove the application complete from both device and simulator and try running them from a fresh install rather than on top of an already installed installation.
Best of luck!
Try to build and install your app from a clean state. You may not be seeing the same as the reviewer, because if you only "build&run" all the time, old files, which are not part of the final build, are still present on your device or in the simulator.
So clean the build folder, remove the app from your device, and try again. Also, check if you app can live without an internet connection.
Your best bet is to discuss this directly with the Apple guys (Resolution Center).