Reputation: 359

iOS 12 iPad Denied Launch Request - Xcode

I've been updating an application for more than 5 years without problems, until yesterday.

I updated my iPad to iOS 12, but, each time I try to run it, I got the message:

iPad has denied the launch request

I tested in other physical devices with iOS 11 and simulators, and this error happens only with the devices with iOS 12.

What I tried to solve this?

Re-generate my certificates in the Apple Developer page.
Editing my scheme to 'Debug Configuration' to 'Release' and checking and unchecking 'Debug executable'.
Restart my Mac and restart the iPad
Enabling and disabling 'Wait for executable to be launched'

And also, each solution of this thread: Xcode 9 error: "iPhone has denied the launch request"

And after try each one of those alternatives, the problem persist only with the devices WITH iOS 12.

Someone has an idea about how can solve this?

UPDATE I debugged my app, and this is whole the log:

predeterminado  10:33:00.516648 -0600   trustd  cert[0]: MissingIntermediate =(leaf)[force]> 0
predeterminado  10:33:00.516722 -0600   trustd  cert[0]: NonEmptySubject =(path)[]> 0
predeterminado  10:33:00.521320 -0600   SpringBoard [com.mycompany.myapp] Generating image data for snapshot: <XBApplicationSnapshot: 0x1115c11f0; identifier: 5E831360-7FEE-4255-A6FB-08712EF1D226; launchInterfaceIdentifier: __from_UILaunchStoryboardName__; contentType: GeneratedDefault> {
    creationDate = 20 de septiembre de 2018, 10:33:00 a. m. GMT-6;
    keepsImageAccessUntilExpiration = NO;
    hasGenerationContext = NO;
    context = {
        contentType = GeneratedDefault;
        fullScreen = YES;
        referenceSize = {1024, 1366};
        interfaceOrientation = LandscapeLeft;
        additionalContext = {
            statusBarSettings = <XBStatusBarSettings: 0x282f43d00; hidden: NO; style: 0x0; backgroundActivityEnabled: NO>;
        }
    }
    imageContext = {
        scale = 2.0;
        opaque = YES;
        fileRelativeLocation = none;
    }
}
predeterminado  10:33:00.585893 -0600   SpringBoard com.mycompany.myapp:10:11:3:1:Application replaced
predeterminado  10:33:00.592674 -0600   SpringBoard [com.mycompany.myapp] Application installed using default data provider
predeterminado  10:33:00.638304 -0600   dasd    com.apple.CFNetwork-cc-87-19005-Task <6A4245D9-BABF-4974-899B-B744DCB219AE>.<com.apple.cloudkit.cloudd>.<route=usmia-edge.icloud-content.com:outOfProcess=T:allowExpensive=T:powerNap=F:adaptive=T:app=com.apple.mobileslideshow:2app=com.apple.mobileslideshow.PhotosMessagesApp:disc=T:retry=F:pool=com.apple.cloudkit.BackgroundConnectionPool:uuid:C3F50637-0E71-4FCD-A8B5-DB01E2F3D518>.<1>:9D4C2B:[
    {name: ApplicationPolicy, policyWeight: 5.000, response: {Decision: Can Proceed, Score: 0.31}}
    {name: DeviceActivityPolicy, policyWeight: 10.000, response: {Decision: Can Proceed, Score: 0.60}}
 ] sumScores:58.471249, denominator:65.910000, FinalDecision: Can Proceed FinalScore: 0.887138}
predeterminado  10:33:00.662238 -0600   SpringBoard [com.mycompany.myapp] Snapshot data for <XBApplicationSnapshot: 0x1115c11f0; …08712EF1D226> written to file: /private/var/mobile/Containers/Data/Application/1DB50DD3-CF52-4498-854F-C0939D28ECC0/Library/Caches/Snapshots/com.mycompany.myapp/[email protected]
predeterminado  10:33:00.666489 -0600   trustd  cert[0]: MissingIntermediate =(leaf)[force]> 0
predeterminado  10:33:00.687764 -0600   TVRemoteConnectionService   XPC: Recieved an application registered LaunchEvent
predeterminado  10:33:00.909692 -0600   trustd  cert[0]: MissingIntermediate =(leaf)[force]> 0
predeterminado  10:33:00.910738 -0600   trustd  cert[0]: SubjectCommonName =(leaf)[]> 0
predeterminado  10:33:00.910872 -0600   trustd  cert[0]: LeafMarkerOid =(leaf)[]> 0
predeterminado  10:33:00.912183 -0600   trustd  cert[0]: MissingIntermediate =(leaf)[force]> 0
predeterminado  10:33:00.912253 -0600   trustd  cert[0]: AnchorApple =(path)[]> 0
predeterminado  10:33:00.912321 -0600   trustd  cert[0]: ChainLength =(path)[]> 0
predeterminado  10:33:00.912399 -0600   trustd  cert[0]: IssuerCommonName =(path)[]> 0
predeterminado  10:33:00.943350 -0600   trustd  cert[0]: MissingIntermediate =(leaf)[force]> 0
predeterminado  10:33:00.943416 -0600   trustd  cert[0]: NonEmptySubject =(path)[]> 0
predeterminado  10:33:00.972795 -0600   trustd  cert[1]: AnchorTrusted =(leaf)[force]> 0

Upvotes: 34

Answers (23)

Xiuhong Zou

Reputation: 1

I try all the solutions above, but none of them works for me.

My problem is that the develop certificate in keychain is untrusted. my problem

I finally figure out a solution for myself.

close the Xcode.
Delete all developer certificates in the keychain.
key step: go to https://www.apple.com/certificateauthority/, download and install the worldwide developer relations certificate for both versions (one expires in 2023, another in 2030) page
restart the XCode, it works.

Upvotes: 0

Robin Dinse

Reputation: 1539

In my case the developer account was not yet approved of on the iOS device. I had to do this manually in the Settings app:

Open the Settings app
Go to General
Go to Profiles & Device Management
Choose the profile in question and trust it

Upvotes: 16

Rakshitha Muranga Rodrigo

Reputation: 1079

Mine was a similar incident - iOS 13 (iPadOS) / Xcode 11

provisioning profile didn't contained current device that I have tried to run the project.

You can generate new provisioning profile with the device UDID
Switch to auto signing

Upvotes: 0

Sami Boudoukha

Reputation: 599

I solved this by checking Automatically manage Signing under Signing Capabilities on my .workspace project under Xcode 11.0.

It is a Cordova Project.

Just saying in case it help someone.

Upvotes: 2

Kiran kumar

Reputation: 1

I have faced the same issue.

Make sure the testing device udid is added in the developer account and if you are facing the same issue again then, Try restarting the testing device.

I solved like this.

Upvotes: -1

Rutvi

Reputation: 11

I fixed this issue by deleting the certificates in keychain and restating the Xcode again. below are the steps :

1) In keychain : System--> all items--> delete - Apple Worldwide Developer Relations Certification Authority.

2) Restart Xcode again.

this worked for me.

Upvotes: 1

JDL

Reputation: 1517

I ran into this issue today and none of the above solutions really worked. After paying attention to what it appears that iOS 12 and XCode are both wanting, it appears, that when running and debugging on the device from XCode, iOS wants a developer provisioning profile instead of a release distribution profile. Attempting to run on the device, from XCode, while debugging with a non developer provisioning profile causes problems of one form or another.

In that regard, if you are using manual profiles, for whatever reason you need two. One development profile and one distribution profile and use the development profile when debugging on a device.

Upvotes: 1

George Vardikos

Reputation: 2437

Something that worked for me was to:

check the "Automatically manage signing"

That way I could make it work

That tells me tha maybe the error is somewhere in the provisioning profile.

Upvotes: 0

gamal

Reputation: 1665

For Xcode 10.v

1 -> Delete all developer certificates in keychain.

2 -> Remove AppleID from Xcode.

3 -> Restart Xcode.

4 -> Add a AppleID again to xcode (same as previous is fine).

5 -> Restart Xcode again, (Better if ReStart your MAC).

Upvotes: 8

Lorenzo Santini

Reputation: 667

Here’s a solution that doesn’t involve editing the scheme and therefore makes possible to use the breakpoints as usual.

Looking in the Keychain access, searching for the keyword "developer" I found out that my iPhone certificate was flagged as "invalid" in red. So here's what I've done:

I opened Keychain access and searched for the keyword "developer".
I deleted the "iPhone Developer" certificate (if you have a problem with another device make sure to delete the right one).
Then I deleted the "Apple Worldwide Developer Relations Certification Authority" and the "Developer ID Certification Authority" too.

After that everything worked as usual and I have been able to launch the app on my iPhone.

There’s also a video on YouTube showing this method.

Upvotes: 2

Binshad

Reputation: 455

This issue can be resolved by unchecking Debug executable in Edit Scheme.

Upvotes: 6

Shane McCurdy

Reputation: 2218

I wanted to expound on the answer a little, to offer a little more detail based on what I have gone through and learned fighting this issue, and for those who, like myself, are new to Xcode and iOS development. And as in my case, I just needed to get it running as fast as possible.

My scenario was I have an Ionic 3 iOS app running on some iPads for a local non-profit as welcome desk checkin kiosk, so this app doesn't need to be public on the store. The app was crashing after a few days, and then I found out after weeks of research that it was my Apple developer account, not a bug or memory leak.

So I re-setup my Apple developer account, created new and updated signing certificates and Ad-hoc provisioning profiles with these iPads on them so they wouldn't crash any longer. I started to run the app on the devices with my shiny new certificates and profiles... and then chased this "iPad has denied the launch request" mess for a couple hours.

Here's what I learned:

Try to edit your Run Scheme first.

If the app already exists on the target device, then just set the Executable setting to "Ask on Launch", by going to Product → Scheme → Edit Scheme...

Make sure Run on the left is selected, and then open the options for Executable on the right, under the Info tab. Select "Ask on Launch", then Close.

When you try to Run the app again, a pop-up with the available apps on the target device will appear, and you will need to select your "appName.app", then click Run.

Don't see your "appName.app"?, then this is a fresh install, click Cancel.

If this is a fresh install, you will have to make sure Executable is set to your "appName.app". It will deny your first Run attempt, but it will have installed the app on the device. Then go back and reset Executable to "Ask on Launch" and then Run again. The "appName.app" should be in the list now.

If editing your Run Scheme doesn't get it up and running...

I'd advise next looking at your Apple developer certificates and make sure they are in line and up to date.

Take a quick peak by clicking on the info circle (i) icon next to your signing profiles.

Manage your certificates here... https://developer.apple.com/account/ios/certificate

You can also have Xcode download your certificates, or just look at them listed out by going to Xcode → Preferences:

Then make sure you are on the Accounts tab, select your Apple ID on the left side, and then look on the bottom right for the ability to Download or Manage/View your certificates...

If you had any changes/updates to your certificates, try Running your app again, and then try editing your Run Scheme again, before going to the hassle of creating a new user account.

If all else fails...

You might then try creating a new user account on your computer, and going through the process of setting that new account up with all the same certificates. But this is more than I want to detail here. I would also advise this as a last resort.

Xcode 10: iPhone has denied the launch request

Good luck!

Upvotes: 15

IceMan

Reputation: 71

Editing the Product → Scheme → Edit Scheme → Info → *Executable** to change to Ask on Launch worked. However, when resetting the scheme to its original setting, the application did not launch.

Searching for a more permanent solution, I removed the developer certificate as described above (solution 2: open Keychain Access → choose System, All Items → delete certificate Apple Worldwide Developer Relations Certification Authority**), but when I relaunched Xcode my application would not launch on the device with exactly the same behavior.

The following approach appears to have resolved the issue:

Removing the Apple ID from Xcode Preferences;
Relaunch Xcode to add Apple ID;
Add a new iOS Development Certificate in Xcode Preferences → Accounts → Apple IDs using the Manage Certificates button;
Quit Xcode;
Relaunch Xcode and the application.

Upvotes: 2

HHD

Reputation: 49

There's a simple solution.

Change your Bundle Identifier or DisplayName or change them both. When it's working, change it back to what it used to be.

It works for me.

Upvotes: 0

JESERRANO

Reputation: 359

After days of research and thanks for the help @Little Green Viper, I found a solution.

Basically, some Apple Worldwide Developer Relations Certification Authority weren't working after the update, but it was able to compile successful for the iOS 11. Then, the most risky solution is deleting all the Apple Worldwide Developer Certificates, BUT before doing that, try creating a new user on your Mac.

(System Preferences → Users and groups → New User) that should work.

Now you have to options, work in the new user or re-sign the certificates. In my personal case, I picked up the first option.

Upvotes: 0

Linh Vo

Reputation: 270

It took me three days to solve problem. I found two solutions. You can choose either of the two ways.

Solution 1:

Open System Preferences → Users & Groups → Add a user account (build with new user is successfully).

Solution 2: open Keychain Access -> choose System, All Items -> delete certificate Apple Worldwide Developer Relations Certification Authority.

Upvotes: 23

LaoTzu78

Reputation: 1

I also suffered the same issues with iOS 12 and Xcode 10 yesterday. I solved it by setting "Always Embed Swift Standard Libraries" to Yes.

In Xcode, choose Target → Build Settings → Always Embed Swift Standard Libraries, and set the value to Yes.

Upvotes: -2

Benjamin RD

Reputation: 12044

The problem should be related with your certificates. Try to resign your certificates and install them on your Mac.

Also, to have a better view of your problem, connect your iPad with iOS 12 and try re-running the application. If the problem persist, you can check the logs to see more details.

On your Xcode, go to Window → Devices → Select your device → View Device Logs.

Upvotes: -1

SwatGuard

Reputation: 55

I got stuck in this issue for a couple of days. I tried everything I read here but with no success. I remembered that I logged in on another two Macs with my AppleID to download some apps. I logged out of those Macs, signed in with another AppleID and downloaded something on them (I did this because I bought and downloaded a Mac App on those Macs).

It fixed my issue. Hope it helps.

Upvotes: -1