Skip to main content
B
brighttext
Known Participant
April 12, 2015
Answered

ApplicationVerificationFailed error

  • April 12, 2015
  • 1 reply
  • 1794 views

I've been getting this error for past 2 days and have tried everything I can think of. I have revoked old certs and created new ones, along with new provisioning profiles.  I did this for distribution, ad hoc, and dev.  When I try to import the dev .cer file into keychain access, it doesn't seem to do anything -- I've tried both 'import' and just double-clicking the .cer file. I've tried deleting all old certificates, thinking that perhaps they were somehow cached and weren't updating with the new import. Didn't work.

When I run using dev .p12 and provisioning, I get "The signing certificate is not from the expected issuer". So I'm trying now to debug using Ad Hoc, which has worked in the past. But I just get the ApplicationVerificationFailed error.  I have removed beta entitlements from the descriptor, as I've read that that can be an issue.

Does anyone have any ideas?

Thanks.

This topic has been closed for replies.
Correct answer nowickim

If you've confirmed that your certificates and provisioning profiles are all good and are still getting this, I determined that you will receive this exact same error if you have your app configured for TESTFLIGHT.  In other words, in your APPNAME-app.xml make sure that the following is commented out within the IOS entitlements section:

    <key>beta-reports-active</key>

  <true/>

Once I commented that out, I was able to resume debugging locally.  Pissed that I spent a day on this, but at least it's working now.

1 reply

N
nowickimCorrect answer
Inspiring
April 23, 2015

If you've confirmed that your certificates and provisioning profiles are all good and are still getting this, I determined that you will receive this exact same error if you have your app configured for TESTFLIGHT.  In other words, in your APPNAME-app.xml make sure that the following is commented out within the IOS entitlements section:

    <key>beta-reports-active</key>

  <true/>

Once I commented that out, I was able to resume debugging locally.  Pissed that I spent a day on this, but at least it's working now.

B
brighttextAuthor
Known Participant
April 25, 2015

Yes, thanks, I discovered the same thing.

I also discovered that, even if you change provisioning profiles, if you're still getting errors you should try renaming your mobileprovisioning profile. Even though you've created new certs, exported .p12, and downloaded new provisioning profile, you may still referencing the earlier same-named earlier of the provisioning profile -- the cached version.

One other thing -- you will also see this message if you have the incorrect id in your descriptor file -  <id>com.whatever.myappname</id> . I had to do change this id between the android version and the ios version (for an irrelevant reason). If I forget to change it back to what it should be for each platform, I see that error.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices