I have 1.1 version of my application already in review process now I also want to upload 1.1 version of the application for review process.
So that if anything bad happens to version 1.1, I could directly release 1.2 without going through review process (as it would have been done already). So, I want to send two version of my same application to appstore review process.
Is it possible. If yes then how?
No, you can only upload one version of the application for the App Store review process. But You can have multiple versions in your application in TestFlight. We can even have greater version of the application available on TestFlight from the current version which is under review.
You can refer here if you want to know more.
No. You cannot submit multiple versions of the same app when it is already in review. If you're unsure of the current version, you can anytime remove the binary and upload new version. Also to avoid app rejection, you can go through the App Review Guidelines for once.
https://developer.apple.com/app-store/review/
Also in the below link you can find new rules and changes in existing ones :
http://www.appstorereviewguidelineshistory.com/articles/2017-06-08-new-rules-following-wwdc-2017/
You need to cancel the current version in review to put another 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.
i have uploaded my app on iTunes but it have some errors now i need to upload newer version of the app and force user to update to that version. How can i do this .. I need help on this..Thanks in advance
If you already uploaded you app, this is not possible. You need to implement this yourself. Basically check against some server where you get the current version from. If the app version doesn't match this one, just show an error message.
In iTunesConnect you can specify that the old version will appear in iCloud, see this doc: https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ReplacingYourAppWithANewVersion.html#//apple_ref/doc/uid/TP40011225-CH14-SW3
But note that this doesn't affect people who have already downloaded your app.
My current application in apple store is with 3.0.1, now to have sync with other platform versions I just wanted to release new version of application with 14.0.1.4. Will it be problem from apple?
Yeah surely you can do this,Apple has no problem at all with this,They just check whether current version is above to the previous one or not.
More information on updating your app(s) can be found on this Apple Developer page.
I submitted my Full and Lite version of my iOS App to the Apple App Store for an incremental release (1.2) - both Apps are already For Sale. I added In-App purchases to my Lite version.
My Full version was approved, but my Lite version was not. In discussing with Apple, they have provided a screen shot showing that they can't access the In-App functionality in the Lite version, but the screenshot is from my Full version, which doesn't have that functionality.
I'm appealing, and am hopeful that they will address.
This is the first time any App I've had was rejected, and I have several questions that I would appreciate any suggestions from developers who have gone through this.
Is there a way for me to run the exact code that I submitted from the Organizer/Archive so that I can verify that my Lite version is indeed the Lite version and not the Full version? I can see them in on the local file system, and there are 2 different, distinct files that have different sizes.
If I have to rebuild my App and resubmit can I do that from the same archive that is in Organizer?
If I have to rebuild, I think I'm in a bit of trouble, because I've been heads down on the next release for the past week and a half. Is there a way to access the version that was used to build the archive?
thanks.
You can resign the released version to be an adhoc version and run it on your device.
If it requires a new build it won't let you submit with the same version number which will probably stop you from using the same archive unfortunately.
It has been my practice to make a snapshot for every release for this case. If you don't have a saved snapshot or if you aren't using source control then you may be out of luck on that one.
I have an app that has been submitted to the app store in iTunes connect and approved but not yet released. (The release date is set in the future). The version number is 1.0.0.
Before the app was to be released my client decided he wanted some changes made. So I added a version 1.0.1 and submitted it to the app store. It has also been approved and not released.
My client has yet again decided he wanted some changes made. I have now made version 1.0.2. I can now no longer add a version in iTunes connect, because 1.0.1 has not been released yet.
My client wants to release the app next week to coincide with a marketing campaign. I want plan to release 1.0.1 in iTunes connect and submit 1.0.2.
My questions are:
When I release 1.0.1 will it go into the app store? I think (and want) not, because the release date of the app is still set for the future, but I want to be sure.
An alternative would be to remove 1.0.1 altogether, but I see no way to do this. Is the way that I originally described the appropriate way to accomplish what I want?
Yes, as soon as you release, either automatically or manually, it will push out live to the App Store.
I'm not sure if you can remove an update that already been accepted and approved. My suggestion would be to release it quietly and submit your update for 1.0.2 right away. With the wait time around 5-6 business days, you don't have a large window if you want to meet your clients deadline for the marketing campaign.