Can't Use Testflight

[kcdev]

Hello Corona Community,

I am having great trouble using TestFlight. I’ve researched the matter online extensively, but no solution found.

If my understanding is correct, you need to upload a beta build to iTunes Connect in order to use TestFlight. The irony is nowhere is it written in detail HOW to “upload a beta build” to iTunes Connect.

When I go to My Apps<<TestFlight<<iTunes Connect, it says “No Builds” in the left pane and encourages me to “Submit builds using Xcode” in the main pane.

However, when I go to Archives<<Organizer<<Window<<Xcode it says “No Archives” (which kind of makes sense, since I’ve been using Corona SDK all along and have not coded a single line in Xcode native thus far).

As such I am stuck. Is is not possible to use TestFlight when developing in Corona? If that’s the case, it is really unfortunate…

Please find the attached images below for more detail.

Thanks in advance!

[roaminggamer]

It is perfectly possible to use Corona built apps with Testflight.  I’ve done it many times.

I personally use the Application Loader to upload binaries to iTunes connect.

1. Start Xcode

2. Select menu: xCode -> Open Developer Tool -> Application Loader

Note: You won’t be able to upload until you’'ve properly prepared the app details on iTunes connect.  I will leave it to someone else to walk you through that if you need help.

Tip: Don’t be confused by the term ‘beta’.  Just upload a normal release ready binary, but don’t release it.  Instead make it available to testers via Testflight.

[anon63346430]

To add… It is important to set up iTunes as if your app was live.

As @rg points out, build your corona app and then use application loader in Xcode to push your build to the app store.

Once this is approved by Apple it can then be published via test flight.

You will need to set up your external users in advance.  Internal testers can test straight away usually.

FWIW, Google play makes this process much easier and I do all my testing that way.  I only release on iTunes when I’m done testing.

[kcdev]

Thank you guys so much for your answers. The information you provided has been invaluable to me.

So let me digest what you guys said, and please tell me if I am right/wrong.

_____________________________________

In order to use Test Flight I must…

1. Complete all app meta data in iTunes Connect >> My Apps

2. Press the “Submit for Review” button on the top right

3. Wait for Apple’s approval

4. Use Xcode to push build to app store

5. Publish with Test Flight

Is that right or did I mix/miss steps?

[rob]

There are two approval processes. The first one is their automated approval which happens automatically when you upload a binary. in 10-15 minutes you should get an email from iTunes Connect if your build passed their scanning or had problems (they do detected some problems during the upload as well). Once you get that email, you can then add your upload to test flight. You do not have to submit it to Apple’s human reviewers until you’re ready to have it go in the store.

Rob

[kcdev]

@Rob

Thanks, that helps a lot! This whole process has been rather confusing to me as it is my first time doing so…

I will post more replies should I have more questions/problems, but otherwise, I’m looking forward to marking this as “solved”!

KC

[anon63346430]

Test flight for internal testing is automatic.  For external testers things are different, Apple still needs to manually approve your build (as if it was live).

[kcdev]

@Rob
 

There are two approval processes. The first one is their automated approval which happens automatically when you upload a binary.

So I tried to upload a binary on iTunes Connet, but when I did so, the system gave me an error stating that the app cannot be submitted for review because I haven’t uploaded a build yet.

Meanwhile, @roaminggamer said in his original reply to my post:
 

You won’t be able to upload until you’'ve properly prepared the app details on iTunes connect.  I will leave it to someone else to walk you through that if you need help.

So I can’t submit for review unless I upload a build, but I can’t upload a build until it has been submitted for review? 

I am facing a bit of a catch 22 situation here…Clearly, I must be missing something?

 

[kcdev]

Also, I have another related question about @roamminggamer’s original reply:
 

1. Start Xcode

2. Select menu: xCode -> Open Developer Tool -> Application Loader

I have found and lauched the Application Loader in xCode, but I can’t seem to actually push my app to iTunes Connet using it.

No matter what file I choose, it is greyed out and unable to be selected.

My natural conclusion was .app files (generated by the building the app in Corona simulator), but that doesn’t seem to work.

What type of files does Application Loader accept?

[rob]

All Apple apps have to go through this basic process.

1. Log into the developer portral and create a key/certificate pair. Create an Application ID. For local testing/AdHoc use add in test device UDIDs and then make one (or all three) of three provisioning profile types:  Developer: for local testing development, AdHoc: for local distribution such as making business for your company that won’t be release, Release: For the store.  You need to get these provisioning profiles into your ~/Library/MobileDeivce/Provisioning Profiles folder. Xcode can do this for you, or you can Download them and move them to that folder. Restart Corona.

2. Next, log into iTunes Connect (through the Apple Developer Portral) and create your app there. It will tie it to the Bundle ID you created when you created the app in step 1. Create your description, upload screen shots, setup IAP, GameCenter etc. Too much of this varies to go into any detail. But you have to have the core framework in place.

3. Using the Corona simulator, build your app, choose “Upload to App Store” as the post build actions and make sure you use a for the store type release profile (not AdHoc, not Development).  This should produce a .ipa file. Application Loader will start, navigate to the folder where you output the build, select the .ipa file and let Application Loader upload it.

4. Application Loader may find issues and report them.  If it succeeds, it will be sent to Apple’s automatic testing. In 5-10 minutes you should get an email saying that its done. At that point you can go into Testflight and send it to your testers. As suggested, external testing may require a submission to Apple to approve it for external testing, but not for internal testers.

You shouldn’t have to fight any other issues or jump through any other hoops or deal with Xcode or other file types.

Rob

[roaminggamer]

It is perfectly possible to use Corona built apps with Testflight.  I’ve done it many times.

I personally use the Application Loader to upload binaries to iTunes connect.

1. Start Xcode

2. Select menu: xCode -> Open Developer Tool -> Application Loader

Note: You won’t be able to upload until you’'ve properly prepared the app details on iTunes connect.  I will leave it to someone else to walk you through that if you need help.

Tip: Don’t be confused by the term ‘beta’.  Just upload a normal release ready binary, but don’t release it.  Instead make it available to testers via Testflight.

[anon63346430]

To add… It is important to set up iTunes as if your app was live.

As @rg points out, build your corona app and then use application loader in Xcode to push your build to the app store.

Once this is approved by Apple it can then be published via test flight.

You will need to set up your external users in advance.  Internal testers can test straight away usually.

FWIW, Google play makes this process much easier and I do all my testing that way.  I only release on iTunes when I’m done testing.

[kcdev]

Thank you guys so much for your answers. The information you provided has been invaluable to me.

So let me digest what you guys said, and please tell me if I am right/wrong.

_____________________________________

In order to use Test Flight I must…

1. Complete all app meta data in iTunes Connect >> My Apps

2. Press the “Submit for Review” button on the top right

3. Wait for Apple’s approval

4. Use Xcode to push build to app store

5. Publish with Test Flight

Is that right or did I mix/miss steps?

[rob]

There are two approval processes. The first one is their automated approval which happens automatically when you upload a binary. in 10-15 minutes you should get an email from iTunes Connect if your build passed their scanning or had problems (they do detected some problems during the upload as well). Once you get that email, you can then add your upload to test flight. You do not have to submit it to Apple’s human reviewers until you’re ready to have it go in the store.

Rob

[kcdev]

@Rob

Thanks, that helps a lot! This whole process has been rather confusing to me as it is my first time doing so…

I will post more replies should I have more questions/problems, but otherwise, I’m looking forward to marking this as “solved”!

KC

[anon63346430]

Test flight for internal testing is automatic.  For external testers things are different, Apple still needs to manually approve your build (as if it was live).

[kcdev]

@Rob
 

There are two approval processes. The first one is their automated approval which happens automatically when you upload a binary.

So I tried to upload a binary on iTunes Connet, but when I did so, the system gave me an error stating that the app cannot be submitted for review because I haven’t uploaded a build yet.

Meanwhile, @roaminggamer said in his original reply to my post:
 

You won’t be able to upload until you’'ve properly prepared the app details on iTunes connect.  I will leave it to someone else to walk you through that if you need help.

So I can’t submit for review unless I upload a build, but I can’t upload a build until it has been submitted for review? 

I am facing a bit of a catch 22 situation here…Clearly, I must be missing something?

 

[kcdev]

Also, I have another related question about @roamminggamer’s original reply:
 

1. Start Xcode

2. Select menu: xCode -> Open Developer Tool -> Application Loader

I have found and lauched the Application Loader in xCode, but I can’t seem to actually push my app to iTunes Connet using it.

No matter what file I choose, it is greyed out and unable to be selected.

My natural conclusion was .app files (generated by the building the app in Corona simulator), but that doesn’t seem to work.

What type of files does Application Loader accept?

[rob]

All Apple apps have to go through this basic process.

1. Log into the developer portral and create a key/certificate pair. Create an Application ID. For local testing/AdHoc use add in test device UDIDs and then make one (or all three) of three provisioning profile types:  Developer: for local testing development, AdHoc: for local distribution such as making business for your company that won’t be release, Release: For the store.  You need to get these provisioning profiles into your ~/Library/MobileDeivce/Provisioning Profiles folder. Xcode can do this for you, or you can Download them and move them to that folder. Restart Corona.

2. Next, log into iTunes Connect (through the Apple Developer Portral) and create your app there. It will tie it to the Bundle ID you created when you created the app in step 1. Create your description, upload screen shots, setup IAP, GameCenter etc. Too much of this varies to go into any detail. But you have to have the core framework in place.

3. Using the Corona simulator, build your app, choose “Upload to App Store” as the post build actions and make sure you use a for the store type release profile (not AdHoc, not Development).  This should produce a .ipa file. Application Loader will start, navigate to the folder where you output the build, select the .ipa file and let Application Loader upload it.

4. Application Loader may find issues and report them.  If it succeeds, it will be sent to Apple’s automatic testing. In 5-10 minutes you should get an email saying that its done. At that point you can go into Testflight and send it to your testers. As suggested, external testing may require a submission to Apple to approve it for external testing, but not for internal testers.

You shouldn’t have to fight any other issues or jump through any other hoops or deal with Xcode or other file types.

Rob