Reputation: 1143

An error was encountered while running (Domain = LaunchServicesError, Code = 0)

I received an error (Domain = LaunchServicesError, Code = 0) when trying to launch my app in the iOS Simulator with Xcode 6. I looked for solution in google, but I didn't find anything practical.

What does this error mean?

Upvotes: 70

Answers (30)

SeanR

Reputation: 7979

I have an app that is set up to use different bundle IDs based on the build configuration. When creating my Apple Watch extension, Xcode generated everything using my Release ID, so I had to go through and change it all manually for debugging. Here's all the places I had to change it:

WatchKit Extension's Build Settings -> Packaging -> Product Bundle Identifier
WatchKit Extension's Info.plist -> NSExtension -> NSExtensionAttributes -> WKAppBundleIdentifier (this needs to use the same prefix as your companion app)
WatchKit App's Info.plist -> WKCompanionAppBundleIdentifier

The last one took me a while since the WatchKit App's Info doesn't show up as a tab when viewing the target settings, I had to go direct to the Info.plist file itself.

Upvotes: 3

Toine Heuvelmans

Reputation: 707

The great explanation by Jeremy at least set me in the right direction, but despite having all the bundle identifiers and versions set correctly, the error still persisted. I then checked the Apple documentation which shows that the WatchKit extension (in its Copy Bundle Resources phase) copies the WatchKit app. This WatchKit app was named exactly the same as my iOS app, causing Xcode to confuse the two and read out the wrong plist, thinking the bundle identifier was incorrect. Renaming the Product of the WatchKit app to something distinct finally solved it for me.

Upvotes: 2

hitesh landge

Reputation: 362

"Reset Content and Settings" from iOS Simutalor menu options and launching simulator after Quitting solved my issue.

Upvotes: 2

UKDataGeek

Reputation: 6882

TLDR: Clear your Project Build Folder - and you will be free of this pain.

( plus I logged this as a bug with Apple as they need to find a way to fix this in Xcode )

None of these solutions worked for me - I banged my head against several walls.
I looked at the CoreSimulator log and I realised that it was trying to build a library that I had deleted. I couldn't find references to it anywhere.

Then I saw via another SO Question which unfortunately I can't find to reference, if you:

Hold down your option key then Product-> Clean option becomes Clean Build Folder
Press that and enjoy having your error vanish

Upvotes: 15

Ace Green

Reputation: 391

I had this problem too, turns out one of my info.plist was assigned to the target specifically when its suppose to be assigned to none. There is actually an Xcode settings recommendation warning, which I tapped and accepted the changes. This resolved the issue.

Upvotes: 0

smac89

Reputation: 43068

My Problem was that the wrapper extension for the target project was unset.

To fix I had to go to target project -> build settings -> Packaging -> Wrapper Extension.

Set this to "app" (No quotes)

This fixed the problem for me

Upvotes: 0

anjani kp

Reputation: 63

This error was showing up on my system when there was no hard disk space available. I freed up some space on my system for it to work.

Upvotes: 0

Zoltán

Reputation: 1450

Since everyone writes what they went through and how they fixed their exact problem, that might be unhelpful.

The problem is that there are different causes for the same error message and the right way of solving it is to open up ~/Library/Logs/CoreSimulator/CoreSimulator.log and look in there for the last message. This message gives you a good clue and sets you on the right path of solving your problem (sometimes it's bundle IDs, sometimes it's a missing or an extra attribute in the Info.plist, but you always get a good, descriptive clue).

This is how you narrow down the problem and eventually get to fix it.

Good luck and tough nerves with Xcode .)

Upvotes: 26

combinatorial

Reputation: 9561

I had the following in my log...

<Error>: Error Domain=LaunchServicesError Code=0 "(null)" UserInfo={Error=ExecutableTwiddleFailed...

This was due to there being no source files added in the extension project.

Upvotes: 0

Simon Rice

Reputation: 1139

One other possible solution to add to all of the others that will no doubt stay above mine ;)

I deleted & later reinstated a Today Extension target retaining the source files, but after trying every solution under the sun, I realised it didn't have any sources or resources in its target! You might encounter this as well if your detailed launch services error can't find your compiled app extension file.

So, long story short, make sure your target has something included to compile or bundle in there. You can check your target memberships by selecting the relevant file(s) on your project navigator (on the left) and setting your checkmark(s) as appropriate in the file inspector (that's the first tab on the right).

Upvotes: 0

Alexandre G

Reputation: 1693

Had a wrong app version set in InfoPlist.strings localization file. Urgh!

An hour gone!

Upvotes: 1

Alvin George

Reputation: 14296

My case was about framework compilation. I have enabled the 'copy only when installing' option from Target- Build Phases- Embedded Frameworks-

Upvotes: 3

Andrew Paul Simmons

Reputation: 4513

None of the above worked for me, but this did:

I simply deleted IceCream.xcworkspace/xcuserdata/xcuserdatad and then reset the simulator and ran the app again. (Reseting the simulator alone, did not work for me.)

Upvotes: 2

Stephen Watson

Reputation: 1710

I had this error whilst trying to build Apple's Lister Xcode Project and run it on the simulator.

The essentials which fixed it for me were:

1) BundleID for the iOS App and the iOS Extension had to be different 2) I provide iCloud and App Groups for both targets 3) I used Xcode's "Fix Issue" to fix the issues

After that I could build and run the app without warnings or errors.

The clue from the log file was "... LegacyErrorString=DuplicateIdentifier, FunctionName=-[MIInstallableBundle performPreflightWithError:], SourceFileLine=450, NSLocalizedDescription=The parent bundle has the same identifier (com.ACMECompany.Lister) as sub-bundle at /Users/stephen/Library/Developer/CoreSimulator/Devices/5329928B-946B-40A4-B666-EFD11B96D11F/data/Library/Caches/com.apple.mobile.installd.staging/temp.HQ5d9X/extracted/Lister.app/PlugIns/Lister.appex"

Upvotes: 1

user1870522

Reputation: 1

This worked for me: In project settings -> General tab -> Identity section I changed the Version number from something like 2.0.2 (three digits) to 2.0 (two digits) then I deleted the app in the simulator and run the project again. No more error after that.

Upvotes: 0

mikezs

Reputation: 422

I removed the key in watch app's .plist file that shouldn't have been there. And the problem disappeared.

Upvotes: 0

Jeff

Reputation: 2699

Open the Console app and look there. In my case it told me exactly what to do. I saw:

ErrorDescription=WatchKit 2 app extension's NSExtension.NSExtensionAttributes.WKAppBundleIdentifier value does not match WatchKit app's bundle ID (found "com.myCompany.MyApp.MyApp.watchkitapp"; expected "com.myCompany.MyApp.watchkitapp").

So, I went to each plist and checked any items that related to a BundleID. Then Clean, relaunch, etc.

Upvotes: 3

Thomas Besnehard

Reputation: 2095

I also have this error. In my case the log ~/Library/Logs/CoreSimulator/CoreSimulator.log was something like that :

Could not hardlink copy /Users/myUser/Library/Developer/CoreSimulator/Devices/60E569E7-6750-428A-A401-841BB081xxxx/data/Containers/Bundle/Application/70F24DDC-7954-46BF-B799-F807FD98yyyy/myApp.app to /Users/myUser/Library/Developer/CoreSimulator/Devices/60E569E7-6750-428A-A401-841BB081xxxx/data/Library/Caches/com.apple.mobile.installd.staging/temp.kOrJ9G/extracted/Payload/myApp.app with manifest /Users/myUser/Library/Developer/CoreSimulator/Devices/60E569E7-6750-428A-A401-841BB081xxxx/data/Library/Caches/com.apple.mobile.installd.staging/temp.kOrJ9G/extracted/com.apple.deltainstallcommands.com.mycompagny.myapp

thanks to this answer In look at my app info.plist. the key CFBundleVersion was missing so I add it and now everything is working !

Upvotes: 2

Jeremy Huddleston Sequoia

Reputation: 23623

This error indicates that there was a problem with installation. Unfortunately, Xcode does not actually print the contents of the error message that would give you more insight, but you can look at ~/Library/Logs/CoreSimulator/CoreSimulator.log to see the rest of the error details. There will also be more information about the problem in the simulated device's system log (~/Library/Logs/CoreSimulator/[Device UDID]/system.log); look for messages from installd around the time of the error).

Common causes for this include bundles missing an Info.plist, missing keys within your bundle's Info.plist, or values for some keys in the Info.plist not being allowed.

If your app's Info.plist does not contain a valid CFBundleVersion key/value pair, it is possible that your app may install correctly the first time but fail to update. Many users seem to work around this by doing a "Reset Contents & Settings" after each install, but it would be better to fix the root cause by setting an appropriate CFBundleVersion in the Info.plist. I believe iOS 8.2 now correctly returns an error on the first install in this case rather than just on updates, so hopefully this problem will be more obvious now.

Users with home directories on file systems that do not support hard links (eg: network home directories via AFP, SMB, or some NFS servers) may also run into problems related to hard linking. If this is the case, I suggest you create a path on your local HFS+ filesystem for simulator development (eg: /var/simulator/[user]) and create a symlink to that path from ~/Library/Developer/CoreSimulator. This particular issue was fixed in one of the iOS 8.2 betas.

In another case, the Build&Run would always succeed on the first try, but subsequent attempts would sometimes fail due to a changed Info.plist (eg: because someone's build system settings result in CFBundleVersion being different on each iteration). You can usually recover by either deleting the installed app (using a long-press from the home screen or xcrun simctl uninstall [Device UDID] [app identifier]) or erasing the device back to a default state. To erase the device, execute xcrun simctl erase [Device UDID] from terminal or choose Erase Contents & Settings from the iOS Simulator menu. This particular issue was fixed in one of the iOS 8.2 betas.

A newer instance of this issue is occurring for Xcode 6.2 users. If you have a WatchKit App Extension bundled in your app, it will fail to install to versions of the iOS Simulator runtime older than iOS 8.2. As a workaround, you will need to manually disable the app extension from installing when you want to test with iOS 8.1 and earlier runtimes.

If you need more specific help, please provide the entirety of the error message from CoreSimulator.log and any messages from installd and CoreSimulatorBridge that appear around the same time in ~/Library/Logs/CoreSimulator/[Device UDID]/system.log as that will reveal the underlying problem.

Upvotes: 120

Meg de Graaf

Reputation: 91

In XCode 6

An error was encountered while running (Domain = LaunchServicesError, Code = 0)

I had this error after making some major code changes to accommodate the iPhone 6 Screens. in Xcode 6 (iOS8)

I followed the options above and found that the only way to really get this fixed was by doing the following:

Deleted the derived data [go to Window >> Organizer >> (Find your App) Click on Delete next to the Derived Data]
Product >> Clean
Reset Contents and Settings in Simulator
Changed the Bundle Version to 1.4.1 from 1.4 in pList

Thank you for all the previous answers that got me to this stage. It worked a charm!

Upvotes: 9

gb_kf

Reputation: 93

This is what caused the problem for me: the build number for the main app and the extension were different (I had incremented the main app build number to 1.0.1.03, but left the extension at 1.0.1.02).

Making them match fixed the problem for me.

Upvotes: 3

possen

Reputation: 9266

One other thing to try, that worked for me, after resetting the simulator and doing a clean build did not help, is clearing out the derived data. To do this: go to Organizer click on project click on delete derived data button. I had this happen after working on an extension for a while and went back to the regular branch. Hope this helps.

Upvotes: 3

Sauvik Dolui

Reputation: 5660

"Reset Content and Settings" from iOS Simutalor menu options and launching simulator after Quitting solved my issue.

Reset Content and Settings

Upvotes: 12

keywind

Reputation: 1195

enter image description here

Delete your simulator and regenerate one.

It works for me.

Upvotes: 0

CFSoftware Malta

Reputation: 181

For me I just cleaned the project and it worked -> Product -> Clean

Upvotes: 18

jos

Reputation: 1070

In my case, the error was caused because i didn't set the build id.

Setting this, launches the emulator without problem.

Upvotes: 5

Maciek Czarnik

Reputation: 6181

So it's definitelly .plist problem. In my case it was empty NSExtensionMainStoryboard, removing this property fixed the problem

Upvotes: 1

BigCheesy

Reputation: 1138

If you've changed your bundle ID, make sure you do a clean build before trying to build it again! See how here: How to Empty Caches and Clean All Targets Xcode 4

Upvotes: 1