testflight - "Unable to Download App"

Solar2D General Questions/Discussion
#1

I’m using testflight.  I’ve used it in the past with corona successfully, but that was over a year ago. 

I built my app, uploaded it to testflight, and then got this error on three different ios devices when I tried to download the app via testflight. 

The error I get is:

 

Unable to download App

“Name of App” could not be installed at this time.

To test the certs on my build, I plugged one of the devices into my mac and installed the same app via itunes successfully.  So it doesn’t seem like it’s a cert issue on the app.  Any ideas?  on Testflight’s site, they say this is a generic error that could be caused by like fifteen things.  None of which jump out as my issue.  I’m wondering if anyone else has used testflight with a corona app recently that could shed any light on this issue.

#2

In my experience test flight is quite unstable sometimes.

I saw this error a couple of times, but managed to install it simply by trying again some hours later.

But as you say it is a generic error so this might not be the case for you.

#3

bumping this topic.  Haven’t heard back from Test Flight yet, although they don’t work weekends, and it’s a holiday today… but if anyone else has worked through this issue (besides just trying it a day later, which I’ve done), I’d love to hear from you.

#4

I haven’t had any issues with using testFlight at all… Follow these steps:

  1. First I create a new Adhoc provisioning profile from apple (make sure you have selected all the UDID’s/devices you plan on having access to the app then download/install it).

  2. Then I open corona, open my project > build using the new Adhoc provisioning profile.

  3. Once built, create a folder on your desktop called “Payload” place your recently compiled .app file in there and then compress the Payload folder into a .zip > then rename the .zip into .ipa (if it asks are you sure you want to change extension, just click yes).

  4. Then upload that new Payload.ipa file into testFlight

  5. Once uploaded (you should be redirect to permissions tab page) you must select all devices you want to have use this app and then click “Update and Notify All” - boom done. the link to share will be listed below

#5

@eja - thanks for posting the instructions.  But those are the exact same instructions I followed to the ‘T’.  They’re the same instructions I followed a year ago when I last did this and it worked successfully.  I know my certs are ok, because I’m able to install the build via iTunes, just not via TestFlight.  I’ve sent my logs to test flight to see if they can shed any light on it.  There wasn’t anything jumping out of my logs at me.  My biggest concern is that it may have to do with how the corona build, which is why I’m asking on the forum if anyone’s been successful or unsuccessful with a corona to test flight build recently.

#6

Hmm… that’s odd, I packaged mine just yesterday with build 2170 (only because 2171-2179 has an android network bug).

#7

I’m running build 2155 currently, I think I’ll get the 2170 build and try that.

#8

I did another build using build  2170. 

I also noticed that I named the folder “payload” instead of “Payload”, not sure if the new version of corona made the difference or if the upper case P matters. 
Either way, the new build worked via TestFlight.  Hope this helps anyone in the future.

#9

In my experience test flight is quite unstable sometimes.

I saw this error a couple of times, but managed to install it simply by trying again some hours later.

But as you say it is a generic error so this might not be the case for you.

#10

bumping this topic.  Haven’t heard back from Test Flight yet, although they don’t work weekends, and it’s a holiday today… but if anyone else has worked through this issue (besides just trying it a day later, which I’ve done), I’d love to hear from you.

#11

I haven’t had any issues with using testFlight at all… Follow these steps:

  1. First I create a new Adhoc provisioning profile from apple (make sure you have selected all the UDID’s/devices you plan on having access to the app then download/install it).

  2. Then I open corona, open my project > build using the new Adhoc provisioning profile.

  3. Once built, create a folder on your desktop called “Payload” place your recently compiled .app file in there and then compress the Payload folder into a .zip > then rename the .zip into .ipa (if it asks are you sure you want to change extension, just click yes).

  4. Then upload that new Payload.ipa file into testFlight

  5. Once uploaded (you should be redirect to permissions tab page) you must select all devices you want to have use this app and then click “Update and Notify All” - boom done. the link to share will be listed below

#12

@eja - thanks for posting the instructions.  But those are the exact same instructions I followed to the ‘T’.  They’re the same instructions I followed a year ago when I last did this and it worked successfully.  I know my certs are ok, because I’m able to install the build via iTunes, just not via TestFlight.  I’ve sent my logs to test flight to see if they can shed any light on it.  There wasn’t anything jumping out of my logs at me.  My biggest concern is that it may have to do with how the corona build, which is why I’m asking on the forum if anyone’s been successful or unsuccessful with a corona to test flight build recently.

#13

Hmm… that’s odd, I packaged mine just yesterday with build 2170 (only because 2171-2179 has an android network bug).

#14

I’m running build 2155 currently, I think I’ll get the 2170 build and try that.

#15

I did another build using build  2170. 

I also noticed that I named the folder “payload” instead of “Payload”, not sure if the new version of corona made the difference or if the upper case P matters. 
Either way, the new build worked via TestFlight.  Hope this helps anyone in the future.