This is the error I'm getting when I try to install my app on my iPhone.
More details:
It did work at one point. I used a different computer recently, working on a different project and had to create a new certificate. This invalidated my other projects (profiles). I went back to working on the first computer and uploaded the certificate from that one. I recreated the app profiles and downloaded the provisioning files based on that previous certificate. None of that worked. In the end I had to start over from scratch as shown in the answer below.
I finally got it to work by starting over from scratch. I think the problem was that when I went to a new computer and uploaded a new certificate I had to revoke the old certificate. It seems that once it's revoked that maybe it can't be used again.
So I recreated my signing certificate, recreated a p12 file from it, recreated (modified) the app profile (making sure to select my certificate again and selected all of my devices again), redownloaded the mobile provisioning file, reselected these in the iOS configuration screen and restarted Flash Builder and it worked again.
I had tried to use a wildcard, "com.myactualdomainhere.*" and I couldn't get that to work but I didn't do all the steps above (I didn't recreate my signing certificate) and if you can't reuse a certificate then that may have been the issue.
So I did all the steps above and used the app name, "com.myactualdomainhere.MyApp" and made sure it matched in the application descriptor file (for AIR apps) com.myactualdomainhere.MyApp.
It would be nice if someday they could simplify this process and give better error messages. Maybe they could verify the different parts along the way, for example, "your certificate is ok, your app profile checks out, but your app id is incorrect."
Also, MilkyWay posted a link to a post that has some more helpful information.
I experienced this error working with code from another vendor. As it turns out, they were trying to compile the IPA with an Entitlements.plist file. I just deleted that block of code (below) and it compiled just fine.
<Entitlements>
<![CDATA[
<key>get-task-allow</key>
<true/>
]]>
</Entitlements>
I've just been stuck with this problem this morning, took a while to figure out so thought I'd post incase anyone else has the same issue.
We had a problem adding a device to our provisioning profile, an iPhone 5 on iOS7. It turned out that the application we were using to get the UDID (UDID+) was giving us the wrong UDID. When I used the ID returned by
adt -devices -platform ios
It worked.
In my case it was at matter of unaccepted characters in some embedded folders. Folder names that contained special characters (æ ø å or whitespace) resulted in an ApplicationVerificationFailed error. (Not exactly the most precise error description I have encountered.)
I know this is an old thread, but if anyone else is Googling around and finds this thread and it does NOT fix your issue, I wanted to share my experience on this one. 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.
This can also happen if you change your Apple ID password.
My problem was that in my Application ID under apple developers, my app wasn't checked for PushNotification, but within my xml application descriptor, I had the entitlments for push notifiaction (aps_development).
Once à removed the APS value from my XML, worked all good.
If you haven't compiled in a long time, be sure you set your compilation settings to device testing and make sure you are using your testing provisioning profile. I got this today because my settings were still on app store.
The problem for me was that I was using a .p12 file which was meant for Apple Push Notifications instead of the .p12 file of my Developer certificate..
I used the .p12 I exported from my developer certificate and it works great..!
In my case it was incorrect application id problem (different compiled app id then app id I have defined apple)
sometimes this error occurs because of you bin-debug folder.
if that folder has some unknown character or something this error occurs.
I suggest if in that case you have to clean the project or find that file and change it's name
If it was working previously, just restart the flash builder.
I did some tests today on test flight with the Entitlements tags. It need to be remove when testing localy or I get the same error.
Like jbyun94 mentionned, get rid of unknown characters in filenames.
I had files in conflict from dropbox that prevented the app from compiling.
Removed them and everything worked again (though I'd lost a couple of hours :/)
Related
I don't remember this has happened to me before, but for some unknown reason my last app build does not appear in TestFlight. The archiving and upload went as usual with no problem. And if I try to make a new upload, it says there is already a build with this number (as expected).
Has anyone experienced the same issue and found a working solution?
Check email linked with apple account, you might have received email listing with issues apple found on your build which most of the times related to .plist file for any missing permission description. After removing issues do change the build Number as you cannot upload with the same build number as previous one.
Besides the reason mentioned by Ali there can be one more thing. Your application might be on processing for the time. Just go to:
Your application>TestFlight>Activity
Check if application with uploaded build version is there and status is in processing. It may take up to and hour or more before it come to your testing tab.
I could fix the problem by adding this key "App Uses Non-Exempt Encryption" in Info.plist
App Uses Non-Exempt Encryption = NO
We encountered the same issue and here is our breakdown of steps.
Important note - phone connects to BT device
Our steps: Solution is under 4. and 6.
Archive the app and upload it over Xcode successfully
Used automatic signing
Everything went smoothly, and Xcode showed a successful upload
Build never shows up on TestFlight
There are no emails about failed processing or any indication of what went wrong
Accidentally found that we’re missing Bluetooth privacy string in Info.plist
Added NSBluetoothAlwaysUsageDescription, archived, and uploaded again
Used automatic signing
Everything went smoothly, and Xcode showed a successful upload
Received an email from AppStoreConnect that Info.plist is missing NSBluetoothPeripheralUsageDescription
This is the first email I received stating something is wrong. Only after adding NSBluetoothAlwaysUsageDescription
Added NSBluetoothPeripheralUsageDescription, archived, and uploaded again
Used automatic signing
Everything went smoothly, and Xcode showed a successful upload
Build visible on TestFlight within several minutes
:party
The issue was that the app was crashing because it was missing the string. The app did not crash on our testing device because that string was once there and the system already asked the user for permission. The field was probably accidentaly deleted during development.
To find similar issues, try to delete the app from your device and install it again to see if it runs.
I have also faced this issue before, tried all the fixes had not received any mail from apple about what the issue is, but finally fixed the issue after making changes in the info.plist file the issue was that description was missing in info.plist file, mostly it occurs because of that check the file again.
I was also facing the error when I make a build and upload it to the app store it display successfully on Xcode. but the build was not appearing on the app store test flight. then I check my email where the app store team was indicating my issue clearly. in my case, my app name contains a white space on starting.
I am trying to start my app on a device and faced with this. It doesn't depend on signing method. Push notifications feature enabled for the App ID in Developer account, valid APNS certs added. On the capabilities tab everything is OK.
I know what is aps-environment (this string presents in generated profile), but what does Xcode mean by environmentProd string? I can't find out just anything about "aps-evironmentProd".
The application started without any troubles on previous Xcode versions. For me it seems like regular Xcode bug. How can I handle this without Xcode downgrade?
Entitlements
It seems you have changed/updated APS Environment to APS EnvironmentProd in your .entitlements file.
Check your .entitlements again to be sure. If not just restart Xcode.
Also, I am assuming you already know following:
No need to update development to production in.entitlements`. Because we can't use the production certificate in debug/development.
When we do 'Archive' Xcode automatically set it to production.
I see this is old question but still I wanted to provide an answer as I had same problem.
I did try so many options, recreated provisions, certificates edit manually entitlements and nothing worked.
At the end I created new project with same name as my original app did all setup a nd there was no eny error for entitlements.
I have Uploaded app into appstoreconnect and tested all worked fine.
Then I copied entitlements file and appdelegeate into my original app and no errors after.
I had a small app I wanted a friend to test, he's far away, so back then, I used ota distribution, I followed a step by step explanation and it went good.
I upgraded my app to ios8 among other updates in it, and I want to do the same : put it in my website, I searched for information about this, but all I got was outdated tutorials / informations.
I suppose I did allmost everything correctly :
created an app id
had the udid of my friend and some others on apple's website.
made a distribution (or provisionning or whatever they're called) certificate using this app id and my list of udid.
downloaded it and put it in my keychain.
told xcode to sign with it on release
archived it
saved it for ad hoc distribution
so there I should only move the .plist .ipa to my site and point my tester to this site, but it doesn't work. First, organizer only outputs a .ipa file when it used to generate a .plist and a .ipa and it used to ask for two images. I read somewhere that xcode 6 only exports a ipa now, so I tried using my newly made ipa and put it on my site along with my old .plist and it failed with the following error message : "the applications can't be installed because [mysite]'s certificate is invalid." (translated from french), that would imply I didn't use the right certificate to sign my release, but I'm quite sure I did.
in conclusion, I'm really lost, and I think I should restart the whole process, so any pointers to an up to date step by step tutorial, or some quick explanation of what I'd be missing / doing wrong would be much appreciated.
Just to notice,
Remember your plist should be in an "https" server. If you don´t have an https server with a valid certificate you could upload your plist to a dropbox public link (this works perfect).
After following the great tutorials from http://www.raywenderlich.com/ on how to submit your app to the app store from square one I started planning my beta test program.
I'm not going to get into details of everything that wen well but of what I'm dealing with right now.
I've read many many posts on how to create provisioning profiles for ad hoc distribution of my app to beta testers. I've focused on those helping user get the app over the air (OTA) after a forum recommendation.
I also know now that TESTFLIGHT is out there but I can't use it this time.
Everything works well except the part where the application actually gets installed on my device. I keep getting the error "Unable to Download Application" after a few seconds of pressing "Install".
There are several possibilities and combinations of certificates, profiles, signatures, and here is where I think I'm doing something wrong. I'd like to show you what I have and what I've done and maybe your experienced eyes can spot my missing step or misconfiguration.
On the iOS Provisional Portal:
1) Ad Hoc distribution profile with a couple of devices:
2) After I download and install my certificates (I've create a couple of each for testing purposes):
3) On my xCode's project configuration:
4) When I generate the archive:
5) I upload everything to my server and then try to get the .ipa to install on my iPhone (which is one of the two devices included on the profile)
And finally I get this:
What could be wrong?
The only difference I can see is in the CodeSigning, ensure both lines under Adhoc point to your certificate.
Second thing to verify: You did not mention the plist that is created during the "Save for Enterprice". Did you upload that to your server, too? And does your link point to this plist? Check out this answer for the plist stuff: How to send the build to already provisioned remote person's iPhone
I've had this exact problem even where, like you (as far as I can tell), everything is done right.
What I discovered is that if you've EVER had the url to the plist file or the app file incorrect then your iPhone will always fail to install. There's some kind of cacheing going on where the phone fails to download the updated plist file if it's previously downloaded an incorrect one.
The fix I've used is to try a different phone (that hasn't cached a previous version), or to make a new version at a different URL. Sounds crazy, but it worked for me!
We have also faced with this problem couple of times and possible reasons might be;
Due to the screen shots, did you upload your files to exact location "http://www.becomingapps.com/en/ota/" location? When you give this URL during enterprise export.
Second possible reason we have seen is mismatched App Id's.
In case you haven't solved your problem, I think you can't use a wild card in your ad hoc profile. It should have the full ...com.becomingapps.dilemma signature.
You also have to upload both the icons, but I'm assuming you did that since your screenshot shows a custom icon.
It's worth the effort to get this working, my customers love it.
I have a number of apps that are almost identical (with the exception of a few constants, images, and a sqllite database file). I've never had any issues submitting them before, however today one of the updates gave the following error when validating/submitting (note: I have updated this app in the past with no issues):
Application failed codesign verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate.
I've spent all day trying everything to get this to work. I even diff'd the entire project folder against another app (which submitted successfully, today), and all build/signing settings are exactly the same (except bundle identifier, version number, etc.). I've even (as a last resort!) revoked the certificate and re-generated everything, including provisioning profiles.
I've been through all of the steps listed here:
https://developer.apple.com/legacy/library/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933
However, if I "Share" the app from the Organizer and save to disk, running codesign -dvvv says it's not signed at all (however, this happens with the ones that worked!). Not sure how else to run this, as the file generated (and shown in Organizer) is not a .app file.
I'm at a total loss how to figure out what's wrong with this, or why it's any different to the others. I don't seem to be able to get any more information out of the Organizer. The app was built exactly the same way as the others, and the project files etc. are identical (except for expected differences like images/names).
Ok, fixed this... I wish I'd tried this sooner, as it would've saved me many hours today!
It seems that the App Store provisioning file for this app was somehow corrupt - not on my Mac, but on Apples servers.. I downloaded it many times today, with no luck. I just discovered that selecting the Ad-Hoc profile during Validation worked, which led me to believe it was specific to the App Store one. So I deleted the App Store provisioning file from the iOS dev dashboard, then recreated it, downloaded it, and it worked!
Before I deleted it, I edited it, and everything was set correctly, and the expiration date was 6 months from now, so I can only assume something was broken Apple's side (even though I'm sure this same file worked in the past!) :-(
I also have the same problem.
All my provisioning Profiles, Certificates, Bundle Identifier every thing was perfect.
Except My Apps Executable file Name in Info.Plist and Product Name in Target Build Settings was slightly different.
And just because of that codesign_wrapper was not able locate Provisioning.
I spend nearly one day to figure this out.
So Please do one check
App Product Name is have to be same with your Executable file in Info.Plist.
I have a very similar problem, but in my case my distribution profiles keep disappearing from my system. So when an application specific distribution profile disappear Xcode picks up another one (wildcard, iPhone developer, etc.) which is not correct. Everything looks fine except I get this error.
My solution was that I downloaded all of my code signing profiles from Apple. I saved them in a directory and whenever one "disappears" I just have to double click the correct profile to add it to Xcode and update "release" entry in Code Signing Identity in plist.