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 have searched over google for the specific rules for creating new version of an existing application but don't able to get proper rules.
I would specifically like to know that only icon and the title change of the application is enough for placing new version of the application on app store?
& if yes then. What precautions I must have take?
UPDATE 1
Thanks for your quick reply, Currently I'm doing the same process :) actually I know the process of creating new version but my specific concern is only icon & title change is sufficient for putting new version of the app on app store ?
Update 2
I have done all the changes and uploaded the binary but after uploading the status is "Invalid Binary".
Now what to do??
You can add a new version of an app when the current version’s status is “Ready for Sale” or Developer Removed From Sale. The new app version goes through the same review process as the first version. You have to increment your version from previous (for this could be depend on major or miner update 1.0.1) into info list
You only need to change the version number.
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
I haven't been able to find relevant answer to this problem. Please redirect if you know it's a duplicate question.
Background:
I have this version 1.0 of an app on the App Store. It's basically a wrapper around a WebApp and the updated 2.0 version I am working on is a native implementation for iPhone.
Now the current version 1.0 of the app is Universal. So trying to submit our finished 2.0-native iPhone only app is refused by AppStore since it's considered a downgrade to no longer support iPad.
The roadmap ahead includes a future release of an iPad-version as well, and this needs to be taken into account. I believe there are good reasons for this iPad-app to be Universal. We need to keep the current AppName in some way.
Now I need advice on how to best handle the situation. These are the steps I consider:
Release v2.0 under new appName i.e. "MyApp 2"
Remove v1.0 app from sales, but keep it in iTunesConnect to save the name
Change WebAppContent of v1.0 to notify the current userbase of the native app (2.0)
When we are ready to release a Universal App we update the current 1.0 instead of 2.0 to reclaim the original name
Questions:
Is there a better way?
If we remove v1.0 from sales and release v2.0 under the name "MyApp 2", is there a way to change the later name back to "MyApp" when v1.0 is of the stores?
If we consider deleting v1.0 completely from iTunesConnect, can we, as the same company, then reclaim the name when it becomes publicly available again (or are we blacklisted for that name)?
Can you have different display names for an App on AppStore and on the devices home screen (how is this done)?
Warning: If you delete an app in iTunes Connect, that app's name is no longer available for use by that same Developer account ever again.
Bundle display names are independent of App store names. Many apps have shortened or abbreviated Bundle display names to fit under the icon, and a much longer app store name.