Xcode 11.2 - Unable to install App file to device?


Ios Problem Overview

I recently updated my OS to Catalina, and updated Xcode to 11.2. Since doing so, when I try to run a release version of my app on my device, I'm simply given the error:

> Unable to install the app.

When I tap 'details', it provides me with the following:

> App installation failed Domain: com.apple.dtdevicekit Code: -402620395 > Failure Reason: A valid provisioning profile for this executable was > not found. > > User Info: { > DVTRadarComponentKey = 487927; > "com.apple.dtdevicekit.stacktrace" = ( 0 DTDeviceKitBase 0x000000011baff6e7 DTDKCreateNSError + 109 1 DTDeviceKitBase
> 0x000000011baffde9 DTDK_AMDErrorToNSError + 792 2 DTDeviceKitBase
> 0x000000011bb3f56a __90-[DTDKMobileDeviceToken > installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke > + 164 3 DVTFoundation 0x000000010356f156 DVTInvokeWithStrongOwnership + 73 4 DTDeviceKitBase
> 0x000000011bb3f301 -[DTDKMobileDeviceToken > installApplicationBundleAtPath:withOptions:andError:withCallback:] + > 1589 5 IDEiOSSupportCore 0x000000011b9c7a25 > __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.352 > + 4523 6 DVTFoundation 0x00000001036a03ba DVT_CALLING_CLIENT_BLOCK + 7 7 DVTFoundation 0x00000001036a1a92 __DVTDispatchAsync_block_invoke + 809 8
> libdispatch.dylib 0x00007fff68220583 > _dispatch_call_block_and_release + 12 9 libdispatch.dylib 0x00007fff6822150e _dispatch_client_callout + 8 10 libdispatch.dylib > 0x00007fff68226ace _dispatch_lane_serial_drain + 597 11 > libdispatch.dylib 0x00007fff68227452 > _dispatch_lane_invoke + 363 12 libdispatch.dylib 0x00007fff68230a9e _dispatch_workloop_worker_thread + 598 13 > libsystem_pthread.dylib 0x00007fff6847a71b > _pthread_wqthread + 290 14 libsystem_pthread.dylib 0x00007fff6847a57b start_wqthread + 15 ); }

My provisioning profiles are 100% correct, as are my certificates. I have no idea why this is happening, and I've tried absolutely everything to get it to install/run. I've tried:

  • Double checked that 'Scheme' has release checked under the 'Run' tab
  • Confirmed that correct provisioning profile is selected
  • Removing the app from my device
  • Creating new provisioning profiles
  • Changing my bundle ID
  • Creating new certificates
  • Cleaning the build folder, restarting Xcode
  • Reinstalling Xcode
  • Deleting the Derived Data folder

NONE of the above has worked. I've been at this for 2 days now - help is appreciated. The only way I'm able to install the app file successfully to my device is if I upload it to TestFlight first (which, I can't feasibly do every time I want to test a small change).

Ios Solutions

Solution 1 - Ios

Go to File -> Workspace Settings, and make sure your build system is set to Legacy Build System.

I ran into the same issue on Catalina and Xcode 11.2 and this solved it for me.

As of Xcode 11 Apple is starting to enforce some of the build criteria that was previously only required for AppStore builds on .ipa extraction, and device builds.

So far I have encountered:

  • Requiring the above legacy build system setting for device deployments for older projects or projects that use older frameworks
  • Removing unused architectures to extract an ipa from an archive

Solution 2 - Ios

For me, it's due to Dynamic Frameworks which I have added in the application. Initially, I have selected (Embed + Don't Sign) option for the dynamic frameworks.

Changing it to (Embed & Sign) for such frameworks resolved the issue for me.

enter image description here

Solution 3 - Ios

Here is what works for me:

  1. Remove the app and profile from device
  2. Reinstall them again.

Solution 4 - Ios

Use Automatically manage signing

Solve this issue.

checked auto signing

Solution 5 - Ios

I manage to fix this issue when first I clean:

cmd + k
shift + cmd + k

and then I delete all the content of Deriving Data the path of the folder should be like this


Or you can check it in

Xcode -> Preferences -> Locations

Solution 6 - Ios

"-402620395 Failure Reason: A valid provisioning profile for this executable was not found."

I had this issue as well and solved it:

This means that your provisioning profile is not set to development. You need to create a new provisioning profile for development, which is different than a profile set for distribution. Then, in signing and capabilities, in your app settings on xcode, choose your development profile if you want to install on your device. Don't worry about distributing with your dev profile, you must choose which profile you want to use when pushing to app store (its set to none and you need to switch it).

Another solution would be choosing automatically manage signing in settings, but that has defaults set when pushing to app store which you might not want.

Solution 7 - Ios

Try to clean Provisioning Profiles[About]

Xcode -> Window -> Devices and Simulators 
-> Right click on your device -> Show Provisioning Profiles...
-> Select Provisioning Profile -> - Remove selected profiles

https://i.stack.imgur.com/jcRRS.jpg" height="250">

Solution 8 - Ios

Delete derivedData folder

rm -rf ~/Library/Developer/Xcode/DerivedData

Solution 9 - Ios

This issue is only related to CODE SIGNING

But, the key point to note here is, if you are using XCode 11.x version. Not only the code signing in your project, but we should check the code signing in Thirdparty SDKs or dependencies that we add to our project.

Steps to verify the Code Signing of 3rd party SDks:

  1. Download the source code of framework you need
  2. Open the .xcproj file from the source code using XCode 11.x
  3. Go to Targets -> Signing & Capabilities -> Select all tab -> Bundle Identifier If you see any unevenness in the identifier like, identifier with 4 seperators (Eg: com.company.mac.app)

Change it to com.* and enter.

  1. Make sure your XCODE COMMAND LINE TOOLS is set with XCode 11.x

  2. Now, use below command to rebuild the SDK, with the changes done in above step-3

       carthage build --no-skip-current --cache-builds --platform iOS
  3. Now copy the framework generated from, carthage folder of source code, and replace the existing SDK in your project.

Repeat the same for process for all the 3rd party SDKs, in your project.

NOTE: Make sure you marked all the 3rd party SDKs as Embed & Sign in

Targets => General => Frameworks, Libraries, and Embedded Content

Solution 10 - Ios

For me, it was that the watch i was trying to use didn't unlock so i had to lock and unlock my watch again and then it was working fine.

Solution 11 - Ios

This is very strange but for me pod deintegrate and then pod install works.

Try out this solution if none of the above works for you

Solution 12 - Ios

I had the same problem until I found this solution. I had to clear out all of my old certificates and provisioning profiles and then create new certificates with "Apple Development" and "Apple Distribution," instead of the "iOS..." option.

Solution 13 - Ios

This could be due to running distribution/release scheme. Changing the scheme to debug works for me. Hope this helps someone.

enter image description here

enter image description here

Solution 14 - Ios

In my case the problem was occurred by empty framework references in pbxproj. After removing them the problem was fixed.

enter image description here

Solution 15 - Ios

This is a codesign problem.

You can check iOS device logs to see which framework go wrong. filter 'installd' process. you can clearly say which framework codesign is wrong. so just find it out and fix it!

0x16fa53000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 77: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.dABVKh/extracted/Your.app/Frameworks/xxx.framework : 0xe8008001 (An unknown error has occurred.)
0x16fa53000 -[MIInstaller performInstallationWithError:]: Verification stage failed

Solution 16 - Ios

I have the same issue and the problem was that I were using unpaid account and the total number of free development profiles was reached ,so you have to use paid account

detailes :

Failure Reason: The maximum number of apps for free development profiles has been reached

Solution 17 - Ios

I got this error when running a project that had a library under Embed Frameworks which had Code Sign on Copy unchecked. Check-marking this resolved this issue for me.

Solution 18 - Ios

Struggled with this for a long time. What fixed it for me was deleting all the cache data generated by Xcode like Device Support, Archives, Derived data, etc...

Solution 19 - Ios

I got this issue resolved after a whole day of mental agony.

For WebDriverAgentRunner package, WebDriverAgentRunner --> Build Settings --> Product Bundle Identifier --> Provide a custom bundle identifier name

N.B: Copy the bundle identifier name you just provided.

Move to WebDriverAgentRunner --> Info --> Bundle Identifier --> Provide here the bundle identifier name you just copied

Follow the same step for the APP package you are trying to push.

Clean build folder and start building and APP should get pushed without an issue. Tested on Xcode 11.7

Solution 20 - Ios

In Xcode 12, I got an error window saying: Unable to install "AppName".
I clicked Details and found that There was no space on my iPhone.

Solution 21 - Ios

In My case just remove the existing build in my phone then run again its working perfectly.

Solution 22 - Ios

I have received this error message after I updated my MacOS (specific to Big Sur) and Xcode (to version 12.5). For me what have solved the problem is just deleting the app from the device and re-install

Solution 23 - Ios

Yes, Faced this issue several times for several xcode and cocoapods versions. This issues happen when each pod frameworks can't find specific info.plist file in project. Of course I don't know why after pod install, each pod frameworks can't find info.plist. In my case I've linked manually to the project main info.plist for each pod frameworks. :) Such as below. enter image description here

After this, I could successfully install app to device or simulator. Hope this help everyone.

Solution 24 - Ios

Use automatic signing on 'signing and capabilities'

Solution 25 - Ios

My case's

Final solution:

  • upgrade from XCode 13.0 to XCode 13.1

Root cause

XCode's bug, not generated proper Provisioning Profile for iOS app/project

cause later:

  • can not install app: Unable to install
  • can not debug app: failed to get the task for process

both internal specific error reason is:

A valid provisioning profile for this executable was not found

Solution 26 - Ios

For me none the answers worked.

The solution was for me to got to your project, then select your project under "TARGETS". Go to "Build Phases" -> "[CP] Embeb Pods Frameworks" and unselect "For Install Builds Only".

Yes, this is disabled in default, but I turned it on once for a problem I had.

Solution 27 - Ios

Xcode 11.2 is deprecated by Apple on November 5, 2019

Even if you can install it on your device, you can't pass AppStore: See here for logs

Download the latest valid to AppStore version xip file.


Xcode 11.2 had some issues and crashes older iOS devices and does not install on newer iOS devices. So for now you can:

So The Solution is:

  1. Update macOS to 10.15.1
  2. Install Xcode 11.2.1 GM seed
  3. Build and install the app on the updated device (13.2.2 is out now)


All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionBrittanyView Question on Stackoverflow
Solution 1 - IosLean van HeerdenView Answer on Stackoverflow
Solution 2 - IosVittal PaiView Answer on Stackoverflow
Solution 3 - IosGovani Dhruv VijaykumarView Answer on Stackoverflow
Solution 4 - IosacoderView Answer on Stackoverflow
Solution 5 - Iosm1sh0View Answer on Stackoverflow
Solution 6 - IosMichael MontalbanoView Answer on Stackoverflow
Solution 7 - IosyoAlex5View Answer on Stackoverflow
Solution 8 - IosHeartless VayneView Answer on Stackoverflow
Solution 9 - IosTeja Kumar BethinaView Answer on Stackoverflow
Solution 10 - IosPetter BrakaView Answer on Stackoverflow
Solution 11 - IosCrazy DeveloperView Answer on Stackoverflow
Solution 12 - Iosuser1791914View Answer on Stackoverflow
Solution 13 - IosiGWView Answer on Stackoverflow
Solution 14 - IosSaheyView Answer on Stackoverflow
Solution 15 - IosfrankView Answer on Stackoverflow
Solution 16 - IosabedView Answer on Stackoverflow
Solution 17 - IosStunnerView Answer on Stackoverflow
Solution 18 - IosJP AquinoView Answer on Stackoverflow
Solution 19 - IosSubhankar MukherjeeView Answer on Stackoverflow
Solution 20 - IosstackichView Answer on Stackoverflow
Solution 21 - IosMuhammad UsmanView Answer on Stackoverflow
Solution 22 - IosCloudBalancingView Answer on Stackoverflow
Solution 23 - IosDarkHorseView Answer on Stackoverflow
Solution 24 - IosBruno MunizView Answer on Stackoverflow
Solution 25 - IoscrifanView Answer on Stackoverflow
Solution 26 - IosMuSoundiXView Answer on Stackoverflow
Solution 27 - IosMojtaba HosseiniView Answer on Stackoverflow