IOS provisioning get-task-allow AND <Error>: Profile invalid: 0xe8008012

I have an iPhone app that I created for the app store. Before I get there, I need to check it internally. So this week I went out, got a distribution profile and installed it on about 50 devices in my organization. It's okay, everything went very smoothly and everyone was happy. So I cleaned up the code a bit, did some refactoring, and added a bit of polishing. At the same time, we had more devices added to the beta version (about 10 additional units). Therefore, when I was ready to build and launch the second beta version, I went out, got a new training profile and archived the build for ad-hoc on air. Then I tested the application on my phone (which is also a development device) and it failed to install. I checked the device console in Organizer and saw an error that looks like this: <Error>: entitlement 'get-task-allow' has value not permitted by a provisioning profile . Do not pay attention to the fact that when I archived and deployed it just 3 days ago, it worked perfectly without the Rights Plate. So I thought, โ€œOkay, just one of these quirks.โ€ I added Entitlements.plist and set get-task-allow to YES . Then I re-archived it with the distribution distribution profile and tried to install it on my device, and it installed it correctly. Then I tried it on two separate devices, which he installed when I successfully deployed it on Tuesday, and the other did not. None of them worked. He did what comes to an end, and then says, "Failed to install." So I thought: โ€œWell, he doesnโ€™t like the Entitlements.plist file. I have read some things that say Apple will reject the application for the app store if it has Entitlements.plist in the assembly (is that true? I would like to introduce the end next week, if I can get this stupid beta again!) I delete the file, archive and deploy it again, and I got the same Error. I connected one of the devices to the Organizer console and I got an error message, which looks like this:

 Jun 29 08:49:13 unknown installd[14394] <Error>: profile not valid: 0xe8008012 Jun 29 08:49:13 unknown installd[14394] <Error>: 00381000 install_embedded_profile: Could not install embedded profile: -402620398 Jun 29 08:49:13 unknown installd[14394] <Error>: 00381000 verify_signer_identity: Could not copy validate signature: -402620395 Jun 29 08:49:13 unknown installd[14394] <Error>: 00381000 preflight_application_install: Could not verify executable at /var/tmp/install_staging.PHE3Kj/foo_extracted/Payload/Lenexa.app Jun 29 08:49:13 unknown installd[14394] <Error>: 00381000 install_application: Could not preflight application install Jun 29 08:49:13 unknown installd[14394] <Error>: 00381000 handle_install: API failed Jun 29 08:49:13 unknown installd[14394] <Error>: 00381000 send_message: failed to send mach message of 71 bytes: 10000003 Jun 29 08:49:13 unknown installd[14394] <Error>: 00381000 send_error: Could not send error response to client 

So, I looked at the error 0xe8008012 , and I note that people say that you must make sure that the provisioning profile is configured correctly in Xcode and make sure that the UDID in the provisioning profile matches the devices that you are trying to install it.

With this in mind, I tested to make sure that this is not a UDID problem, creating against the same initialization file that I successfully deployed from Tuesday. Still no.

I changed the entire code signing section in the build settings to look like this: enter image description here

I read that some people rebuilt the project in Xcode. I would like to avoid this. Does anyone have any ideas? I would appreciate anyone!

+4
source share
1 answer

I get it. Someone gave me a bad UDID. To be frank, Xcode could better deal with these issues. It doesnโ€™t take half a day to figure it out!

+8
source

All Articles