App Installs OK for my iPhone - fails for testers

Solar2D iOS
#1

Build 2015.2669

Development machine = Apple MacBook Pro

OS X 10.10.4 (14E46)

My builds for iOS and Android (Windows generated) complete successfully. The iOS build lists 8.4 as iOS SDK.

ANDROID - installs ok onto my Android tablet; works “as advertised”

I have 4 devices registered with Apple via UDID, including my own iPhone.

iOS installs are the issue. In all cases (mine and the testers), the installs are via iTunes - and syncing the iPhones to iTunes.

The .app file synchs to MY own iPhone consistently and functions fine when opened. But when I send the .zip file to my iPhone testers, they are complaining that my .app file will not install successfully. The sync process starts but never finishes. When I sync from my MacBook Pro to my own iphone, the sync-ing is fast.

QUESTION 

What are the critical settings I should check on my Testers’ laptops, apple desktop units and/or their iPhones?

Obviously, it’s bothersome that my installs work fine but my Testers’ fail.

Is there something “special” about being the developer so that my stuff works but fails when it goes to another device?

Thanks for any hints.

Seth 

#2

Hi Seth,

I seem to recall (of course, I can’t find it now) that you need to “enable the device for development” or something. I think it’s done in iTunes, but again, it was something I did long ago when I got the device, and now looking in iTunes, I can’t find any way to “disable” it for development. If I recall, it’s a step you do once, then that makes the device applicable for testing. Perhaps your testers have not done that?

Sorry I can’t be of more help, but nothing else you describe above brings up any red flags.

Brent

#3

It could be that the distribution profile you are using to build your app does not have a provisioning profile in it that includes the UDIDs of your testers’ devices.  You say you “registered” them, but y can’t tell if that means you added them to a provisioning profile and are using that profile in your distribution profile.  See here for details: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/TestingYouriOSApp/TestingYouriOSApp.html

#4

tonygod - nice/effective hint. I think that resolved the iPad “not installing” issue one tester was encountering. Your hint led me back to the Apple Development Center and my own settings.

Originally, I had registered four iPhone UDIDs for use in my Development/Production environments. Initially, I generated the .mobileProvision file and have been using that successfully for the iPhones. But, later, when I added the additional iPad, I neglected to re-issue a new .mobileProvision file - so I’m assuming this prevented the iPad from fully installing my app.

I have re-issued the .mobileProvision file with the iPad included - and am awaiting word from the Tester but am hopeful this resolves the issue. I am waiting to hear back from the Tester before assigning this as a Best Answer response.

thanks bunches, tonygod!

PS: Brent, methinks this is what you were alluding to when you offered your hint. 

#5

I was 100+% certain that finding the device unchecked in Apple Development Center, checking it - and re-issueing the .mobileProvision file would resolve the issue.

no cigar, he says. didn’t work.

I had done an iPhone+iPad build. installs OK via ITunes sync with my own iPhone.After syncing, I open up he app on my iPhone and when tapped, it opens immediately and works as advertised.

but my Tester says that he 1) expands my .zip file which contains the .app file); adds the .app file to ITunes and synchs. but when he opens it up on iPad OR iPhone, he gets feedback that it’s installing - and nothing happens. Again, on my iPhone, there’s no “installing” message; it’s installed and opens up immediately.

I double-clicked the .mobileProvision file downloaded from Apple Dev Center - but maybe i didn’t do enough. I will review steps re what to do with mobileProvidision file after being downloaded.

Stay tuned.

#6

How did your tester install the provisioning profile?  I just went through the “exact” (in all instances), situation and it turned out that when I emailed my tester the provisioning profile, he opened the email via his iPad and clicked/touched the provisioning profile thinking that it installed, but it hadn’t.  When he added the app to the iTunes library and sync’d, the app looked like it finish installing, but never did (greyed out).  I instructed him to add the provisioning profile to his iTunes library (like he adds the app to iTunes library) and sync… Viola, that worked and the app finished installing and launched/functioned as advertised.

#7

Try using Installr? It handles the provisioning profile updates automatically. No need to use iTunes, etc.

#8

douglascavanaugh -

You get the bonus on this one - adding the .mobileProvision file to iTunes was the final missing ingredient. Thanks bunches for passing by - and leaving the hint. Sincerely appreciated!

Seth

#9

Hi Seth,

I seem to recall (of course, I can’t find it now) that you need to “enable the device for development” or something. I think it’s done in iTunes, but again, it was something I did long ago when I got the device, and now looking in iTunes, I can’t find any way to “disable” it for development. If I recall, it’s a step you do once, then that makes the device applicable for testing. Perhaps your testers have not done that?

Sorry I can’t be of more help, but nothing else you describe above brings up any red flags.

Brent

#10

It could be that the distribution profile you are using to build your app does not have a provisioning profile in it that includes the UDIDs of your testers’ devices.  You say you “registered” them, but y can’t tell if that means you added them to a provisioning profile and are using that profile in your distribution profile.  See here for details: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/TestingYouriOSApp/TestingYouriOSApp.html

#11

tonygod - nice/effective hint. I think that resolved the iPad “not installing” issue one tester was encountering. Your hint led me back to the Apple Development Center and my own settings.

Originally, I had registered four iPhone UDIDs for use in my Development/Production environments. Initially, I generated the .mobileProvision file and have been using that successfully for the iPhones. But, later, when I added the additional iPad, I neglected to re-issue a new .mobileProvision file - so I’m assuming this prevented the iPad from fully installing my app.

I have re-issued the .mobileProvision file with the iPad included - and am awaiting word from the Tester but am hopeful this resolves the issue. I am waiting to hear back from the Tester before assigning this as a Best Answer response.

thanks bunches, tonygod!

PS: Brent, methinks this is what you were alluding to when you offered your hint. 

#12

I was 100+% certain that finding the device unchecked in Apple Development Center, checking it - and re-issueing the .mobileProvision file would resolve the issue.

no cigar, he says. didn’t work.

I had done an iPhone+iPad build. installs OK via ITunes sync with my own iPhone.After syncing, I open up he app on my iPhone and when tapped, it opens immediately and works as advertised.

but my Tester says that he 1) expands my .zip file which contains the .app file); adds the .app file to ITunes and synchs. but when he opens it up on iPad OR iPhone, he gets feedback that it’s installing - and nothing happens. Again, on my iPhone, there’s no “installing” message; it’s installed and opens up immediately.

I double-clicked the .mobileProvision file downloaded from Apple Dev Center - but maybe i didn’t do enough. I will review steps re what to do with mobileProvidision file after being downloaded.

Stay tuned.

#13

How did your tester install the provisioning profile?  I just went through the “exact” (in all instances), situation and it turned out that when I emailed my tester the provisioning profile, he opened the email via his iPad and clicked/touched the provisioning profile thinking that it installed, but it hadn’t.  When he added the app to the iTunes library and sync’d, the app looked like it finish installing, but never did (greyed out).  I instructed him to add the provisioning profile to his iTunes library (like he adds the app to iTunes library) and sync… Viola, that worked and the app finished installing and launched/functioned as advertised.

#14

Try using Installr? It handles the provisioning profile updates automatically. No need to use iTunes, etc.

#15

douglascavanaugh -

You get the bonus on this one - adding the .mobileProvision file to iTunes was the final missing ingredient. Thanks bunches for passing by - and leaving the hint. Sincerely appreciated!

Seth