I have uploaded build on TestFlight beta iTunes. Its status is showing "Created" to me instead of Processing . Does any one know about build status "Created" ? What does this mean ? Does apple need to review ?
You need to wait a bit, Apple is still finishing the touches on uploading and processing your build from the image you attached. You'll be able to tick a selector to the activated position (green) next to beta testing for the version when they are done. Then you'll be able to test it yourself and after they review it (in my experience it takes about a day) then you can invite external testers.
Check this image of one of my apps for reference.
The developer build versions will be made available to testers only after review by Apple.
In my case the builds were approved within 8 hours and i was able to invite the testers to test the build.
Related
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).
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.
Having submitted a beta version of my IOS App trough Itunes Connect and Testflight to INTERNAL users, and selected it for testing to EXTERNAL users, it displays "waiting beta app verification" (from Internal users) and I don't know how to release the app for EXTERNAL User. (see pict enclosed).
It did worked on past version but I don't know how ... times, upload from Internal users, approval from them (but don't know how).
Need to re-test then submit my app quickly, any help welcome !
NOTE : Apple displays help on old itune connect versions, and don't see where this can be done. See here
Apple says:
Upload a build for the app. See Uploading a Build for an App.
Add App Description and What to Test to the build. This step is optional for releasing your builds to internal testers, but required
when submitting your app to Beta App Review for external testing. See
Add Metadata for your Prerelease App.
Distribute the app to internal testers.
Submit the app for Beta App Review, and distribute it to External users.
You need to have every build reviewed from apple for distribution to external testers.
I'm not sure how it worked earlier, but for now
All builds distributed to external testers must pass through an Apple review. While these reviews do not fall into the same queue as those submitted for App Store release, they can take time.
In other words, you have to use button "submit for beta app review" ;)
You can find guides here: Ray Wenderlich or kyleclegg.com
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.
now i am using test flight for testing my application.Testflight said from next month onwards standard test flight is not available.SO i have some doubt on this please clarify
-Standard test flight is available for already existing apps or not?If available can i release new build?
-How can i test the ios 7 apps with test flight beta testing.
-Apple saying,each prerelease version expires after 30 days.So after 30 days can i test downloaded app?
-Suppose i released build A and installed in some devices and after 10 days again i released build B and installed on some other devices.Both are working or only latest Build B is working?
-Each internal tester can test the app in 10 devices,So how we can register that devices.
-Each version we have to wait for beta app review for external testers?
If any information is useful for me please post except these questions.
-Standard test flight is available for already existing apps or not?If available can i release new build?
The original TestFlight is being shut down. Apple's TestFlight is the new TestFlight and you can use it with existing apps.
-How can i test the ios 7 apps with test flight beta testing.
You can't. TestFlight is iOS 8 only.
-Apple saying,each prerelease version expires after 30 days.So after 30 days can i test downloaded app?
This means that the build expires in 30 days. You have to keep submitting new builds for your testers.
I find this good way to keep your testers really up to date and up to the task. In contrast, if build didn't expire, the beta testers could stick to the old versions and eventually become a burden (irrelevant bug reports, etc.).
-Suppose i released build A and installed in some devices and after 10 days again i released build B and installed on some other devices.Both are working or only latest Build B is working?
I think the old build A will continue working for the aforementioned 30 days when you submit the new build. You simply can't revert back to it. I'm not absolutely sure though, but there is a transition time for beta testers to update to the new version.
-Each internal tester can test the app in 10 devices,So how we can register that devices.
I haven't had any internal testers but my guess is that the usual way: add the devices from the developer portal.
-Each version we have to wait for beta app review for external testers?
Yes. However, if the new builds have no major modifications they might not need to wait for the review process. This is being asked when you submit consecutive builds.
I think there is a chance of review even with small updates, but I haven't seen any. I've had new builds ready to distribute within the same hour every time I submit a minor update.
Recently, the All-New TestFlight Beta Testing service was launched inside of iTunes Connect.
Here's What's New:
Invite up to 1,000 external testers using just their email address
Easy to use TestFlight iOS app available on the App Store
No need to keep track of UDIDs or provisioning profiles
Beta testing directly inside of iTunes Connect without the need of the TestFlight SDK
Learn more ยป
With the new version of the TestFlight service available inside of iTunes Connect, we are also informing you that TestFlightapp.com will no longer be available as of 2/26/2015.
To prepare for the TestFlightapp.com closure, we recommend that you export all of your current testers so you can import them directly into the new TestFlight Beta Testing service.
How to export testers from TestFlightapp.com
Sign in to the TestFlight Dashboard at testflightapp.com
Navigate to the "People" tab
Check mark the teammates you would like to export
Open the "Actions" menu on the right side of the teammates list
Select "Export Contact Info" to download the exported CSV file
How to import testers into the new TestFlight Beta Testing
Sign in to iTunes Connect at itunesconnect.apple.com
Click "My Apps"
Select the app you want to enable for beta testing
Enter the "Prerelease" tab and select "External Testers"
Click the plus sign to add new external testers
Use the "Import File" from the "Add New External Testers" page to upload the exported CSV file
Hope this information helps you.
-Standard test flight is available for already existing apps or not?If available can i release new build?
Standard Test flight app is completely shut down. You cannot use it anymore.
-How can i test the ios 7 apps with test flight beta testing.
Testflight beta testing is not available for iOS 7 apps.
-Apple saying,each prerelease version expires after 30 days.So after 30 days can i test downloaded app?
Yes, you can continue testing already downloaded app. 30 days is the active period for downloading app.
-Suppose i released build A and installed in some devices and after 10 days again i released build B and installed on some other devices.Both are working or only latest Build B is working?
Both will continue to work but after uploading release B, build A will be deactivated for downloading. Only latest uploaded builds will be active.
-Each internal tester can test the app in 10 devices,So how we can register that devices.
When you accept the invitation from any device, the device gets registered.
-Each version we have to wait for beta app review for external testers?
Yes, you need to wait for approval then only you can distribute app to external testers.