30

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.

user856232
  • 1,073
  • 2
  • 14
  • 40
  • 1
    possible duplicate of [TestFlight rejecting build "get-task-allow" error](http://stackoverflow.com/questions/10435697/testflight-rejecting-build-get-task-allow-error) – Almo Mar 20 '14 at 14:39
  • 4
    I just encountered this problem. Restarting xcode and archiving the app again fixed it (I suspect this has something to do with the way xcode was generating the the entitlements file, though I'm not sure what). – ahtierney Mar 20 '14 at 22:05

8 Answers8

107

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

Mike
  • 9,765
  • 5
  • 34
  • 59
  • 11
    Wow, this fixed it for me as well. – shim Apr 07 '14 at 19:50
  • 5
    Found this after 1 hour.. victory in comparison. – JeremyDay Apr 29 '14 at 14:36
  • 2
    You have got to be kidding me!! Hours wasted! Thanks for the help. – Kyle Redfearn May 12 '14 at 18:08
  • 2
    Just restarting XCode didn't help, but a full machine restart did the trick for me. – Dane May 16 '14 at 20:55
  • 1
    Shocking. Fixed it for me as well. :-) – ToddB May 22 '14 at 17:07
  • 1
    Thanks a lot. I started to become frustrated. – Timo May 25 '14 at 19:08
  • Fixed for me as well.. Wow Thanks! – mejim707 Jun 01 '14 at 20:34
  • Fixed for me as well.. Where would I go if there were no stackoverflow! – Usman Awan Jun 10 '14 at 18:10
  • For a few days my macbook had been asking to be restarted to complete an update. I kept delaying it but when I faced this issue, simply restarting XCode didn't help. So I restarted the macbook and let the updates get installed (OSX and Safari update). Then fired up XCode, clean-build-archive and uploaded again to TestFlight. No problems this time. What a waste of time :-/ – Kapil Pendse Jun 17 '14 at 03:05
  • This fixed for me as well, any idea the actual cause of the issue? After multiple cleans, builds and tweaking provisioning profile settings I was amazed that restarting xCode ultimately fixed the issue. – negrelja Jun 18 '14 at 19:24
  • Unfortunately, I have absolutely no idea. – Mike Jun 18 '14 at 20:11
  • Fixed for me as well. Pathetic. – Taylor Jun 28 '14 at 02:02
  • Messing around with the Code Signing Identity and then resetting it and the restarting XCode a couple of times fixed this. Apple just didn't get famous for their developer tools I guess... – esbenr Jul 17 '14 at 05:39
9

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.

JosephH
  • 37,173
  • 19
  • 130
  • 154
5

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.

tonisives
  • 1,962
  • 1
  • 18
  • 17
4

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

Leeleo3x
  • 631
  • 1
  • 6
  • 13
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.

user856232
  • 1,073
  • 2
  • 14
  • 40
0

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.

webcpu
  • 3,174
  • 2
  • 24
  • 17
0

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)

Daniele
  • 2,461
  • 21
  • 16
0

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.

user462990
  • 5,472
  • 3
  • 33
  • 35