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..
Related
We have not been able to publish our first update to our iPhone app on the app store.
The validate step after build always fails with:
"This bundle is invalid. The bundle identifier cannot be changed from the previous version. If you want to change your bundle identifier you will need to create a new application in itunes connect."
We have only one Apple account with only one app. We have not changed the bundle id in the plist file ever since we released earlier in the summer (it was different before we released though). it is "com.company.product" (with our real company name and real product name all in lowercase). We only increased the version number from 1.0 to 1.10 (after seeing articles here with problems going to 1.1)
The iTunes connect is expecting 1.10 and the same bundle id. Spent 2 days Googling but can't find anything useful and tried different versions and bundle ids etc but nothing was good.
Please help!
(I have also sent an itunes connect question on this to Apple but no response so far)
I got this error before, I'm not sure however if you have done the same thing I did:
In versions 1.0, 1.1 and 1.2 of my app, it only supported iPhone. I then got an iPad of my own for testing. In version 1.3 of my app, I updated it to support iPhone and iPad. It wouldn't upload, giving me this error. Turns out if you want a universal app, it has to be universal from the start, you cant decide in version 1.4 or whatever that you want to add iPad compatibility.
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 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.