Using Xcode beta 9 (v4), I'm trying to launch the app by clicking on the "play" button. I get a "build succeeded" but right before launching, a popup message appears in Xcode:
"iPhone has denied the launch request."
It used to work yesterday. It does work on the simulator. I've rebooted my computer, the iPhone, uninstall the app, cleaned the build. Running out of ideas.
It may be code sign issue. Make sure you're signing with developer, not distribution.
It happens using Xcode 9.x or newer.
I tracked this problem down to the "debug executable" checkbox in the product scheme (product->scheme->edit scheme->info->debug executable checkbox). I unchecked that and this stopped happening (as well as a couple other weird issues - no output in console being one).
I have a workaround:
If you change the scheme to 'Ask on Launch' it works.
In Xcode top bar
Product > Scheme > Edit Scheme > 'Info' tab > Executable: "Ask on Launch"
http://upload-images.jianshu.io/upload_images/663014-d5d182e310052664.png?imageMogr2/auto-orient/strip%7CimageView2/2/w/1240
It's slightly annoying but it works.
This issue can be resolved by unchecking Debug Executable in Edit Scheme.
After getting "denied launch request" error, do this:
Edit Scheme -> Info -> Executable -> Ask on Launch
This worked for me with adhoc profile.
The problem for me was that I was using a free developer account (simply signed in with my Apple ID). When looking at the device logs I found (bold added)
(RequestDenied); reason: "The request was denied by service delegate
(SBMainWorkspace) for reason: Security ("Unable to launch
{com.my.bundleID} because it has an invalid code signature, inadequate
entitlements or its profile has not been explicitly trusted by the
user")"
That made me realize that I needed to go into Settings -> General -> Device Management -> {My Apple ID} -> Trust
After that, everything worked as expected.
In previous versions of iOS I would encounter a dialog on my device that would tell me that this was the problem. Maybe Apple took it out for iOS 11. 🤔
Simple restarting of the iPhone helped me out.
For me issue was due to code signing the app with Ad hoc profile.
After changing the code signing to developer profile,from xcode settings general tab the above issue got resolved.
I got this issue recently and I found the solution for this crazy issue. This are the Scheme Issue to fix this issue follow following steps.
Click Edit Scheme top Navigator Tab.
Click Info on Run menu.
On Executable dropdown select "Ask on Launch" option -> Then Close and run the build once.
This solved my problem when I got this issue.
Apple Reference
Got this with Xcode 9.0 while deploying to a non-simulated iPhone 6s with iOS 10.3.
I had force-quit the app right before this arose. Otherwise, nothing had changed; all the developer signing credentials was still trusted, and the app was still marked Verified in the iPhone's Settings.
The trick that fixed it was turning the iPhone off and then turning it back on again.
Looking at my logs, it appears applicationWillTerminate was triggered a while before this happened; the instance of the app that I thought I force-quit must have been some zombie process?
The problem is that xcode 'times out' after certain seconds. The fix is to edit the scheme and ask xcode to 'wait' until the executable is launched.
In Edit Scheme, check 'Wait for executable to be launched' instead of 'Automatically'
I attentively read all answers but they don't help me. My solution:
Go to Xcode preferences, select accounts (⌘ + ,)
Select your Apple ID, choose team and click Manage Certificates
In Pop up menu in bottom left corner click + button and select iOS Development, then click done and close popup
Try to relaunch application, now it's should fine.
It may cause with switched a wrong branch with Git, Make sure the branch you switch not too old(since it may cause code sign issue), And on the right branch if this still bothering, select the development Provisioning Profile under Signing(Debug) if u r not Automatically manage siging.
Just tick "Automatically manage signing" in General -> Signing properties of the Target. It will create Development provisioning profile for you and running on the device will work.
These simple steps helped me.
Remove your connected iPhone, iPad from the mac.
Restart your device.
Select "Automatically manage signing" in Xcode settings.
Reconnect your iPhone, iPad.
I know there are lots of answers in this thread. I've tried every one of them but none worked for me.
TLDR:
Here is the solution:
Update to xcode 11.4.1 or newer
Going through all the certificates in Keychain access I found out that all of my developer certificates has a invalid status. And, I believe that, this is the root cause of this issue. I've tried the solution here saying delete Apple Worldwide Developer Relations Intermediate Certificate and everything. But, It didn't work.
Then I came across this link. Apparently, the Apple Worldwide Developer Relations Intermediate certificate (AWDRI) is set to expire in 2023 and developer certificates or any other certificates issued after January 28, 2021 won't be using that particular AWDRI certificate. Instead of that they use a renewed certificate which is set to expire in 2030. And here comes the problem, The new renewed certificate only works in xcode versions of 11.4.1 or newer. And, I have an older version of xcode.
When I updated my xcode to latest version - 12.4 (I had to go through making space on my machine, updating macos and all) The problem went away. All my developer certificates on Keychain access are now showing valid. And, I could see two AWDRI certificates on my Keychain access one expiring on 2023 and another one in 2030.
Description from the link I shared:
The current Apple Worldwide Developer Relations Certification Intermediate Certificate (intermediate certificate) is set to expire on February 7, 2023. The renewed certificate will be used to sign new software signing certificates issued after January 28, 2021 for the Apple Developer Programs. Remaining service certificates will be updated in the future and this page will be updated to reflect additional certificate changes.
And more...
This requirement also impacts all software signing certificates generated after January 28, 2021, by developers with Personal accounts in Xcode, as well as members of the Apple Developer Program, Apple Developer Enterprise Program, and iOS University Developer Program.
The new Apple Worldwide Developer Relations Intermediate Certificate is downloaded automatically by Xcode 11.4.1 or later and is available for download on the Certificate Authority page. Confirm that the correct intermediate certificate is installed by verifying that the expiration date is set to 2030.
Also they are mentioning about an issue with older versions:
Xcode 11.4.0 and earlier may not be able to sign software using signing certificates issued by the new Apple Worldwide Developer Relations Certification Intermediate Certificate. If you’re unable to upgrade to a supporting version of macOS or Xcode on your build machine, you can build and archive your app using an earlier Xcode client and sign it for distribution using the latest release. Alternatively, you can utilize the codesign tool to sign your software using the command line.
I face this issue on Xcode 9.1
Scenario: I checked "Connect via Network" option for device. And trying to run app to this device with USB cable attached.
Fix: Simply remove USB cable and run.
I'have tried all the answers nothing worked for me,
The problem is coming form Xcode itself and has nothing to do with profiles and certificate :
Product > Scheme > Edit Scheme
In Run (Section) / info (tab) [select] the Release instead of debug as Build Configuration as follow :
It's a regression since Xcode 10.1
Config : Xcode Version 10.1 (10B61)
Iphone X / IOS 12.1.4
I had the same issue . Its a bug in Xcode 9.1. There is a trick to make it work for now. Lock your phone. Run the code. Xcode will ask to unlock the iPhone.
I just cleared the profiles with the Apple Configurator, restarted the iDevice and worked again as usual.
It's an intermittent bug in Xcode - I just stopped and started all my devices and it magically worked (after messing about for 1/2 hour)
I had upgraded MacOS overnight to 10.13.04 which obviously upset something!
Xcode 9.3, iOS 11.3 watchOS 4.3
Let me tell you a workaround which solves my problem:
Step 1: Windows > Devices and simulator.
Step 2: Unpair device.
Step 3: Reconnect device and trust.
Step 4: Run the application. BINGO.
For me this issue was related to a Manually installed Enterprise Certificate and having to use it for both development and release schemes. I had to trust the certificate on the device before it would allow the app to be launched, but it would never launch as I kept getting that denied message. Eventually, editing the scheme and setting it to wait for the app to be attached before debugging did the trick.
Open the App Groups in Capabilities, wait App... effective，then close the App Groups, it worked:
After seeing all the solutions given across web, i finally found one and here are those:
Error occurs because of it makes Runner confused about what profile to use.
You will most often get this error, when you have added new account in profile in Xcode > Targets > Signing.
You can remove this error by just using before one Profile.
There is no need to create New Users.
or you can sign in with account you are using in Profile in your iPhone (i did this!)
Happy Days :)
In case this problem occurred for you a couple of days before today, 2019-Mar-20, it is very likely related to the fact that faulty code signing certificates were issued. In that case you should be able to resolve it by just recreating the code signing certificate. This SO question already has an answer that explains you how to do so.
I'm not sure whether it's a fix, or just another workaround, but uninstalling the application from my device helped. I'm still not sure what caused it, but #MrRogers answer helped me figure it out.
For me the issue came-up because, I was using the Distribution Provisioning Profile to debug.
We cannot debug with Distribution Provisioning Profile, changing it to Development Provisioning Profile fixed the issue.
Steps: (Xcode 11.2.1)
Select Project, Under TARGETS, select the correct target.
Switch to Signing & Capabilities
Under Singing section, change the Provisioning Profile to Development profile or you can just check Automatically manage signing
None of the other answered worked -
Xcode 11+
Click Edit Scheme on the top Navigator Tab.
Launch option choose Wait for executable to be launched
You will have to run the application on your device manually but that will keep the debugger attached as for some of the other solutions debugger get detached.
Today,I also meet this question.This is my way to solve.
Xcode 9.0,iPhone 6s,Automatically manage signing with my account.
When I select "iPhone 6s",I found that there is an logo after the iPhone 6s
It's the new function of Xcode 9.0 that can run an app on the iPhone without a string connect computer(iPhone and Mac must connect the same Network).
So, I try to change this kind of connect way.
Open "Devices and Simulators"-> unselect "Connect via network"
And then, I clean, rebuild and run my project.It works!
I will be happy if this method can help you.
I am trying to publish an app for testing, without having to connect a device in my mac.
I have created a developer account, created an app in itunes, generated bundle id, signed into xcode with the developer account, generated a distributor certificate.
When I tried to archive the app, I got the error "conflict provisioning setting. app is automatically signed for development ..."
I read in this post and followed the tip of unchecking and rechecking the option "Automatically manage signing". After re-choosing my team, I get the error "There are no devices registered in your account on the developer website. Plug in and select a device to have Xcode register it".
The goal all along was that I wouldn't need an ios device, because I intended to immediately publish the application and invite people to test it via testflight. Is it not possible to do it like this? Am I missing something.
I have read lots of documentation, but being a first timer in this, everything seems confusing.
Edit: I created a provisioning profile as distributor. Even after creating and installing the distributor profile (it now appears also in xcode at Account -> provisioning profiles), I still get that same error. I also noticed that in signing, The signing certificate is iOS Developer. I am sure
I fixed it by plugging in my iPhone and going to the Product menu > Destination > iPhone (my device).
Then after clicking Try Again on this properties page the warnings went away.
Source
The solution (though I would welcome more elaborate, insightful explanations):
#General -> Signing, disable the option "Automatically manage signing"
#General -> Signing and certificates choose your team
Though in my case that was not the issue, I would recommend making sure that in the device list, you choose Generic iOS device in your target devices.
This really sucked to figure out.
What you do is add a distribution profile in https://developer.apple.com/account/resources/profiles/add. Don't choose development! Don't let the Xcode Automatically manage signing!!
Then, you download the provision.
Then, in the Signing & Capabilities -> Signing Section of the project.xcodeproj file, turn off Automatcially manage signing, choose import and import the file you just downloaded.
Then, in the top, you choose Any iOS Device (arm64, armv7) and then you go Product -> Archive.
What happened to me was that I was about to run my app on a physical device for the first time and I didn't have a Team. So I created it in the process before connecting my phone with the USB cable. After I created the team a message like the listed above appeared. I did some research on internet but nothing found.
So here's what I did: I connected my phone, did all the trusted process, then restarted Xcode, and it worked. I am not sure what happened, but it was some of my first experiences using Xcode. It could sounds silly but it helped me. Hope to you too.
If you do not wish to register a device follow this advice:
https://stackoverflow.com/a/44157307/499581
* In short use "Generic" as the device while archiving.
If you do wish to register a device then the solution to:
"There are no devices registered in your account on the developer
website. Plug in and select a device to have Xcode register it".
Is to physically plug-in your device (an actual iPhone, or iPad) so that Xcode can register it for development use (note: this will not affect the normal everyday use of the device). After the device is registered it can then be used for development testing, load provisioning profiles onto it, etc.
↳ Disabling and Enabling Devices Using Your Developer Account
For those who are trying to develop without a mac computer using MacInCloud don't follow the standard advice out there. Its will lead you down a hole. I have wasted hours of my time.
The reason it say something about "a device to be registered to create provisioning profile" is that you need to provision an iOS device that you can test on before you can get it signed. If you are using MacInCloud you probably can't physically connect an iPhone or iPad to the MacInCloud and therefore it can't automatically provision devices for you.
Before you get to far into this you will need to get your iPhone/iPad UDID. Which I was able to do with https://get.udid.io/ on my iPhone, but it didn't work on my iPad. Instead, with the iPad I had to download iTunes from the Windows store and connect my iPad. Then click on the little gray square in the menu that's inline with Library tab.
image of itunes
Then when it pops up with your device info (mine didn't come up with my info at first, I had to sync my device). You will see your SN. Click on your SN and it will change to your UDID. Once you have your UDID you are ready to create a provisioning profile. What is confusing is this isn't done in the appstoreconnect section of your account online. Its done in your developer account: https://developer.apple.com/account
developer.apple.com account screen shot
When you go there you will want to click: Certificates, Ids & Profiles
Here you will need to add your devices and then with auto signing checked in Xcode that made the problem go away. NOTE: I originally tried to create a profile, download it, and import into Xcode under the Provisioning Profile dropdown in Signing & Capabilities. As described in another answer here, but that proved more problematic and wasn't necessary.
Then you can chose Any iOS Device from emulator device drop down then go to Product > Archive > Distribute App and create a certificate to place it on the app store (TestFlight).
you can also plug an iphone, run the app the app on your iphone as the target, it will ask you to register the device and then the certificates will be generated
Have you paid the $99/year developer fee? TestFlight is only available for paid developers. I would highly recommend plugging in an iOS device, though. It's more fun and rewarding testing that way.
I have an app build with Meteor like this meteor build <path> --server <address:port>. What is the next step to add it to my iPhone for testing?
When I open the myApp.xproject file it saying in Identity section no matching provisioning profiles found I did try 'Fix issue' btn, which guided me to make an account etc. But this did not fix it. Is it possible because I haven't paid yet for for my account? I just would like to see how it would work on my iPhone for now.
Yes, you need a developer account to run on an actual device. Pay for the account and you will get development profiles and distribution profiles so you can run on your phone and submit to The App Store. Good luck!
There's a weird way that used to work. It's like a debugging mode but the most recommended way is to do it getting the developer account as Douglas said.
These are the steps:
Go to Xcode > Preferences and where says Accounts add your apple id. It will ask you for a team name, type your name for example.
Now go back to Xcode and click on the blue file at the top of the navigator with your project name. Then General.
The system will ask you about fixing an issue, do it and after a while it will finish.
Then choose a version available on your device and your iPhone in the device selection.
It worked with some of my classmates, I can't verify it 100% because I have the developer account. Hope it helps.
I was trying to activate a developer app in iOS 9.2 and the app was not trusted due to security settings. I tried to go into the Profile area under General Settings, but it wasn't there. What gives? It was there this morning . . .
Apple renamed the Profile section to Device Management. It is still under General Settings and performs the same function.
This somewhat worked for me: Instead of looking in the device, go to XCode, Devices (Under Window), ctrl -click on the device and you should see a "Show Provisioning Profiles" menu item.
I had the same problem and I couldn't debug my apps anymore.
I used the Apple Configurator (https://itunes.apple.com/de/app/apple-configurator-2/id1037126344?mt=12) to delete all of my profiles on the iPhone. Afterwards I installed another signed app again and now I can debug again.
But I still can't see "Device Management" in Settings.
I was successful doing this when I accidentally went to Product>Profile once the build is finished head over to your phone then Settings>General> then the Device Management will instantly appear under VPN.
I am at iOS 12.1.2(16C101) and was trying to verify that the Developer App certificate for my account is trusted on my device. Found the option at
General -> Profiles & Device Management.
If "Device Management" doesn't appear you must restart your device to see it.
This worked on ios 9.
I know that it has been asked a thousands of times, but I am struggling 4 hours with every possible sollution I read but still I cannot beta test my app in my device.
Here are the facts:
1) My app is uploaded in the IOS store, so I have created a provisioning profile, app id's and so on. I just now want to test it in my iPhone4, with target iOS 6.0.
2) I added my device UDID in the devices, in my developer account.
3)I set the code signing for debug to my provisioning profile.
4) I plugged in my ios device in the mac and I see that picture.
As you can see there is no provisioning profile.
5)If I run the app to my ios device (which is listed in the Xcode) I get the error
No provisioned iOS devices are available with a compatible iOS version.
I tried so many solutions that I found that I cannot even remember all of them. I am following all the steps one by one.
-someone said to log out from developer account
-other said to change deployment target
-other said to change the "edit scheme" to debug.
Can anyone help me? I do not understand what is missing since app is published and I only want to test it in my device. Should I change anything else?
EDIT: I selected the device as Ganee said. Then in my organiser I see the following picture:
If I press refresh, I see "Too few items in team".
So If I remove the provisioning profile, how do I download the new one? I suppose I enter my developer account and press download in the distribution profile under the provisioning tag, right? But is this updated with the selected device?
Here is my picture from the developer account:
I think you followed all steps, but still you have to conform the following steps.
After you added device to developer account, you have to select that device in your provisioning profile.
Remove old profile from your organiser, download new modified profile and install it on your Mac.
Please check wether you modified developer/ distribution profile and select it on your xcode.
Hope this will give some clarity.
I remember having similar problem in the past. I am not sure if yours is similar. But awhile back when I upgraded my iOS device, it was no longer compatible with the xcode version I was running. I had to upgrade to the latest version of xcode. What is Xcode version are you running?
Finally the problem was that I had a distribution profile set up, and not a developer. Thanks for the help!