TestFlight iOS App get-task-allow Issue

Question

I have an app in testflight for ios called MapItTrackIt. Everything has been working great.

I just updated to xcode 5.1. I built the app exactly the same way I always have. Same profile and ad-hoc cert.

This time when I try to upload my IPA file I get the 'Invalid Profile: developer build entitlements must have get-task-allow set to true.' error.

I didn't change anything at all with provisioning or what not. I just added some more functionality to the app and rev'ed the version.

What the heck do I do now? How do I fix this? My boss wants this deployed right now and I can't.

Answer 1

It looks like there are several different issues that can cause this. Mine was similar to JosephH's, but not the same.

For me there was another provisioning profile that was valid, but from a different user. I have several apple accounts that I am a member of for development.

My build was using a different profile from another user account when it went to sign. This was even though I had told it which one to use in the settings.

I solved this by having to delete that other provisioning profile whenever I wanted to build this app for testflight. The provisioning profile would always come back if I did an update from the dev site for that other user account.

The final solution was that I happened to get a new mac for development and didn't install that other user account's profiles into this mac yet. Now everything builds fine without doing anything.

Answer 2

Same exact issue for about 4 hours today - restarting Xcode seems to be the fix as depressing as that is.

Answer 3

I had this and solved it.

Xcode was using a different provisioning profile from the one I had expected it to - it was signing the build with a distribution certificate, but had created a development provisioning profile.

It turned out that the distribution certificate was somehow invalid. I discovered this by setting the provisioning profile explicitly in the project, which then prompted xcode to give me an error to tell me there were problems.

A good place to start solving these issues is to look in the build log, at the codesign step - there will be a line line:

Using code signing identity "iPhone Distribution: XXXXXX" and provisioning profile "YYYYYY" (<..guid...>)

Check this line says the certificate and profile you expect, and that the signing identity and profile are both distribution ones.

Answer 4

For me the problem was that I had a custom .framework bundled with the app that was not code signed. Apparently this unsigned framework caused the problem.

When I code signed the framework with a distribution certificate the app uploaded without problems.

Answer 5

I fixed this bug by changing my Code Signing Identity - Release part to Distribution certificate

Answer 6

I tried many different ways. None of them works for me.

I thought maybe it's a problem of testflight.

So I used crashlytics to distribute my adhoc build. I had no problems to upload it.

Then I tried to use Organizer to validate this archive to get more information, I got an error. I was told this archive contains unsupported i386 and x86_64 architectures.It turned out that I used a framework which contains i386 and x86_64 architectures. Then I recreated a new framework which contains device only architectures. It works like a charm.

Answer 7

Same exact issue here with the new Xcode 6.3 beta, solved by deleting the Project.entitlements (along with the Code Signing Entitlements entry on the Build Settings of the target)

Answer 8

Solved. I was trying to update a label in the launch screen to show app name, version and build through a custom ViewController. This proved impossible to too complex so I deleted the View Controller. BUT I left the outlets in the Launch Screen Storyboard. I deleted these (Last icon in Utilities tab, a right arrow in circle) and all is love, peace and joy.