Xcode: Could not locate installed application. Install claimed to have succeeded, but application could not be found on device

Viewed 17670
20 Answers

I ran into the same issue while testing a app on iOS 13 via XCode 11.0. Building via the legacy system solved it (File > Workspace Settings... > Build System > Legacy Build System).

Hope it helps

As always, when the question is posted on SO, one finds a solution ;)

I edited the Scheme, setting the build configuration from debug to release and that installed the app again. Changed it back to debug and now it's running again as expected.

I had a similar issue after one of Carthage/XCode updates. It means iOS was not able to install app on the phone. XCode apparently is not able to provide this information directly. The first thing to do is open your phone console - go to Window/Devices and Simulators then select your device and click Open Console. In the console you can search for your app name what should provide you more detailed fail info. In my case it was sth like this:

Applications did fail to install: (
    "<LSApplicationProxy: 0x118913b60> com.mydomain.myapp (null) <com.mydomain.myapp <INVALID >:0>"
) (appInfos: (null))

There was another console log few rows before flagging the problem:

0x16f4df000 -[MIExecutableBundle codeSigningInfoByValidatingResources:performingOnlineAuthorization:ignoringCachedSigningInfo:checkingTrustCacheIfApplicable:error:]: 789: Code signing identifier (org.alamofire.Alamofire.iphonesimulator) does not match bundle identifier (org.alamofire.Alamofire.iphoneos) for /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.E83T1l/extracted/myapp.app/Frameworks/Alamofire.framework

There was an issue with one of the frameworks Alamofire I'm using in the project. I changed bundle identifier of the project and build framework again what solved the problem.

Hope it helps!

In my case, the problem was an embedded framework that was not being signed. In the General tab of the project settings, setting the embed setting to 'Embed & Sign' did the trick.

I was facing similar issue in Xcode 11.1. I have fix this issue. Not sure about this solution that it will to work for all or not.

My device iOS version was older then the iOS Xcode target build version.

Steps:

  1. I have put Xcode target Device to iPhone device OS version.
  2. Delete derived data
  3. Start xcode and open project
  4. Clean the project and gererate build and install in device

Note: Please check your developer account, certificate validation and already registered device warning.

Hope this solution will help some peoples. Happy coding.

On your iPhone go to Settings/General/Profiles & Devices/Apple Development: "YOUR APPLE ID" and delete all apps from there. It fixed the problem for me.

In my case it was a problem with new Development certificate. It's created automatically after Xcode updated to 11 and may not be included in current provisioning profile.

Uninstall all the other apps that are under the same "Organization" or "Bundle Identifier" with your current app and try again.

It works for me. Hope it does for you too.

After trying everything here, for me the solution was to change my distribution profile to use the new Apple distribution certificate that covers all apple platforms. This should be compliant with xcode 11 (if you're not experiencing one of the other million problems since the "upgrade").

The cert change is mentioned here: https://developer.apple.com/documentation/xcode_release_notes/xcode_11_release_notes

Cert creation instructions here: https://help.apple.com/developer-account/#/devbfa00fef7

Once done, make sure the correct profile is selected in Signing & Capabilities, and 'Apple Distribution' is selected under Build Setting -> Signing for the appropriate build configurations

A solution that solved this issue for me was to check the signing team for my tests target. Selecting the same development team then meant that my app was able to be built and run on device.

Build system: New Build System

Xcode: Version 11.1

It happened to me when trying to launch a watchOS app on a real device.

The only solution that worked was:

  • Delete iOS app from device
  • Delete watchOS app from device
  • Close and reopen Xcode
  • Clean build folder

I did a Product -> Clean then Build, and it was able to run.

Go to settings on your phone and wipe out all certificates and apps and then install your app again. That helped me

Problem occured on XCode 11

TL;DR:

Try changing Embed option in General=>Section Frameworks, Libraries.. to Do Not Embed (although it sounds strange)

In my General=>Section Frameworks, Libraries.. list are Security.framework and the CocoaPods Pods_projectname.framework amongst others. Default setting of these two was Do Not Embed. Sounded strange to me, so I changed it without need alternating to Embed & Sign or Embed Without Signing. With both options the error occured!

On your iPhone go to Settings/General/Profiles & Devices/Apple Deelopment: "YOUR APPLE ID" and delete all apps from there. It fixed the problem for me.

This was the solution that worked for me.

Please double check the bundle ID of the installed application to see if it is re-applied, this will also cause this problem .I uninstall the app and solve the problem.

In my case i have PROD certificate and trying to install the app in the device, later i changed to development certificate it got installed.

As Marcin's answer suggested, I visited the phone console and in my case, it is this error message:

-[MIFreeProfileValidatedAppTracker _onQueue_addReferenceForApplicationIdentifier:bundle:error:]: 182: This device has reached the maximum number of installed apps using a free developer profile: {(

So if you are signing your app with a Personal Team certificate, make sure that you don't have more than 3 apps.

Read more here: Why can I not install more than three apps?

As for me, I added a custom key-value to Info.plist of main watchOS application file. That was wrong. After removing it, all works correctly. It seems this is not allowed but where is no other information about it.

If you have other under-development apps installed, try uninstalling those you are not using, and run Xcode to install your app again. It works for me.

Related