1 person found this helpful
This has almost always come down to an application ID is set improperly in the app XML <id> attribute or a certificate issue (mobileprovision assigned to dev cert not dist cert, etc). The new provisioning profile should be stopping you from that however.
Are you using any services like APNS but use a wildcard app ID?
If you publish but select Ad-Hoc (dist not dev) instead of package for store, does it install on your device?
Hi sinious. Thank you for replying. I was taking care of each aspect you point out. I was using an "Explicit App ID", I was using the proper certificate with the proper PP. I had the cert on my mac and I was exporting it with "Keychain Acces". Finally I found that I could generate and export an "iOS Distribution Signing Authorithy" on Xcode. When i did that, things worked again! Thank you.
Glad you got it working, you're welcome and good luck!
1 person found this helpful
I encountered this same error and what the problem is is that when you go to create the App ID through the Apple Developer website you created an iOS App ID you gave it a name and an ID. The ID per Apple's recommendation is in the format of: com.XXXX.XXX for example com.jsebrey.demo.
So, in Flash in the AIR for iOS settings underneath the Provisioning Profile is App ID and if you don't put anything in there by default the name of your Flash file will be put in there. If you are getting the error when publishing using AIR for iOS you need to change the App ID from the default to the App ID you created on the Apple Developer website and my example is: com.jsebrey.demo.
If this App ID does not match the App ID you created at the Apple Developer website you will get the error: "iPad: The device has encountered an unexpected error. Installation Error: ApplicationVerificationFailed".
It's a simple easy fix and does not require going through Xcode in any way. Just make sure that the App ID in the Publish Settings matches the App ID you created through Apple's Developer website.
I hope this helps others who are getting this error as well. I've encountered it a couple of times and I finally realized what the error was and as soon as I did and I made the necessary changes and Published again, everything worked. No problems.
On my side the solution was to move the project to a new clean Workspace.
I'm using Flash Builder 4.7 and AIR 19 for building (although at the time of the writing AIR 20 is available, AIR 19 is used due to wider coverage on both iOS and Android versions)
The weird thing is that in the original Workspace the compiling of the final release build worked like a charm. The issues were poping-up while trying to build the debug version. In that case the process run smoothly until it came to the moment of installing the app on the device. At that point the ApplicationVerificationFailed was triggered without no clue of why that was happening. The result was a compiled app, but no way of actually debugging it.
Although there is here an article about the iOS issues: Troubleshooting common Adobe AIR installation errors with iOS applications it was of no help to me.
This error seems to pop-up randomly (which makes it very annoying).
Hope my solution will help you save some time while developing and trying to debug iOS apps.