Good afternoon. There is a project, it is published in appstore. A major update is planned - the project will be fully rewritten. Can I replace an existing application in the App Store with a new one to make it look like a normal update for the user? Can I release an update to a new application in the itunes connect replacing only Bundle Id? Thank you
This is the standard procedure of updating an existing app. You might want check Apple's docs: https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ReplacingYourAppWithANewVersion.html
There are only 3 important things:
Bundle ID: Needs to be exactly the same as you can see in iTunes Connect
Version Number: Need to be higher than last in iTunes Connect. Not talking about the "customer-facing" version number but the actual one you can see in the list of builds
Build Number: Counter begins with every version.
Related
I've just published an app on Apple's store and I'm wondering about having multiple versions of the same app for testing on TestFlight. Of course dev doesn't stop when publishing... from now on I'll have to update the app store version (v1.0.0) with bug fixes (v1.0.1, v1.0.2, ...) and before doing so I'd like to check them in test flight to ensure the fix was appropriate.
My problem is that I'm already starting to develop the next version with further functionalities of the app which will become v1.1
So ideally I'd like to have my app available both for my bug fixes, for instance v1.0.2 and also my next version v1.1.0 (this will include all bug fixes made to the store version and also many new features, refactors, redesign, etc)
I know that if I build and upload to the apple store connect a build with v1.1.0 (next version) I won't be able to upload one for a built with a bug fix on the current app store version (v1.0.2) since this version would be lower than the one I uploaded (next version)
Is there a way to accomplish this? I've read this article https://savvyapps.com/blog/using-testflight-to-distribute-multiple-versions-ios-app which solution is to create extra applications in iTunes with different app ids and bind them to different certificates. But what will happen when the next release is ready to be in the store? I would have to release it and then disable the previous one? How may this affect my users? Will they have to re-install a new app rather than updating it?
I really need to start testing and checking the next release of my app in TestFlight and also support the current one with updates if something pops up. Thanks in advance!
I am able to upload multiple versions of the app to TestFlight. Each upload requires a higher version/build number, but you can switch the TestFlight test version between them as need be for testing.
Once I submit a particular build for release, however, I seem to lose the TestFlight access to the old builds.
In short, you can have many builds available in TestFlight, but once you submit the app for release, you have to start over making builds for TestFlight.
You keep talking about numbers like v1.0.1. That looks like a public-facing version string, with a major, minor, and patch number.
But that is not what TestFlight cares about. Well, it cares to some extent. But all TestFlight really cares about is that every new build you upload has a new build number. This is just an integer which you simply increment every time you submit a new build.
So you could have v1.0.1(23) on the App Store, and then on TestFlight you could upload v1.0.2(24) which starts moving forward toward version 1.0.2, but also upload v1.0.2(25) which is actually an attempt at a prospective version 1.1. TestFlight doesn't know or care what these different builds signify. They can all exist simultaneously on TestFlight. Keeping them all straight and on their individual trajectories is up to you.
Good afternoon. There is a project, it is published in appstore. A major update is planned - the project will be fully rewritten. Can I replace an existing application in the App Store with a new one to make it look like a normal update for the user? Can I release an update to a new application in the itunes connect replacing only Bundle Id? Thank you
This is the standard procedure of updating an existing app. You might want check Apple's docs: https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ReplacingYourAppWithANewVersion.html
There are only 3 important things:
Bundle ID: Needs to be exactly the same as you can see in iTunes Connect
Version Number: Need to be higher than last in iTunes Connect. Not talking about the "customer-facing" version number but the actual one you can see in the list of builds
Build Number: Counter begins with every version.
I had an App in Appstore, i need to remove the app from sale and upload that as new app or record with same name. But i am unable to give the same name, it's showing an alert like this,
The app name you entered is already being used. If you have trademark
rights to this name and would like it released for your use, submit a
claim.
Is there any quick process to solve this? Please advise.
Thanks in advance
Let's say your app is called Awesome with current version v1.0.0, I think you might try to follow these steps:
1) Rename your current live app in something like: Awesome App
2) as explained in the image, to be able to see the changes you have to release a new app version, let's do it with v1.0.1
3) wait for approval, then as soon as it's on the store, submit for the first time the new app (with a new bundle identifier and so on) called Awesome.
4) finally you should remove from the store Awesome App.
Unfortunately that name is locked permanently and you have to choose another name. According to App Store Review Guidelines:
2.3.7 Choose a unique app name...
More info here.
I wonder if there is any way to distribute different versions of same app (same means same bundle id, same account) in Apple Appstore.
Lets say, I want to distribute, MyApp (com.stackoverflow.myapp) version v1.2 but there is already a version v1.1 open to public. Is it possible to keep both version open for public. And fixing issues and release different sub version like, v1.1.2 and v1.2.2.
As far as I know with single bundle its not possible. But still I am curious if there is any workaround.
When you release a new version on to the app store, you can now select an option for a "phased release", where the update is shown to current users incrementally over a 7 day period, but at the end of that seven day period the updated version is available to everyone. Also, new users will get the latest release when they install from the App Store.
You cannot maintain two "active" releases on the store.
If you want to test a new version or new features with a limited set of users then TestFlight may be an appropriate tool.
You can use whatever versioning system you want (such as semantic versioning), but you can't distribute multiple versions of an app at a time without uploading them to the App Store as 2 entirely different apps
I have an app on AppStore that I would like to improve with StoryBoard. I was recomended to build a new app from scratch instead of trying to add storyboard to an old app. So I have done that and now I would like to upload it to the AppStore and replace the old one.
I understand that the bundle identifier and app name must be the same. Do I have to make sure any other stuff is the same?
Yes, you can do this no problem.
Just make sure to use the same App bundle identifier i.e. com.companyname.appname as in your original app.
Then use the same distribution license that you would normally use.
You have to release the new app as an update to the old app but apart from that you can change anything else.
You also have to make the new version number greater than the current apps version number.
To the users it will look like a normal update but in the background you will have essentially replaced the entire app.
You could consider this as an update of you app.
Bundle version should be higher then before (for example 1.1 or 2.0 if the previous one is 1.0) - this usually depends on how big the difference will seem to the users.
And also: if you are saving anything to documents folder make sure that the new version is compatible with the old data.
New version should be able to run on device:
if there was (any) previous version installed
if there was no previous installation of your app