Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I just submitted a new version of my application (version 2.0) to Apple and it is Waiting For Review in the App Store. I set it to release manually as we are strategically planning a release.
We have a more feature filled version of the app (2.1) ready but we want to make sure the first version passes Apple review first.
My question is, once Apple accepts 2.0 are we going to be able to upload 2.1 without releasing 2.0 live into the app store?
You cannot have two unreleased versions at the same time.
When you have only a version that's live on the app store, the iTunes Connect UI shows these buttons:
When you have a version pending developer release (or waiting for review, or otherwise not on the store), the iTunes Connect UI shows these buttons:
As a result, you do not have the option to create a new 2.1 version without pushing 2.0 live on the store.
You will see two statuses - one for 2.0 that will be green once it is approved and on the store, and one for 2.1 that will be yellow - waiting for review. You can always have a live binary and one waiting for review :)
Yup, you will be fine. No need to release 2.0 :)
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I am new in ios development. I have created one app, in this app some features are not available right now. So my question is can i submit my app to app store with same design by giving coming soon alert for those features. Thanks in advance.
It is likely that your app will be rejected if you include such an alert. Refer to section 2.1 of the App Review Guidelines:
2.1 App Completeness
Submissions to App Review should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you offer in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you explain why not in your review notes. Please don’t treat App Review as a software testing service. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.
And
2.2 Beta Testing
Demos, betas, and trial versions of your app don’t belong on the App Store...
You should remove all reference to "future functions" and put it back in when the function is available.
Yeah, as per my knowledge you can submit but it must not crash on iphone or ipad and must follow all the guidelines of apple. Because coming soon is on kind of UI of your app so i don't think that it will be rejected due to this kind of stuff.
You should refer App Store Review Guidelines for more details.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Apple just approved my update for my app but it doesn't show under the updates page of the app store. You have to manually go to the app page on the store and there is a cloud icon that appears that will download the update.
I named the first version of my app 6.1 for some reason, don't know why. And my update is version 2.0. Is this the reason? And if so, can i change the version number of the first to 1.0.
Apple never publishes the updates / new apps right after ready for sale. You have to be a bit patient and wait for about a day or something.
Also, it does not matter how you name your app versions. It can be whatever number you want it to be. Apple just recommends using numbers that make sense but they won't do anything about it.
Hope that helps :)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I've been using TestFlight for my internal beta testings, everything was set and it was working for a while. after one of the submitted binaries got rejected from AppStore review, there seems to be a problem.
On any new uploaded binaries and turning on the Beta testing switch in iTunes Connect, I get the notification from testflight app that the new version is ready to be downloaded but on the app it says "UNAVAILABLE Expires in 30 days" and when I click on the beta app in TestFlight, on top it says "This version is no longer available for testing" even though the expire date is in a month from now.
Any workarounds for this?
So I solved this issue, not once but twice, apparently it's a bug.
what you have to do is turn off all the beta testings and then turn on the one you want to test, and then it works :)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
When releasing to the App Store after using iTunes Connect Testflight beta testing, what's a good way to ensure that external testers get cleanly upgraded to the official App Store version? Specifically:
Will external testers get a notification on the device that a new app version is
available? Will this be a regular iOS notification, a notification
from the Testflight app, or both?
On the home screen, will the beta app's icon show any indication that
it's been superseded by a non-beta app?
If the user has automatic app updates enabled, will the app store app
download and install automatically, replacing the beta app? Or will
the user have to upgrade manually even if auto-upgrades are enabled?
If the user opens the Apple Testflight app, will they see any
indication that the build they were testing has been superseded by a
released build?
If the answers to some of the above questions are "maybe" then what configuration or settings should we use to ensure that app updates work as expected? (where "expected" means that when we release the app to the app store, then all testers should be updated with that new version of the app).
Googling on this topic hasn't been very helpful, perhaps because Apple's TestFlight support is only a few months old so Google is dominated by non-technical news links instead of technical blogs and other places that may offer more details. I've been unable to find any programmer blogs which talk about the "upgrade from external tester to app store version" workflow.
Apple's documentation is clear about what happens from the perspective of the iTunes Connect web application (see excerpts below, coalesced for clarity) but not very clear about the external testers' user experience, which is what I'm trying to figure out. Here's excerpts from Apple's Docs illustrating this:
Finish Testing an App. To stop testing a prerelease version of an app that is actively being
tested in TestFlight beta testing, set the Testing switch into the Off
(white) position.
Submit to the App Store When you are done using TestFlight beta testing, you can submit the
app for final review. Before you submit it, make sure you no longer
want to test it or any builds you uploaded earlier than it. When the
app becomes Ready for Sale in the App Store, testing automatically
stops on earlier builds, and you will be unable to view or test them.
See When builds become unavailable for more details. If you want to
resume testing of an earlier build, you can upload it as a new build
associated with a new prerelease version.
When builds become unavailable
Before your app becomes Ready for Sale, the Prerelease pane lists all builds for all prerelease versions
you have uploaded. After the app becomes Ready for Sale, some of the
builds will be removed from the pane:
The build used in the app is removed from Prerelease, as are all other
builds in the same prerelease version. All builds in earlier
prerelease versions are also removed from Prerelease. On the
Prerelease page, the sections for those prerelease versions will be
removed.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
My app has gone from In Review (Yellow) to Pending An Apple Release (red). I couldn't find anything on this combo in the docs. I set my app release date for immediately and its price tier is free.
Thoughts?
EDIT: Since others brought this up, my app is also targeting 7.0
EDIT: App has been approved without me doing anything. Side note it's not appearing in search but the direct link works.
Per https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ChangingAppStatus.html#//apple_ref/doc/uid/TP40011225-CH30-SW1
The "pending an Apple Release" means:
Apple is holding your app version until the corresponding Apple iOS or OS version is released to the public.
If you think an app should be released on existing iOS or OS versions, review the deployment target set in your app binary. If you rebuild your app binary with a different deployment target, reject the binary for this version and submit the new version.
Sounds like you need to review the deployment target and if you change it, reject the binary and re-submit. If you need help with rejecting the binary, please let me know.
Hope this helps!