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.
Related
I have been testing my iOS app on my physical iPhone XS for quite some time now and all of a sudden it threw an error when I tried to run it saying:
"APP NAME" is no longer available.
So I went to re-build via Xcode into my device again to reinstall it. But I was getting an error message saying "Untrusted Developer".
So I tried to go to the Settings > General > VPN and Device Management screen to see if I need to 'Trust' my own developer profile again. But it's not appearing on that screen or any other new developer profile for that matter.
Did a bit of research and tried to troubleshoot. One of the solutions I've found and worked was to actually create a new developer account and use that to build and install the app on my device. I does work but I don't want to use another developer account to to build this app as the bundle identifier that I wanted to use was already tied up to that old account. And I have a bunch of other apps tied up to that old account as well.
The other reason why the above solution also wouldn't be ideal as I already have months worth of data in my device that was saved in that app. If created a new build using a new account it wouldn't be able to access the data of the old app built using the other account.
Just to note, that old account was formerly a paid account but now it expired. But I didn't have that problem until recently. So I am guessing it has something to do with the recent iOS 15 beta builds.
I will be filing a bug report for this. But does anyone have any idea or workaround to get rid of this issue? Any information that could potentially point me towards the right direction would be appreciated. Thanks!
I've filed this as a bug on AppleFeedback Assitant. They've reached out to me to ask for logs and the certificate I used to re-build the project. I'm guessing this this a bug and they are trying to fix it.
The provisioning profile generated prior iOS 15 is preventing installation on the new release. Therefore, you will need to generate a new provisioning profile for your app. Try the following:
Quit Xcode
Go to the directory of cached provisioning profiles (cd
~/Library/MobileDevice/Provisioning Profiles/)
Back up the existing
files to another directory
Remove all profiles listed under
~/Library/MobileDevice/Provisioning Profiles/
Launch Xcode
Install/run the app on your device
Xcode will detect that there are no eligible profiles on your local system and request a new one during the next build to a device. The new profile will be compliance with iOS 15 provisioning.
NOTE: if it still doesn't work, then install the iOS 15.2 beta release (Build 19C5026i or later) on your device and try the steps above again.
I managed to fix this issue.
Xcode -> Preferences -> Accounts -> Manage Certificates -> + -> Apple Development and then make a new certificate
My situation might be different from yours but here were the symptoms I was seeing. I was able to sign random Github projects and run them on my phone. I also have a paid developer account. I never saw anything related to my app in the VPN & Device Management settings on my iPhone and I still don't.
I think I found solution for this problem.
You need to remove old certificate from your keychain, after then create new in Preferences... -> Accounts -> Manage Certificates... -> Tap +
I hope I will help someone.
iOS 15 + macOS Monterey + Xcode 13 Seems to have fixed the issue
After updating to macOS Monterey, my app launches as normal. I will add that I did all the things that other people which might've changed the outcome. This included changing my bundle identifier and deleting my certificate from the key chain and creating a new one. I'm also running Xcode 13.1, iOS 15.1, and macOS 12.0.1.
I had the same error on my iphone 12 promax, You just need to create a new bundle identifier then build and then change back to the old bundle identifier. It works for me
I'm running Xcode 10 and iOS 12.1 on my iPhone 6S Plus. The app works when running in simulator, but when running my app in Xcode with my phone connected, i get this error:
iPhone has denied the launch request.
My iPhone is a trusted device on my mac, and i have my signing certificate. I've spent hours googling for a solution but none of them are working for me.
Anyone have any ideas?
I was also facing similar issue.
What work for me is to change the trust to "Use System Defaults" (Previously it was always ask) in "Apple worldwide developer relation certificate authority" in keychain.
My solution worked: Menu Xcode - Product - Scheme - Edit scheme - Build Configuration -> [Release] (instead of Debug) + Debug executable -> [remove the cross]
I have faced the same issue when I run the build-in ad hoc profile and I have fixed it by unchecking the " Debug executable " option from the Product -> Scheme -> Edit Scheme.
Try upgrading from XCode 10 to XCode 10.1. The SDKs for iOS 12.1 were added in XCode 10.1, so XCode might be having trouble communicating with your device because it's on a higher OS version than it understands.
Select the Project> Target > Build Settings. Search PROVISIONING_PROFILE and remove whatever is there. Then run.
Check you certificate in keychain if its double delete one of them > Quit XCODE > Clean > Build again ( This work to me )
edit scheme > uncheck debug executable.....this works but make you lose debug capabilities.
what is really worked for me without losing the debug capabilities is doing the following
open keychain
search for iphone developer certificate
delete it (Xcode will create another one for you)
relaunch the app Xcode will ask for your computer password type it and you are done
i found this answer thanks to Tommy Callaway on youtube
video link
The solution for me was to delete ALL my apple dev certs locally, then approve them during the next build process.
But def make sure you've set the provisioning profile for your project, that's a classic..
Keychain Access
On my device, I went to Settings -> General -> Profiles & Device Management. I then tapped on the 'developer app entry' which displayed my personal development team. On the next screen I chose to trust apps from this developer (me).
In project , open your project's TARGETS.
1.Check your Provisioning Profile whether is match Signing certificate
2.In debug their are develope profile and certificate,and in release their are distribution profile and certificate
3.[enter link description here][1]if you don't determine, there is a easy way to help you,xcode offer the Automatically manage signing ,just in xocode tick this option.look this here
This will help: iPhone has denied the launch request
I'm trying to solve an issue with Xcode 8.3.3 that prevents me to test my Apps on my devices.
At the moment I'm using a free provisioning account for my tests.
I've worked many months without any problem, then I've upgraded to Sierra and Xcode 8.3.3.
Unfortunately I don't know exactly after what action/update the problem started, because I have not used Xcode for several months.
The issue: when I try to build my app to run on my iPhone, I get these errors in project page, under General > Signing view:
Automatic signing failed
Xcode failed to provision this target. Please file a bug report at http://bugreport.apple.com/ and include the Update Signing report from the Report navigator.
Signing certificate is invalid.
Signing certificate "iPhone Developer: edoxxx#me.com (xxxxxxx)", serial number "xxxxxxx", is not valid for code signing. It may have been revoked or expired.
The issue happens either on my main Mac account and also if I create a fresh new user account,
it happens also if I use another AppleID account for code signing.
but it doesn't happens if I boot the same machine into another macOS installation (using the same AppleID and same device). In this last case I'm able to build and run the app without any issue on my device.
Because of that behaviour, I think that is something related to some software crap in the first OS installation, and not related to my user's "data" nor my AppleID account.
I've tried everything I've found on internet to clean-up the Xcode installation, including total removal/reinstall plus Keychain cleanup. But nothing solved the problem.
I've found some related informations in this topic:
https://forums.developer.apple.com/thread/83611â
but no real solution.
Hope that someone could help me :)
Bye,
Edoardo
Here's what worked for me:
Open "Keychain Access"
Find the private key called "iOS Developer"
Delete the private key
Try code signing again, it should work!
I had the same thing happen to me. I discovered my problem was that in my build settings I had set my Code Signing Identity
Debug to iOS Developer
and my
Release to iOS Distribution
Because they were different. One wasn't able to find a signing certificate. The signing certificate I had downloaded was and iOS Developer certificate so when I switched my Code Signing Identity for Release back to iOS Developer everything was fixed.
After further investigation, I've found the problem.
Looking at differences in keychain between my productive machine and the fresh OS installation, I've dicrovered that the "Apple Worldwide Developer Relations" CA was missing in my productive machine (no idea why...).
I've erased all my developer certificates, downloaded new certificates from https://www.apple.com/certificateauthority/.
After the code signing fix in Xcode, I was back able to build and run my app on my device.
Strange that Xcode does not handle this kind of errors correctly, but report a "generic" error about code signing.
Although I added the new, valid certificate to the keychain, it was not working. The solution for me was:
1. Restarting Mac OS (because deleting certificate was not working)
2. Deleting all invalid certificates
You don't have to do something further. The valid certificate is being automatically used for your deployment(/development) provisioning profile.
I've run in release mode my app on a iPhone with Xcode 4.
Everything worked great until when I switch to the simulator and I switched back to the iPhone. After switching back, the app is launched on the iPhone, but the home screen is displayed immediately after and in Xcode I get:
failed to get the task for process
I've tried to remove/add Entitlements file, delete app and restart Xcode but nothing to do.
I am betting that your release mode includes compiling with your distribution certificate, which disallows this behavior (you wouldn't want some random fool hooking into your app after downloading it from the app store). Compile with the development certificate instead. You can change this in the building settings under code signing.
Change the profile for code signing. Select your project, go to Build Settings > Code Signing Identity. Switch to other developer profile.
I had this error while running from Xcode
Edit Scheme
Choose Run
Uncheck âDebug executableâ
Clean Derived Data: â Cmd + â Shift + K
Run the app again: â Cmd + R
If anyone is having this issue but is sure they have their certificates and code signing correctly set up, check the capabilities tab when you click on the project (i.e. next to build settings tab, build phases tab, etc).
In my case there were broken links for Game Center and In-App Purchases that needed fixing (by clicking the "fix me" buttons) to solve this issue.
I had a the same issue and after reading the above answers all I had to do was go to Build Settings > Code Signing > Provisioning Profile > None and was able to ran the app on my devices again. Hope this helps someone else out
To anyone who comes across this:
After reading this, I attempted to solve the problem by setting the Debug signing to my Development certificate only to find that deployment was still failing.
Turns out my target was Release and therefore still signing with the distribution certificate - either go back to Debug target or change the release signing to Development temporarily.
If you've set the correct code signing certificate under Build Settings->Code Signing, then make sure you are also using the correct provisioning profile for Debug/Release mode as well.
I was having this issue because I was using an Ad-Hoc provisioning profile for both Debug/Release modes, which doesn't allow for a development profile to be used when doing a debug build.
I switched back to "Automatic" on the build settings provisioning profile for "Debug" and left the release certificate profile unchanged, mine worked. Tried the other answers. nothing worked. Didn't want to have to reconfigure my certificates. Automatic on the provisioning profile did the trick
Just get the same problem by installing my app on iPhone 5S with Distribution Profile
-> my solution was to activate Capabilities wich are set in Distribution Profile(in my case "Keychain Sharing","In-App Purchase" and "Game Center")
Hope this helps someone...
Just had the same problem - app was being installed OK, but won't run from Xcode with the "process launch failed: failed to get the task for process".
Turns out my development certificate expired during the night. Regenerating the certificate and the provisioning profiles solved the problem.
Having the developer code signing id is correct for sure, but also make sure you device is added to the Member Center via organizer, or through the developer portal.
A few days ago I reset my device list, and today I was suddenly getting this for an iPod I debug with all the time. About 15 mins later I realized the problem.
I had this problem after I created a new developer certificate.
The following was already correct:
The old private key was deleted from the keychain, all profiles where up to date, the build configuration and signing settings were correct. Yet I had this problem.
Solution:
I had to restart Xcode (5.1.1), because it was not aware of my new developer certificate. I also deleted the obsolete profiles from my devices just to be sure and to clean up.
I had this issue when trying to debug an App on a device I hadn't used before. Developer profile was correctly set. The device was part of our teams account but wasn't included in my profile.
Simply had to open Organizer -> Select the Device -> Add to Member Center
I had this same problem, however in a little bit different situation. One day my application launches fine (using developer provision), then I do some minor editing to my Entitlements file, and after that it stops working. The application installed fine on my device, however every time I tried to launch it, it exited instantly (after the opening animation). (As I made edits to other files too, I did not suspect the following problem)
The problem was in the Entitlements file format, seems so that the following declarations are not the same:
Correct:
<key>get-task-allow</key>
<true/>
Incorrect:
<key>get-task-allow</key>
<true />
Altough it's an XML format, do not use spaces in the tag or the Xcode will not be able to connect to the process.
I was using developer provisioning profile all along.
Edit: Also make sure the line ending in your Entitlements file are \n (LF) instead of \r\n (CRLF). If you edit the entitlements file on Windows using CRLF line endings may cause your application to fail to launch.
I have the following error when I try to run a new project on my ipod:
Error launching remote program: failed to get the task for process 312.
The program being debugged is not being run.
I've read about Entitlements.plist, and I've tried to add the get-task-allow, but then it doesn't let me compile because of a code signing error. I only have a development provisioning profile, so it's not the same as the people who were trying to debug the distribution build (I'm also in the debug build, so that isn't a problem).
Old projects build and run fine on the ipod, just new projects.
I've tried restarting both xcode and my ipod, but it doesn't help.
I have no more ideas on how to build/run new projects on xcode, so any help is much appreciated!
Oh, and I'm using an iPod 3G with iOS 4.0.1. Xcode is 3.2.3 (64-bit).
It turns out that using a different provisioning profile (one with a wildcard rather than one without) solved this issue.
The key point is to use a Developer profile rather than a Distribution profile.
Check that you're doing signing using a development provisioning profile, not a distribution one.
This error happens when you have set Distribution Provisioning profile in code signing. Change it to Developer Provisioning Profile, then it will work. Worked for me for Xcode SDK 4.5.
There is also a case that your error would happen.
If an app with same Bundle Identifier is launched at background ( probably an App Store version ), Xcode debugger will not know which App it should attach to. To solve it, remove/uninstall the App Store version, and click Run in Xcode again.
The same story can apply if you once build the app with a bundle id then you changed the project bundle id and still kept both app versions. make sure you remove the old one.
If your certificates are not quite right or have become not quite right, this problem can start to happen and you can go round and round playing with provision and entitlement files to no effect. (In nearly all cases, you don't need an entitlement file.)
I'm talking here about debugging on a tethered device in "debug" mode, not any sort of "release" mode.
Here's how I finally determined this was the problem and fixed it:
1) Try to create the simplest Xcode project possible and in Target...General set it up for your "Team". (If you find this impossible to do, that already is a sign of this sort of problem.)
2) Tether your device and try to run on it. Normally, this would go smoothly, but if the opening screen appears on your device for a second or two and then the app crashes and Xcode says it can not attach to some positive task id, then you may have the sort of problem I had.
3) So I then went to another Mac with Xcode and did the same thing, letting Xcode 5 automatically get the needed credentials. (I'm using a "wild card" * app id for all of this.) In my case, much to my surprise the simple app I created on the new Mac ran on the tethered device just fine keeping up its opening screen indefinitely. What a relief. So I then went to keychain access on the new machine, exported all of the relevant keys into one file and then exported the relevant certificated to a .p12 file. I also made a copy of the new working project to take back to the first Mac.
4) Back at the first Mac using the app for the second Mac, it had trouble with the Team ID when I looked at the Target...General screen. Your symptoms might be different, but the point is I couldn't rebuild the app from the second Mac on the first Mac.
5) So I then opened up Keychain Access (possibly not necessary) and double-clicked on the files I brought over, first the one with the keys and then the one with the certificate, providing the p12 password when requested. (Some of this may not actually be necessary, but I'm not sure which and I am describing what worked for me.)
6) I did step 4 again and this time it worked fine! I then found that the other programs that were giving me the "failed to get task" problem now worked fine, too. I just wish I could get back all the time I lost before I tried the process described here.
Conclusion, something was wrong or had become wrong with the certificates or the keys on the first Mac. It was subtle enough that I could still do builds, make ad hoc releases, etc. but I could not run on a tethered device. Though I don't think it is a factor, I was using a corporate developer account and this Mac was set up to do development for several other developer accounts (and these did not display the problem).
After Xcode 5.0 tried and failed (it hung) to update certificates, ... which it suggested me to do. All I did then:
Restart Xcode 5.0
Open Window > Organizer
Select Devices at the top
Select my device (which had a green bullet)
Click the (+) Add to Member Center at the bottom and follow the few simple steps
Go to the Apple Developer Center and make sure that your developer certificate has not expired. Mine had expired so I renewed it and then went back into Xcode (5.1.1) and under accounts preferences I viewed the details of my apple account and hit the little refresh button at the bottom. My iOS development signing identity showed up and I was back in business.
Removing distribution profiles from device in Organizer solved this issue for me
1.Run the Application using development certificates in both debug and release area in code signing identity.
or
2.Use the development certificate in debug area and distribution certificate in release area.