Comments on: What’s a Security Policy Error?

By: S Woodside

S Woodside — Thu, 27 May 2010 06:21:18 +0000

Awesome. Even simpler solution — just delete ALL the provision profiles on your device. Then let XCode prompt you to re-install them.

By: Stephen

Stephen — Mon, 17 May 2010 18:54:11 +0000

Thanks. I was heavily into paragraph two of your post until I found this.

By: Manoj

Manoj — Fri, 11 Dec 2009 10:55:25 +0000

Thank you, your solution is the coolest solution for Remote debugging.

By: Mark Knopper

Mark Knopper — Thu, 10 Dec 2009 19:43:21 +0000

Just adding my thanks – this solved my problem.

By: kode80

kode80 — Fri, 06 Nov 2009 14:09:46 +0000

Awesome this has to be my quickest provisioning fix yet! It may be worth noting that in my case the offending profile did *not* show up in the Xcode organizer – I checked in “Profiles” on the device however and sure enough there it was.
Thanks!

By: Brian F

Brian F — Mon, 02 Nov 2009 01:36:08 +0000

Awesome, thank you much!

By: steven

steven — Fri, 23 Oct 2009 07:24:36 +0000

you are genius godsend thank you!

By: Lakshmikanth Reddy

Lakshmikanth Reddy — Sat, 03 Oct 2009 06:41:12 +0000

Hey, thanks a lot, this is really magic.

By: FyKnight

FyKnight — Mon, 07 Sep 2009 00:54:12 +0000

Thank you for this! If only I’d searched before wasting half an hour on the same problem. I’d sent a build to a tester and they were able to install it but not run it (got an alert) due to having previous expired provisioning profiles on their phone! For a different app!

So it seems all the development apps refuse to run if there are _any_ expired provisioning profiles on the phone, even if they have different App IDs, etc.

By: Orin

Orin — Fri, 04 Sep 2009 08:05:02 +0000

Thanks a ton! I would never have thought of doing that, but it worked like a charm.