Security Policy Error after Installing iPhone SDK 3.1 - iphone

I'm working on an iPhone project in which the developer that created it has left the company. The Boss asked me to ensure it compiles on the 3.1 iPhone SDK.
After installing, it built and ran fine just once on the device.
After that, it still builds okay, but if I try to run it on the device, it halts saying
Error from Debugger: Error launching remote program: Security policy Error
It won't play in the simulator either, except this time it just says "Debugging Terminated"
Does anybody have any ideas about what might be causing this?

The problem ended up being that there was a provisioning profile (from a completely different project) that had expired. I don't know why having this unrelated profile expire would cause this problem.
Deleting the expired profile from the iPhone fixed the problem.

I have written down a tutorial to solve this:
http://www.drooljunkie.com/code-uncode/beginning-iphone-app-dev-issues-part-2-running-app-on-the-device-issues/

in my case I removed those with the same name ...

Related

Xcode shows popup but there is no errors

Working with my application It goes well but has met into a problem with Xcode. When I try to run the application on the iPhone simulator this message always pops up:
"A coordinated app install already exists for com.apk.ios with intent IXCoordinatorIntentUpdating (creator InstallCoordination Simple SPI) but request by CoreSimulatorBridge (pid 677) was for intent IXCoordinatorIntentInitiating"
What is wrong? There are no errors when trying to build the app. Has tried to clean the build.
Erasing all content and settings is not always necessary as #user3344236 stated.
Please make sure to delete the app that you are trying to install from the iOS Simulator. That'll probably solve your problem.
Why this occurs?
In my case something went wrong while Xcode is trying to install the app on the simulator. Everything is frozen and I had to restart the Mac manually.
Found a solution that works for me:
Reason:
Either the App store or something else tool is downloading the same app with the same identifier at the time Xcode is trying to launch the same app on the Simulator or on MAC.
Solution:
Need to stop/delete all the running installs of the app with the same identifier. (How to stop -> that can be figured out to see either App Store or any other tool ) Then try again to launch the app with Xcode, this time it succeeds.
No need to Reboot the simulator/ Mac or reinstall Xcode.
Thanks, Hope this will help someone.

Error - The service is invalid. Please check your setup and try again. (0xE8000022)

I keep on getting this error when I try to run the app on my iPhone. I'm running Xcode 7.3 and had started to get this error on Xcode 7.2. I have tried pretty much every solution I could find, but none seem to work. I also tried using the previous versions of Xcode, and didn't seem to resolve the problem either. My iPhone is running iOS 9.1. Is there any work around this?
These are some of the solutions I followed but didn't work:
Error : The service is invalid
how to remove error the service is invalid please check your setup and try
Warning dialog "The Service is Invalid" when building and running App in XCode 4
I had this issue when attempting to register for remote push notifications in my app, in the end it was because I had assigned the iOS Team provisioning profile to the app as opposed to the one I generated in the developer portal. The error occurs because the one that xcode generates doesn't include include permissions for remote notifications.

iPhone app could not be installed at this time [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 months ago.
Improve this question
I was trying to install my iphone application from testflight.
It installs perfectly on few devices but in some after installing about 80 percent it gives an error Unable to download application, <my app> could not be installed at this time
I am able to find out the reason for, why is it so?
Here's a screenshot:
clear your cache and cookies in Safari, make sure your device is in provisioning profile and provisioning profile is installed on the device.
If everything mentioned above didn't help, try to create a new build with higher build number and try to distribute your app again
Most common issues that cause this are (from testflight's website):
Device storage is full
The provisioning profile is a developer provisioning profile
The ad hoc distribution provisioning profile is corrupted and the device is having an issue with it.
The device was restored from a backup and is causing a conflict for over-the-air distribution
There was a network timeout
Architecture settings of the build and the device are incompatible ( can sometimes happen -when "Build Active Architecture Only" is on when building).
Not Using Mobile Safari.
for me it turned out that my client's ipad was running iOS 4.2.2 and my project supports 5.0+.
Recently default Xcode project settings set ONLY_ACTIVE_ARCH (Build Active Architecture Only) to yes for Debug configuration.
So your build can not be installed on different hardware than the one you use for development.
Change this setting and installation should go fine.
As for Xcode 5.1, the problem was in arm64 architecture in VALID_ARCHS. Building the release configuration for 5.0 device locally gives the following error:
Xcode cannot install or launch applications supporting the 64-bit architecture on devices running iOS versions prior to 6.0. This configuration is supported for distribution through the iOS App Store, but cannot be used during development with Xcode. To continue, edit the Run scheme action and select a build configuration that does not include the 64-bit architecture.
Removing arm64 from VALID_ARCHS solves the issue. In my case I had to create a separate branch for testing on iOS 5 devices.
You can try to publish the application by changing the version of the build.
I was also having the same problem and tried the same by just changing tIt may help you too.
For me Setting Build Active Architecture to NO... works and installed successfully
Watch the console through the Xcode Organiser for the device that is failing to install.
You'll get a helpful message from the system telling you what is wrong. There are lots of potential failure reasons, so unless you check the message, you're just guessing...
Here is what worked for me:
Clear the Cache and Cookies (Settings > Safari).
Remove existing profile (if any) linked to "Test Flight App" (Settings > General > Profiles).
Open Safari and go to https://testflightapp.com/. Login and follow the steps to start over.
P.S. I used to have a Test Flight App, but it looks like it crashed and the icon turned to be all white. Restarting my iPhone made it reappear correctly.
I was also having this problem, with an Ad-Hoc iPad application, when trying
to install it on a iOS 6 device.
What fixed it for me was to click on the project in XCode, and change the
"iOS Deployment Target" setting from 5.1 to 6.0.
And there was silly me thinking that iOS 5.1 apps would run on a iOS 6.0 device.
I just saw this as a result of a network error / time-out on a flaky network. I could see the progress bar increasing after I got the bright idea of just retrying. Also saw HTTP Range requests on the download server with ever increasing offsets of a few megabytes (the entire app was about 44MB).
I had this problem but I fixed this by making sure my Code Signing Identity is the SAME as the one I used in test flight.
After that, everything works fine
This can also happen if you disable cellular data for "App Store" (for example, while on vacation) and forget to turn it back on. The solution here is to simply re-enable it in Settings -> Cellular.
in my case app want to use iCloud services, but in distr. provision profile wasn't set iCloud enabled. turn it on and refresh profile.
I have had the same issue after fiddling around with certificates (argh).
The problem became apparent as I followed the comment of #Duraiamuthan.H, I installed on a device. The device reported 0xe8008016 (Entitlements) see SO here
The initial reason was, that the testflight target used the App store distribution certificate, not the Team certificate. I fixed that and the application was installing on the device over Xcode and then it also worked with testflight.
I had similar issue. However, I was able to fix it when I updated my iPad timings to that of current. I just checked the device log and found that the time in the log was shown 2 years before.
Hope updating the device timing to the current time will fix the issue.
Missing icon could be a problem. My manifest file points to a non-existing image and it fails the installation process. Placing an icon at the corresponding path solved the issue for me.
I ended up creating new Provisioning profiles, not sure if it was because of:
"The ad hoc distribution provisioning profile is corrupted and the device is having an issue with it."
I had the same problem as #mohitum007. In my case the developer of this App included an expiry date in it.
As workaround I set the date backwards to a past date (e.g. last month). Then I could install it and use it.
Also when I set the date back to normal, the already installed App didn't start up anymore. I contacted the company of this App to send me an updated version.
Sidenote: I found out that users from other Apps had the same problem but reversed: it won't install or start before a certain date.
For me, just uninstall the Testflight and restart my iphone. After that, install TestFlight, it works fine !
Check if the deployment target in the General section of the project settings, is greater than that of your device's iOS version.
If yes then you need to update the version of your device to at least the deployment target version. in order for you to be able to install the application on your device.

Weird error when trying to run a test on device

For almost a week i'm getting this weird error when i'm trying to run the app on my idevice.
the error is that:
error launching remote program: failed to get the task for process 10492
It's important to say that I get this message on Xcode, the app quites on the idevice, but right after I can run it by clicking on the app icon and it works just fine with the latest updates.
what seems to be the problem?
Thanks alot!
The problem is that you have set the build configuration in Release mode, and installing the application in device through Xcode. If you want to debug the app, then you should go to Edit scheme, and choose Debug mode. Also, make sure, you have a developer profile, and that you are building with that developer profile. Then, when you try to install the app through Xcode, you will see the app getting installed. Hope that helps!
GDB is having trouble attaching to the device process. Have you tried restarting the device?
If this is a permanent issue and you have an Entitlements.plist file have a look at this.
Please check your certificates. If you are signing with distribution certificate then you will not able to debug. To debug you have to have provision certificate
Hope this will help

error from debugger :error launching remote program

I am getting this error while running my app on the device.I have installed the distribution provisioning profile.
error from debugger :error launching remote program: failed to get the task from process 1637
Thanks
I came across this question while searching for an answer myself. I figured my problem was I was trying to launch and debug my app from xCode using the Ad-hoc provision rather than the developer 'Debug' provision. xCode would build and copy the app to the device but wouldn't debug.
I just changed the Active Configuration to Debug and the problem was solved. A silly mistake really.
I have two suggestions:
1) Quit simulator and xcode completely. Then start back up.
2) If you can run other projects OK, but not this particular project, it could be something wrong with your projectname.xcodeproj folder.
I spent hours trying to fix a similar problem. I started picking apart changes from subversion and was "diffing" each and every file to find a "breaking change". Finally, I just deleted the entire folder and then restored it from SCM and everything was fixed.
Quit xcode and restart again works for me...