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).
Related
I have an IOS app in the app store. My plan is to make it free, and create an in-app purchase of a non-consumable product within it.
I have included some, but not all, of the in-app code needed to do this. I have uploaded the resulting builds to iTunes Connect without a problem.
To test the code I have created a test user in the 'sandbox'. I have logged out of my 'real' Apple ID (iCloud etc) in my iPhone and logged into the sandbox account...
and this is the point where I am confused...
When I click on the icon for my app, am I seeing its latest build, or the 'ready for sale' version. Do I have to anything? Is the Sandbox looking at my latest build or at the 'ready for sale' version?
BTW, I'm using Phobegap Build.
Do I have to submit the app for review to Apple before I'm able to see the app in the Sandbox?
If it passes the review, does that then mean it becomes the 'ready for sale' version? If so, how do I develop the code efficiently if I have to resubmit each time? My first submit is going to contain errors... do I have to submit a 'perfect' working version before I continue development (which clearly doesn't make sense!).
As you can see I'm confused. The online help that I've found online is really helpful (especially Stack Overflow... thank you everyone), but 'big-picture' advice is elusive.
I'm an iOS developer working for a company and in the next days we'll be publishing our customer .ipa compilation onto the app store.
The thing is we're perfectly aware of the 1st of April restrictions about "how to publish new apps", that is, we already know we need to use XCode 9 to add proper iPhone X screen layout support.
Anyway, our intention is releasing our app AS OF TODAY (20-Mar-2018), before the 1st of April deadline, with not perfect iPhoneX support yet. In fact, the .ipa file has been already uploaded weeks ago, and considered ready to be published by Apple. So far so good.
Now here comes our doubt: What would it happen if we keep the "approved status and ready to be published" of the .ipa file we sent some days ago, and perform the actual publish action under iTunes connect after the 1st of April? Would Apple refuse our (otherwise) already accepted .ipa file, which is now "in the oven" ready to be published?
After reading the new conditions about uploading .ipa files after 1st of April (with Xcode 9), we have no idea if the already uploaded .ipa file would make its way to the app store, or would be banned.
We sent our query to Apple.
Apple told us this: once the app reaches the "the only thing needed to publish your app is just pressing the 'publish' button inside your itunes connect", the app will get published, no matter what.
In case legal/technical conditions are known to change, if they apply after the app has been approved by Apple review team (as it will happen on 1st April 2018), the "invalid app" publishing action will be valid anyway.
In case other developing teams have this doubt, here you have Apple's answer to our query.
We are in a hurry to publish an app for a customer, so yesterday we published an app to App Store and now is "Waiting for review".
Meanwhile, the customer aked if he could have a preview. My idea was to send him a TestFlight beta testing. I'm thinking in several options:
Start an internal testflight for the build that is in review for team customer users
Start an external testflight with the build is in review for other customer users not in the team
Send a new build and start internal testflight for team customer users
Send a new build and start external testflight for other customer users not in the team
What I'm not sure is on each case (internal/external testflight):
Can I start a testflight testing for a build that is "in review"? And if I can, will it cancel the "in review" process for this build?
Can I send another build while there is already one "in review"? And if I can, will it cancel the "in review" process for the previous build? If it will not, can I start a testflight for a new build while previous one is in review?
As said, the priority here is not to stop the "in review" process.
EDIT
I've been reading docs at https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html and what makes me be scared is:
When you are done using TestFlight beta testing, you can submit the app for final review
So it seems that testflight is more like an step in the process than a parallel option in the process...
Would be nice to have had a reply after your "will give a try..."
So I had the same issues a few minutes ago:
App is "waiting for review".
And no internal/external testing available for the client.
Since the external testing will also need a review by Apple I went for the internal way. So I added my and the clients account to internal testing. Then I added the current build which is also in "waiting for review" state to the internal testing.
Result: It worked. I got the invite email and could download that build via TestFlight. The app is still "waiting for review".
Just in case someone else stumbles upon this question/answer here.
From answer at below link:
Will submitting a build for TestFlight Beta Testing stop the Final Review Test for the same build?
Apple will review as normal even with an active TestFlight and
external testers using it.
What apple doc at below link says:
https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/BetaTestingTheApp.html
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.
If you want to resume testing of an earlier build, you can upload it
as a new build associated with a new prerelease version.
So, when the app becomes Ready for Sale in the App Store, testing automatically stops on this and earlier builds, and you will be unable to view or test them.
You can invite users to test even when the app is in review. It will not be available only when its in store.
For external testing you need the app to be reviewed by Apple just as you publish to store but for internal testing its not required.
Send invitation to the user
Select your app
Go to TestFlight
Select Internal Testing
Click select version to test on right hand side of the screen
Select the users to send test invite
Click save
App invite will be sent to all selected users.
You always have the option to build an adhoc distribution version of your app. With this anyone who has given you there udid and it has been added to the adhoc provisioning file can install via a link or by using an .IPA file.
The major benefit of this is that the there is no review process. You build and distribute.
https://developer.apple.com/library/archive/documentation/ToolsLanguages/Conceptual/DevPortalGuide/DistributinganApp/DistributinganApp.html#:~:text=the%20App%20Store.-,Ad%20Hoc%20Distribution%20Authorizes%20a%20Limited%20Set%20of%20Devices%20to,devices%20for%20testing%20purposes%20only.&text=You%20distribute%20your%20app%20by,to%20install%20on%20their%20devices
As a first time apple developer publisher - I found the process rather easy than intimidating. I just had preconceived thoughts on the complexities that I would face if comparing to Google.Console publish.
What railon said is still true if not slightly improved since 2017 and should be accepted as an answer.
Say for example internal and external testers under TestFlight are testing the application. Then a live Appstore release that was uploaded previously gets approved. Will the current testers get the new app update which will override the current test build?
Any feedback is greatly appreciated.
Testing
Once you accept your invitation, you’ll be able to download a beta version of the app you’ve been invited to test. If you already have the live app installed on your device, the beta version of the app will replace the live version. When you’ve downloaded the beta app, you’ll see an orange dot next to its name that identifies it as a beta. TestFlight will notify you each time a new build is available and provide instructions on where to focus. You can easily offer feedback by tapping the Provide Feedback button in the App Details view in TestFlight. An email automatically opens with pertinent app and device details, and you can add additional details and screenshots.
The beta period lasts for 60 days, starting on the day it is released
to testers. In TestFlight, the number of days remaining appears below
the Open button for each app.
If a beta app has In-App Purchases, you do not have to purchase them,
as In-App Purchases made with beta builds are free within the context
of the beta version.
Quote from this link
Tester won't get notified whether the original app is approved by Apple or not. If the app is approved, then user have to download app via App Store. But if tester downloads app from App Store, then it's gonna override the test version.
Apple developer site says
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.
Refer this link
I think the tester will get an email saying the app has been updated and approved. Since the normal upload will be notified by an email, but haven't tried it ,
TestFlight testers will get notification by email and after app live beta version of app will be unavailable and when they update their app they get live update app.
I'm waiting for the design team to finish app icons, I'm wondering if I can save time and go ahead and post the first version of the app for Apple review so we can start beta testing it.
Clarification: I'm not talking about publishing my App to the store but send it for initial review to start beta testing.
EDIT
There is some controversy about Apple testing or not beta binaries but it seems they do it according this
Your app must pass Beta App Review before you can invite your external testers to test it (see Submitting an App for Beta App Review). The build will be available to them for 30 days after the invitations are sent.
TestFlight Beta Testing
Without app icon you are not able to upload the build. Application Loader will show you the error to add icons in the build.
The error message would be like below.
Missing recommended icon file - The bundle does not contain an app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format
More information :
You can/could upload another version of your app on a private store, and since there are no guidelines/prerequisites there, you could upload without a fully finished app. It would require an Entreprise account, and wouldn't "save" you much time in the review process, but it's a different way to beta test your app.
The cycle we use where I work is : upload an entreprise version for the company to test, and then submit an appstore version. This way, you have 100% control over your entreprise versioning/beta testing, and so on.