This week, after getting my new MBP, I was trying to deploy my new iPhone application to my testing device (iPhone 3G). After going through all code signing/provisioning issues I managed to deploy my app. However, when GDM tries to run it, I was getting an exception that says “Error from Debugger: Error launching remote program: Security policy Error“.
And it was unable to run my sweet app in my device. Everything was working perfectly in Simulator, but not in device. After a little googling, I found the solution. Before going into the tip, I want to let you all know guys, this problem only occurs if your iPhone is jailbroken.
Okayyy, here is the tip: Please just add following lines into your Info.plist file and save the world :)
<string>Apple iPhone OS Application Signing</string>
I hope it saves your day too :) Good luck!
Edit: As Mike Rentas / @Overloaded mentioned below, if you’re having this problem with the normal iPhone devices (non-jailbroken), then first try removing the old provisions from the device.
Amazing. Thank you, all the message board posts seemed like complete voodoo. This worked without a hitch.
April 16, 2009, 9:30 AMYou are AWESOME!!!!! Thank you!!!!!!!!!!!
However, our own crack detection code works against us! Why do we need to add the line???
April 17, 2009, 11:44 AMI’ve never tried with non-jailbroken iPhone before. My guess is MobileInstallation puts these lines on the fly for normal iPhones while installing the app to the device. As you may know, to jailbreak iPhone, you need to change the MobileInstallation.
April 17, 2009, 12:52 PMWoW. That was amazing and solved the issue right away. I only would like to note that I had to remove my previous installation using Organizer and then it worked.
April 21, 2009, 10:21 AMTHANK YOU!!!
May 9, 2009, 12:17 AMThank you! This provisions stuff is a minefield.
May 17, 2009, 7:49 AMThanx a lot! You’re the best!
May 18, 2009, 4:49 AMThank you a lot ! it’s a really awesome tip !!!
June 2, 2009, 1:26 AMThank you! Removing Entitlements.plist from debug build solve this issue to.
June 23, 2009, 11:07 PMNice!!! You save my day!
July 9, 2009, 9:07 PMWeird, I just got this problem on a non-jailbroken 3G. Tracked it down to an expired provisioning profile (not the one I was signing the build with). I deleted that from the phone and it worked.
July 24, 2009, 12:51 PMYeah, I’m getting it on a 3.0 device never jailbroken. What I had to do was delete every profile from the phone itself (Settings > General > Profiles) that had expired or was about to expire. Perhaps it’s a 3.0 bug that’s confusing any expiring profile with the one the app was signed with…
July 26, 2009, 8:23 PMAs Jazon, I too had the issue when another profile has expired. I deleted only the exipred profiles (which non were the profiles I signed the app i was trying to open) and it worked. Mostly likely a bug in 3.0.
August 23, 2009, 7:09 AMSame thing with expired profiles for me too.
September 11, 2009, 5:04 AMDear RolYroLLs! Thank you very much! The deleting of exipered profiles gets rid of any errors with launching new apps fro testing in device.
September 17, 2009, 4:14 PMThis did not work for me, but I did have luck using the iPhone Configuration Utility to remove the old profile.
September 19, 2009, 11:50 PMThanks a lot. It did save my day.
October 12, 2009, 9:32 PMThis problem seems to occur for a variety of reasons and not just for jail broken phones as mine is completely legit.
My problem was happening because I had another development profile o my phone and it had expired. I removed it and my new app works just fine.
October 20, 2009, 3:55 AMMy iPhone is NOT Jailbroken. And I had this problem, and deleting the old profiles worked.
October 25, 2009, 11:13 PMWith firmware 3.0.1 I was required to remove expired provisioning profiles of other apps. Seems a bug of this fw version, I don’t know if fixed in 3.1 or 3.2
November 1, 2009, 2:23 PMExpired profile for me as well. Again, not the profile I was signing against. Thanks Overloaded, I was tearing my hair out with that one.
November 2, 2009, 8:08 AMI have a jailbroken iPhone 3g(firmware 2.2), I am trying to debugged my application by bypassing the security policy, I did it from this link http://www.alexwhittemore.com/?p=10 , and I even install the mobileinstallation patch from http://iphone.org.hk, but when I Build and Go, the icon comes up on the device but it gives the error like this at my XCode “Error launching remote program: security policy error.”. did anyone have done for the jailbroken device. Please help
December 4, 2009, 2:48 AMhey im unable to test my app on the simulator when i choose the iPhone Device 3.0 option in the xcode build nad run. i get the error as “code signing error: no provisioning profile found matching for Iphone Developer”. i was following the http://www.alexwhittemore.com/?p=10 approach.. can neone help.. working on iPhone Os 3.0, sdk 3.0 thnx
December 7, 2009, 3:44 PMhi ritika, you must have not create the self sign certificate at the keychain. You can used the guid from the following link http://developer.apple.com/mac/library/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html
December 9, 2009, 12:48 AMYour solution does not work. you need to delete all the expired provision profiles from the device. Then download the provision profile from you iphone development account and install. It will work.
December 11, 2009, 2:58 AM@johnson, I’ve never tried after 3.0, but this way was working on #jailbroken phones.
@manoj, I already mentioned in the article (10x Mike Rentas / @Overloaded for that), you have to try deleting old provisions first :)
December 11, 2009, 8:36 PMwell, this solution did not work for me. actually, this error can be caused by a no. of ways. with me, it occured because i installed 2 versions of same profile on my ipod (i modified my profile slightly and re-downloaded it from the developer portal and installed both of them on my device … silly of me)
December 14, 2009, 8:24 PMwell, this solution did not work for me. actually, this error can be caused by a no. of ways. with me, it occured because i installed 2 versions of same profile on my ipod (i modified my profile slightly and re-downloaded it from the developer portal and installed both of them on my device … so silly of me). i just removed one of it and the error was gone hope this helps someone who did the same.
December 14, 2009, 8:25 PM@johnson, thanks for the link but i hav already done tht..I have obtained the signing identity following the 9 steps given but I havent gone beyond it..like i havent done “Adding an Info.plist to Single-File Tools” and “signing your code”. do i have to do those too?? thanks
December 16, 2009, 5:23 AMsweeeeeeeet, fixed it
January 7, 2010, 4:25 PM