Error from debugger: Error launching remote program: security policy error

[rofus]

Hi all,

I bought yesterday the license for Iphone Developer, I'm programming
an app and would like to start testing it on my iPhone (EDGE, OS 2.1).
I'm using osx 10.5.5 on a MacBookPro, and latest SDK. Developing
and testing on simulator is ok, I followed all the procedure for requesting
certificates, downloading them, the provisioning file and dragged on
Xcode, I can see the iPhone with my provision name enabled for developing
in the Organizer view, and I followed instructions to configure Xcode to develop
on my device changing relevant options in the targets as explained online.

When I try to develop on device I get all the process, file is transferred
on device, but when launching I receive the error

Error from debugger: Error launching remote program: security policy error

Also when I try to launch the app from the phone it says there was
an error and it's not possible to lauch the app. Is that an error in my
steps configuring Xcode or is it something else?

Thanks,
Giancarlo

[phuongth]

I have the same error?
Did any one know how to solve this problem?
Thanks,
Phuong

[phoo1234567]

Check out post #82 of this thread.

[XCode Template] for SDK and Open Toolchain API in firmware 2.0 - Hackint0sh

[nambrot]

yeah me 2.
i got the iphone security policy error.
Also tried the solution of installing a free App(fring).
It just do not work.
Has anybordy solved the problem yet?

[phuongth]

I don't know all reasons cause this problem.
In my case, I put wrong company's domain name and product's name. Make sure you write exactly company's domain name you registered.

[Tim14ww]

Originally Posted by phuongth

I don't know all reasons cause this problem.
In my case, I put wrong company's domain name and product's name. Make sure you write exactly company's domain name you registered.

I have the same problem, you just need to make a new project, and make your apps again. probleme solved.

Greetz,

Timmeehh

[gechici]

Just look at the following blog post guys:

How to Get Rid of Security Policy Error | « Simple and Pragmatic Thoughts » Isa Goksu

[aryaxt]

I know this thread is old, but i still post my solution.
I got the exact same error and the reason was that the provisioning profile was expired.
Just go to program portal renew the provisioning.
Then go to xcode==> Organizer, remove the current provisioning. download the renewed provisiong and that solved my problem

NOTE: Just replacing the old provisiong with the new one didn't fix the prolem, I had to remove the old one first, then add the new one.

[MatuX]

Originally Posted by aryaxt

I know this thread is old, but i still post my solution.
I got the exact same error and the reason was that the provisioning profile was expired.
Just go to program portal renew the provisioning.
Then go to xcode==> Organizer, remove the current provisioning. download the renewed provisiong and that solved my problem

NOTE: Just replacing the old provisiong with the new one didn't fix the prolem, I had to remove the old one first, then add the new one.

Hey all,

I had this exact problem, some of my provisioning profiles expired, I deleted the ones I had in my iPhone, reuploaded, but I'm still getting this error.

I've tried Clean/Recompile, reuploading the provisioning, etc.

Can anyone help?

Thanks!

[douglaspneill]

Try deleting the profiles manually from your phone (i.e., not via xcode).

[rudifa]

I had the same problem ...
1- I installed a new profile on iPhone 2 days before the expiration of the old one
2- after the old one expired, I got "Error launching remote program: security policy error"
3- on iPhone - Settings - General - Profiles I removed the expired profile
4- this solved the problem

Thanks to all participants above for hints.

[pcgeek]

Originally Posted by rudifa

I had the same problem ...
1- I installed a new profile on iPhone 2 days before the expiration of the old one
2- after the old one expired, I got "Error launching remote program: security policy error"
3- on iPhone - Settings - General - Profiles I removed the expired profile
4- this solved the problem

Thanks to all participants above for hints.

I had to remove both of the profiles I had on the phone to get it to work not just the new one I was using.

[Darkin]

I got a new iphone and xfered all data off my old one. When I went to test an app on the new one, gave me the same error. I deleted all the old profiles of the new device so I only had the new provisioning profile I made for the new iphone and it worked!

[sdowns]

I had the same issue... I solved the problem by removing expired profiles on my iPhone...

Settings -> General -> Profiles -> (look for expired profiles and delete them).

After deleting a profile with the same name (that was expired), I reran my app and bingo!

[nycdude777]

Hey guys, thought I'd give my 2 cents. I had the app running and installing on the phone just fine. I upgraded my phone to OS 3.1 and xcode to 3.1. When I tried building and running for the device, i got the same error.

I removed the provisioning profile using Organizer, downloaded a new one from portal, readded it using the organizer but still the same problem.

I then read someone's suggestion to remove the provisioning profile from the phone itself, Settings > General > Provisioning...

I went back to xcode and decided to hit Build and Run BEFORE adding the provisioning profile to the phone using the Organizer. XCode gave me a message I never seen before, saying that there is no Provisioned Device connected, but there was a button that said Install the Profile and Run... so i hit it. And voila! It ran.

I went back to phone settings and the profile was there ))

I guess XCode 3.1 is now smart enough to install the provisioning profile for you.

Good luck

[bb0868]

Originally Posted by sdowns

I had the same issue... I solved the problem by removing expired profiles on my iPhone...

Settings -> General -> Profiles -> (look for expired profiles and delete them).

After deleting a profile with the same name (that was expired), I reran my app and bingo!

I did this and it worked... Thanks

[vibhorgoyal]

I have written down the steps I followed to solve this issue:

Error from Debugger: Error launching remote program: security policy error | droolJunkie

[cdasher]

Originally Posted by vibhorgoyal

I have written down the steps I followed to solve this issue:

Error from Debugger: Error launching remote program: security policy error | droolJunkie

I just got the same error and fixed it. For a couple of days, I have been getting the message on the phone that one of my profiles was expiring. It was an app that I no longer am working on, so I disregarded the messages thinking "so what if that one expires". Well, it appears that if you have any profile on the phone that is expired, it will give you this error even though you are trying to install a new or different app with a perfectly valid (and different) provisioning profile. So I removed ALL of the expired profiles and now it works as expected.

[vibhorgoyal]

yea you need to remove all the expired profiles to make it work, strange but true.

[QuantumDoja]

Originally Posted by nycdude777

Hey guys, thought I'd give my 2 cents. I had the app running and installing on the phone just fine. I upgraded my phone to OS 3.1 and xcode to 3.1. When I tried building and running for the device, i got the same error.

I removed the provisioning profile using Organizer, downloaded a new one from portal, readded it using the organizer but still the same problem.

I then read someone's suggestion to remove the provisioning profile from the phone itself, Settings > General > Provisioning...

I went back to xcode and decided to hit Build and Run BEFORE adding the provisioning profile to the phone using the Organizer. XCode gave me a message I never seen before, saying that there is no Provisioned Device connected, but there was a button that said Install the Profile and Run... so i hit it. And voila! It ran.

I went back to phone settings and the profile was there ))

I guess XCode 3.1 is now smart enough to install the provisioning profile for you.

Good luck

Thanks! That worked great!