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.
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.
Let's say I have an existing IOS app live on Appstore which is version 1.0
Now I make some changes to the app and want to submit back.
Are there 2 separate ways to submit ?
Like can I still keep the version as 1.0 and just submit the app OR
I need to create a new version 1.1 and then submit it ?
What are the differences in the process?
Also from the customer end, how does this work for new/existing users ?
I have just discovered something about version upgrades and the App Store. Just now, I'm suffering issues and users crashes because of a behavior of iOS system that I can't figure before. And, very important, iTunes, AppStore and iOS have modified some upgrading and installing rules in last versions. Now, it works this way:
- When user install a new version, all the files in the bundle are downloaded and copied in the previous existing bundle, but OLD FILES OR COMPONENTS ARE NOT DELETED (or not all are deleted). So, the final bundle IS NOT equal to the bundle of a fresh installation of the new version.
- For example, if a xib/nib file is localized to different languages for the new version, the updated bundle will include both versions: the one in the root folder and the other one in each localized folder. The system, obviously, will use the first one and only a fresh installation will show localizations for that file.
One of my apps shows that issue with MainWindow.xib and as there are some modifications in references and classes, the updated apps crash each time you try to run as it is using a obsolet object. I have built a new version changing the name of the xib/nib files that have been localized. As MainWindow is one of them, I have to modify the reference in info.plist of course.
OK, knowing that, you can build a new version with complete different components in the bundle that, if files of previous version does exist, the app then offers the user the option of using them. That is, two versions of the app in a single icon and bundle. Not very difficult to do.
BUT, the very weird thing is that I think that new iOS version and iTunes don't allow downgrades. I have tried to do it but didn't get it done. That is, if you install a version, for example 1.2, it is impossible AFAIK to install latter v1.1 on the device nor in iTunes->"Applications". So, the double version bundle will live until a reinstallation of the app.
You need to create a new version number, which makes sense since this is a new version of your app. This will then appear as an update for your customers. I don't think you can upload a new binary with the same version without removing the old one from the store.
You add a new version in iTunes connect, then update the version number in Xcode to match and create a new archive. It's pretty straightforward.
You must always increase the version number of any update to your app.
Users will see a badge on the App Store icon on the device, and in iTunes on their PC. Going into the updates section, it will list your app along with the list of changes you've provided, and a button to install the update. They can also update all apps at once.
NSString *version = [[[NSBundle mainBundle] infoDictionary] objectForKey:#"CFBundleVersion"];
NSLog(#"version is%#",version);
You do not have to open version numbers to submit any longer. Open up Xcode, go to Window - Organizer - Archives and Distribute an app you have created successfully.
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.
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
When I am installing new application on iphone, this current application get override on the last application,so we can not maintain the previous application.
Please help to solve this installation problem.
If you change the app identifier in info.plist you can have a different version on the phone at the same time...
However, do you really want to do that? Most apps migrate by loading a new version, but then updating the old database or preferences to work with the new version of the application. Just because your application is replaced does not mean the data the user created is replaced.
If you change the Product Name in the build settings, that directly affects the name of the .app bundle. You can have two copies of the same app, as long as theyhave different names - this can be helpful for testing a new version while preserving the old, stable version.
As Kendall says, you probably want to use the same name for newer released versions of the same application.