Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Neil_Enns_-_Ado
Neil_Enns_-_AdoAccepted solution
Adobe Employee
Jul 23, 2015 2:56 PM UTC

Can you start a new thread for your Android crash? It’s an unrelated issue that just makes this thread confusing ☺

Neil

11 replies

Level 2
Jul 22, 2015 9:50 AM UTC

and i dont know why it's doesn't have any icon too

Translate
Level 4
Jul 22, 2015 1:34 PM UTC

Th fact that it won't launch and based on the screenshots, it looks like your device is not provisioned. That means your device is not listed in the certificate you used to sign the app. When you sign the app, the signed app contains this list inside it. So when you try and use that is not provisioned, it will not allow it to launch.

It is a bit deceiving when one sees the app icon on the springboard. So one thinks the app is installed and everything is OK. But when your device is not provisioned you can't go that one last step into launching the app.

Make sure your device is indeed provisioned. It it is you may have to re-build or re-download and re-sign the app.

The app icon missing is strange... Maybe go ahead and start the app again on the Dashboard, download it, and sign in it. Then try that new app.

Translate
Adobe Employee
Jul 22, 2015 2:58 PM UTC

I believe the missing icon would is just another effect of the device not being provisioned. If the device were provisioned the icon would appear once the app is installed.

Translate
Level 2
Jul 23, 2015 8:46 AM UTC

actually incorrect UDID i was my first idea, and i tried another apple device. made new mobile provision, resign api file and get same result.

Translate
Level 2
Jul 23, 2015 1:16 PM UTC

Furthermore, right now i get " Unfortunaly, This App has stopped" on my android device(

Is it all cause not clean beta, or what?

Translate
Neil_Enns_-_Ado
Adobe Employee
Adobe Employee
Jul 23, 2015 1:36 PM UTC

Your troubles on iOS are one of two things:

1) Your device ID isn't in your mobile provision file

2) The certificate you used to sign isn't valid

Unfortunately iOS does not provide any useful error messages to figure out which of these two is the culprit. It's almost always the first one though because it's easy to miss the little checkbox next to the device ID when rebuilding the mobileprovision file (happens to me often).

As for Android, did you sign the app before attempting to install it?

Neil

Translate
Level 2
Jul 23, 2015 2:47 PM UTC

Neil, i made three different mobile provision file for three different devices, and every time use for this brand new certificate.....

and yes I sign the app for android, because without signing app can not be installed on device. and my crash happened after launch

Translate
Neil_Enns_-_Ado
Adobe Employee
Neil_Enns_-_AdoAdobe EmployeeAccepted solution
Adobe Employee
Jul 23, 2015 2:56 PM UTC

Can you start a new thread for your Android crash? It’s an unrelated issue that just makes this thread confusing ☺

Neil

Translate
Level 2
Jul 24, 2015 8:34 AM UTC

ok, my next move was recreate app on site with "enable newsstand" option, now it has app icon but after launch look like white snowland without any pixel.

and yes, it was made with valid certificate and mobile provision file

and published content too

Translate
Adobe Employee
Jul 27, 2015 11:48 PM UTC

It sounds like a cross-up with Newsstand settings. Newsstand is going away soon, so I think the best approach is to edit the App ID on the Apple dev site to disable Newsstand. Then rebuild your mobileprovision files, which include the App ID settings. Then rebuild your app without Newsstand enabled, sign it with the new mobileprovision file, and see if that works.

Translate