I have an app that has a great version 1. Very few bugs, etc. I sent in a update (2.0) and it's extremely buggy and apple accepted it. I didn't know it was that buggy when I submitted it - so I changed the availability date to the future. I am working on fixing it.
So my questions is - Can I delete this 'buggy' v2 and revert back to v1 so my app won't be off the market like it is now?
On the versions page, it will only show version 2 and a blank spot to add a version. Was version 1 erased?
Been searching for about an hour and haven't found anything yet. Thanks in advance! Coulton
If you have not yet released version 2, then Apple still has the binary for version 1 and you can delete the binary version 2 and/or resubmit it at a later date.
If version 2 is released already (folks can download it from iTunes), then Apple no longer has version 1. In this case, you could release version 2.1 and have the app be the version 1 release, but you'll have to re-upload the binary for version 1 (hopefully you archived it). A poor but possible option is to release a new version 1.1 that is the old version 1 and have this replace version 2. Apple does not require version numbers to ascend (though good sense does, but you may have a strong case in this situation).
If the app binary is already sent to iTunes Connect, but not been approved, do the following to get it "rejected by developer" (so you can upload new binary):
Step by step
In iTunes Connect click "view details" on the new version
Click on "binary details" to the upper right
Then press a greyed button to the upper right to reject the binary
Now you can press "ready to upload binary" whenever you would like to update a correct version.
If you haven;t uploaded the next version build then surely you will have the availability of old version.Once apple approves the new version then & then only new version will be available, then it one can download the old version of apps.
For more details, I suggest is through apple guideline.
Related
I have client with an app in the app store that was at version 4.05 and they accidentally submitted a new build as version 5.06 when they meant to submit it as 4.06. They aren't ready yet for a full version number increase. Long story.
Is it possible to submit the next version as 4.06 to get it back on track? Or is not allowed to upload a lower version to iTunes Connect?
Yes. The version numbers only need be distinct.
From the Developer Guide:
A Version Number The unique version
number of the app. Keep the following
in mind:
Use typical software versioning conventions (for example, “1.0 or
1.0.1 or
1.1”).
Do not include words such as “build” , “version” or “beta” in your version
number. This will appear next to your
application icon on the app product
page.
Perviously the client uploaded same app on iTunes connect and rejected for some reason.
After some modifications I need to upload the binary again.
The previous binary details are,
Now, here are the current info.plist details,
I am using Xcode 4.0
When I tried to validate product from Xcode I got this error,
I tried different different CFBundleVersion in the Info.plist. but still error occurs.
I cleaned project, deleted build, also re-installed Xcode and retried but no use.
Please help me.
So it looks like this needs to be an ever-increasing version number and can't reset when the marketing version number changes. It seems like you could use your VCS revision number here; in my app I display the marketing version number and if the user "clicks" on it it adds the build number (CFBundleVersion) on the end. The primary purpose of this is to keep the version number clean and simple, but also allow QA and beta testers to determine the exact version of the product they're testing. The Subversion revision number would certainly help us track down the build being used, but in this case that'll be a strange version number jump for me (6 -> ~74000).
basically i had to change 1.1f to 1.11 in both itunes connect and in xcode. the f had to be removed from the version number. no alphas allowed !
Reference: Can't Update App with New Version Number
I have an app on appstore.
I uploaded a new version and it was published. But, just after that I realized an important bug in my app. Since the approvement process takes a long time, I want to downgrade to the previous version until the fixed version is approved by Apple.
Are there any way for that?
Thanks
The only way to downgrade is to resubmit the previous version with a new version number, or a new fixed version, and wait until it is approved. If you put a note in the Demo Account section saying this is a rollback or a critical bug fix, there are reports that Apple may perhaps expedite the review. If the bug is bad enough to create very unhappy customers, you can warn customers not to download it in your update notes, and/or you can set the availability date of the current broken version into the future, until your fix is accepted.
Unfortunately not, Apple doesn't provide a means of rolling back to previous versions. If you have the source code, you could always just increment the version number and upload the old version again.
like the other answers have said - unfortunately, Apple does not provide a way to rollback once you've released the app.
The way many major apps deal with this is by instrumenting their app ahead of time with feature flags (https://martinfowler.com/articles/feature-toggles.html): ways to enable/disable features and codepaths from the server.
Granted that implementing feature flags requires foresight and planning (it's unlikely you'll capture every codepath). Fwiw, I started my current company (https://screenplay.dev) out of this frustration; you can read much more on this approach here: itunesconnect App - Revert to previous version :)
i have been trying to uplaod an application to apple store for 2 days now..first they said the provisioning profile was not right due to which i had to make a new one and upload it again now after that problem was solved while uploading the new binary it said the version was same with the previous minor version(1.0 - which someone else uploaded in my company)..then i changed the version to 1.1 by changing it in target > info > properties..then i cleaned all targets quite the xcode,restarted the xcode and build the project again..it succeeded and now wen i uploaded it it still says the same error
version same with the previous minor version
is there any other way of changing the version number though in my info.plist file it is showing version:1.1??
i am all new to iphone and the person who created the application is not here and i dont have any CFbundleversion in my info.plist which some people suggested me to update??
Alternately you can change CFBundleShortVersion string in app-info.plist file and increment it. I have faced the same problem earlier. This property is not present by default and needs to be added.
Bundle versions string, short is the parameter name
Change your version from 1.1 to 1.1.1 or 1.2 For each new binary, your version number should increase. How to increase version numbers will depends on your versioning system.
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.