Update for my app on appstore was just accepted by Apple (and held by developer==me because i used this option when submitting app to review).
If i release this version to appstore, is it possible to switch back to older version (also approved by apple) without submitting it again to review?
Its not possible. You can submit the old version if you have your source code for old version. You can change the version to new one and compile source, submit to App store. I don't think they wont review it.
No. It is not possible to revert to a previously submitted version.
Related
I have an iPhone app that was accepted in the App Store almost a month ago. Now i have updated my app with some new features and added iOS 7 support etc.
This is actually the first very first time i am going to submit a new version of the same app to the App Store.
As far as it seems, i have to go to iTunes Connect > Manage Your Apps, select the app and then click on "Add Version" and add the version number and whats changed in the new version. Go back and add the updated screenshots and then using Xcode, i can submit it for the approval.
The question is that is there anything else that i am missing and that i should do in order to submit the new version of the app? As i said i am doing it for the very first time. Thanks!
Things you may wan't to consider:
submitting any new in-app purchases with the new version of the app
make sure your app version and short app version is higher than the one in the version currently in the app store, otherwise you will not pass validation
run validation before submitting so you can see if you get any warnings, sometimes there may be collision with Apple private apis. If they are in your code, I'd suggest to rename your methods
The only thing you need to do now is to update the version number and the build number in your Xcode application, archive your app and submit on the AppStore.
On iTunes Connect you set the new version number :
Is there any way to test the unreleased build on itunesconnect after Apple certified?
Following article shows how to get the unreleased app but just works on the very first version
"Is it possible to get App Link for App which is not approved yet? (http://www.cocos2d-iphone.org/forum/topic/10044)"
But my issue is there's already some old version on the Apple Store, and I just submitted a new version, this version was passed by Apple certificate but not released yet.
As the concern is after I release it, any issue happened on this build was not revertible.(After Apple certificate and encryption, sometimes the app will perform not exactly like what your debugging build, I just suffered a lot from this issue, that's why I want to check the real final build)
I'm not sure, but I think there is a way to do this by redeeming the app with a promo code. Apple allows this so you can send it to testers and app reviewers before you release.
I have an app in apple store, I want to update it. But instead of working on old project, I created a new project and now it is finished. If I upload the new one, does apple reject it because of different sku and appids. Older version was very bad and I created totally new app. What should I do to update my application?
In your apps Info.plist, you want to make sure that the Bundle Identifier between the two apps match, and that the new app has a higher version than the old app. Then you should be able to successfully submit your new version to Apple.
I think you need to make sure:
your application identifier is the same
you sign it with the same developer certificate/identity
new version > old version
I just got my app approved....but realised there is a bug that will need a small fix. I do not want to release this app with the bug.
I am unsure how to get this fixed. If I submit another binary it will go through the review process again. I will also need to put a new version (1.1).
If I still have to submit a new version, can I directly release the new version (1.1) and completely ignore version 1.0?
Thanks in advance for advise..
pm
You would have to reject your binary for 1.0 and resubmit either a 1.0 or greater binary.
You can set the release date of an approved app into the future and then submit an update. If the update is approved, pull the release date back. The current version need never be visible in the App store.
If you put in your comments field that this is a critical bug fix, then there is a possibility (but no guarantee) that the review period may be a few days shorter.
You don't need to change version. You can keep version 1.0 and change build 1.1. Then Submit app for review process.
If your application has been approved, then it's available in the appStore.
The only solution for you to fix this bug is to send a new version of your application with unfortunately the Apple review process. (We just got the same issue)
From here, 1.0 will be ignored for new downloaders and those who have installed it would have to update the app.
I submitted an update for one of my iPhone apps last week and just realized I forgot to change the bundle version in Info.plist before I submitted. The update fixes a critical bug, so I want to get it into the store as soon as possible. The app update has not been approved yet. I am debating on replacing the binary with the updated bundle version or leave it.
What are the consequences of leaving the bundle version the same as the previous version of the app?
Apple may not accept the update as the bundle version is the same as what is currently on the app store
If it gets through Apple, iTunes will not automatically download or synchronize to the phone (you can see this behaviour using an ad-hoc distribution)
I'm surprised it even got through. I forgot to do that once, and itunes connect wouldn't accept my binary. I'd say you should leave it as it is, since you probably did change the bundle version in itunes connect, when you were uploading the binary, and so it should all work out. I'm not exactly sure though, cause I'm surprised it is even possible.