My iOS app is currently "Pending Developer Release". I did this to get promo codes. With promo codes, I got some awesome feedback from users. I want to implement those changes and add it to app. So how do I remove my app from "pending developer release" since anyways it's not in app store now. Also, if next week I add the changes and upload this new app build, would App store have a problem with it and think it's a duplicate so they wouldn't allow it to be uploaded to App store?
Also, if next week I add the changes and upload this new app build, would App store have a problem with it and think it's a duplicate so they wouldn't allow it to be uploaded to App store?
There are two build numbers:
Increase the second build number but leave the first build number the same. That way, the App Store knows that this is an update to the same build. And when it has processed, you can then release the later build.
Related
I'm not very familiar with TestFlight. I would like to add a build with a new version for my app. Do I need to add the new version to the App Store settings first?
For every build you upload to iTunes Connect you can decide whether you want to share it with testers on TestFlight and/or submit it for app store review.
When you share builds with TestFlight Apple will review these builds too and you can receive warnings to them too. The initial TestFlight build will be tested more extensively.
Do I need to add the new version to the App Store settings first?
I don't know about which app store settings you are talking about, but all you have to do before uploading to iTunes connect is set the code signing and provisioning profiles first in XCode and Apple's development portal and make sure you increment the build number on every new upload because the upload will fail if you try to upload a build with a build number already present on iTunes Connect.
Once uploaded iTunes Connect will start processing it and then you can share it for testing with TestFlight or submit for app store release review.
You can read more info about TestFlight in Apple's dev site
1 - Test Flight have nothing to do with Live apps
2 - Versions can contain unlimited number of builds before submitting one to the Live app store
3 - Every time you upload new build it goes under the version number in test flight.
So lets say I am on version 1.0, everyday I'am uploading new build under the same version number
day one : 1.0 (1)
day two: 1.0 (2)
And so on, after i upload the final build i can submit that to the live app store, next i will start working on version 1.1 I add that and submit builds to test flight as before, then i submit my 1.1 to the store, and so on .
On app store users will not see anything but the version submitted and current version live is not affected by any test flight version, i can be on version 9 on test flight but 3 on app store, and even schedule an update every month till i reach 9.
My app has been approved but is awaiting developer release as I want to release it manually. Before releasing, it however, I want to test using test flight
When I try to send the approved build to my testers, Apple asks for a login id and then gives me a dialog to Submit For Review. Is this just Apple being clumsy with their language or do they actually want to review it again before testing even though it's been approved?
Anyone have any experience with this?
Here is pic of dialog box
My experience is that the Store and TestFlight are two different worlds with two different approval processes — but that the former affects the latter in a peculiar way.
The way the issue you raise has arisen in particular for me is that you release, say, version 1.1 build 26 on the Store, it is ready for sale, and then you proceed with development and upload version 1.1 build 27 to TestFlight. Even though 1.1(26) is being sold already, and even if 1.1(26) was already released on TestFlight, 1.1(27) requires a new approval! In other words, it appears that an App Store release resets the approval clock, as it were, on TestFlight.
That is almost exactly your situation. The approval on the App Store apparently means that your next TestFlight upload needs a new approval. So yes, you will have to wait while it is approved. This usually takes just a couple of days.
Instead of using TestFlight, there is even more simpler method to test the Apple approved build (Pending Developer Release state) before releasing to Store. It is Promo code testing.
You can generate nearly 100 promo codes, if i am not wrong. These promo codes can be shared to the developers so that they can actually test the store build without releasing it to app store.
You can find many articles about Promo codes. I have shared one here.
I had uploaded my App successfully to TestFlight, 5 days ago(with new version and new build number). Which is already uploaded on App Store (But with its Older version).
Now i have added external user to test it and select the build to test and then click on save button, then it is showing "Waiting for beta App Review".
I don't know why user is not added directly rather app goes into "Waiting for beta App Review", and how much time it will take to approve?
Please help me if anyone has faces such issue.
Once you add another user (ie not your apple id), then it must be reviewed by Apple first to ensure the app is safe (contains no malicious intent) for the users testing it.
Normally takes a couple of days for apple to turn around and approve.
There is a distinction between iTunes Connect users and people in TestFlight.
When you upload build, and it shows up, then it becomes visible to your users. But there is an approval process (presumably automated) before TestFlight users see the announcement (assuming it is approved).
Can anyone tell me how to set a specific release date in new iTunesConnect interface, after approval with pending developer release state?
Our release should for some reason at a weekend now, so changing from manually release to a date would be nice. But now where the app is in pending developer release state, I can not find the option for a specific release date anymore.
According to Apple App distribution guide:
Use iTunes Connect to set a date when the app is available on the store. For example, you can choose a date that immediately releases the app to the store after it’s approved, or you can set a later date. Using a later availability date allows you to arrange other marketing activities around the launch of your app.
The screenshot in documentation is outdated though. See the image below.
Steps:
Login to iTunes connect
Select Apps
Select your application
Click Prepare for Submission
Scroll down the detail page to bottom to see option to manually
release the app.
Note that if you set a date too early, it is entirely possible that your app will not be released until and unless the review is complete.
Also, if you decide to update your app during review time, you will have to restart entire process and lose progress on current app review.
I've uploaded binary to Appstore for review and approval. How to change following settin now:
When they approve it, I don't want to be automaticaly be visible on AppStore. I want to change the setting so i can put it on Appstore when I decide.
It asked me for this setting before binary is uploiaded, but can i change it now?
You can't. iTunesConnect will only ask you this once. Your update will released once approved.
Just reject the binary and upload again, you will be asked the question again.
You Can Not do this.
Check the list here in detail :-
Editing and Updating App Information
Goto rights and pricing info screen (where you can select pricing tiers for your app), and then either choose your app's availability date or deselect all countries from appstores.
The following text was from Apple' doc.
If you choose to automatically release your app update, it will go live as soon as it is approved by Apple (pending the availability date you have set).
If you choose to control the version’s release, your app status will change to Pending Developer Release after it has been approved by App Review, indicating that you can release it to the App Store whenever you are ready.
When you're ready for your app update to go live on the App Store, you are responsible for releasing your app version to the App Store.