Some time ago we released an app to the AppStore on a client's account. The client preferred a simple version number scheme, so the apps first version number was 1.0. Since it's release, however, there seems to be an unexpected need for minor changes to the content of the app on a regular basis, so a more precise versioning scheme, reflecting content revisions, would be more feasible now.
Is it possible to "refine" the numbering scheme in the course of an update to the app? Instead of upgrading from 1.0 to 1.1, I'd like to go to 1.0.1 now.
Would it be sufficient to just change the version number according to the new needs or will the AppStore accept only new releases if they follow the original scheme?
Thanks!!
You definitely can, especially if you haven't submitted the 1.1 version yet. 1.0.1 > 1.0 so it's ok.
Taken from "Developer Guide" (https://itunesconnect.apple.com/docs/iTunesConnect_DeveloperGuide.pdf)
Version Number:
The version number of the app you are adding. Numbering
should follow typical software versioning conventions (for
example, 1.0 or 1.0.1 or 1.1).
Related
I uploaded the app in App Store, and now it in "Pending Developer Release" status. But I want give it to testers before release. I have no troubles with internal testers, I gave them access to application without problems. But I have trouble with external testers with the same binary. There is an error:
CFBundleShortVersionString in info.plist must be higher than 1.0
What should I do, if I don't want to reload binary, because I can lose the "Pending Developer Release" status?
When you release a new version using Apple's distribution system (i.e. App Store or TestFlight) the version number needs to be higher than the previous release.
If the app is still in testing, it shouldn't have even reached 1.0 yet. Start with 0.1 and increment up to 0.999 as development milestones are reached. Once it's tested and ready for release, make it 1.0. This is my thinking on the issue anyway; the actual value is not important, however some users may query why a newly-released app has a version number of 1.452, for example.
Note that the number is not a floating point; instead it's major.minor and major does not increment when minor goes above 9; instead the version becomes 1.10 until you rework it sufficiently that the major becomes 2 and the minor resets to 0, and so on.
So to answer your question, change CFBundleShortVersionString to 1.1.
As for CFBundleVersion, that should be an integer that increments from 1 whenever a build is performed and source files have changed (again, in my opinion), which can be managed with a script as posted in this answer.
Is there a chance of app getting rejected if the iPhone app update is submitted with wrong version number? For instance i had given the version number 1.6 instead of 1.5. The app which exists in app store is of version 1.4. Will my app update get rejected?
The version number just has to agree with the version number you specify in your Info.plist. Apple does not care about he numeric value, so nothing to worry about.
It doesn't matter. Apple doesn't have a version number naming scheme. As long as your app-version matches the version given in your itunes its not an issue. Also any error related to incorrect versions are reported during submission itself.
So naming scheme is totally dependent on the developer.
No it doesn`t matter.
i have submitted an app with version number 1.3 instead of 1.2 and it was approved.
so don`t worry..
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.
I don't understand, why i need versioning in my IPhone apps.Could anyone explain.
Apple uses the version number when you submit an update to your app. If the update you submit does not have a version number greater than the currently shipping app, then Apple will not accept the update.
That is the only technical reason.
There are other reasons:
it gives you a way to track issues against different releases
it allows users to know whether they are up to date
Etc
If course if you are never going to update your app then you can just set the version to 1.0 and forget about it...
You don't have to support different versions - you can just choose one (probably the latest) and just develop for that. However, it will limit the number of devices that can run your application.
Read the accepted answer to this question (the one with the green tick next to it) for information about supporting different versions of iOS :
How To Make iPhone App compatible with multiple SDK (firmware) versions
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 :)