Unable to run app in Simulator: An error was encountered while running (Domain = LaunchServicesError, Code = 0)

Question

After successfully compiling the project in Xcode 6, I am unable to run it in the simulator with the above mentioned message. I did all the possible research, tried everything and still no advances.

I am not working with swift, neither I use widgets or extensions, so please do not suggest solutions caused by these as can be seen in similar questions.

If someone found a possible cause (or solution!!) other than these, please help. Thanks

it would be helpful if you can list what you have tried to exclude those recommendations. — donmarkusi, Sep 17 '14 at 11:48
The issue is now resolved, but just for information I tried: - running a clean - removing the project cache/derived data - restarting both Simulator and Xcode - restarting the Mac - reinstalling Xcode - cleaning and reinstalling CocoaPods - checking Build Settings for any rare appearances Nothing helped. Did't try fiddling with app extensions naming as I do not use any. — Miki, Sep 17 '14 at 15:39
I had this problem: http://stackoverflow.com/questions/27037589/xcode-6-1-installation-failed-invalid-argument-when-trying-to-run-today-appli#comment52061760_29645687 — derpoliuk, Oct 10 '15 at 10:04

score 179 · Answer 1 · answered Dec 19 '14 at 11:04

179

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

Reset Content and Settings

answered Dec 19 '14 at 11:04

Sauvik Dolui

5,520
3
34
44

6

Way better than initial answer. Should be marked as the solution. – denislexic Jun 16 '15 at 20:33
After that I also needed to quit and reopen the simulator. – jfredsilva Oct 29 '15 at 08:07
This requirement is already mentioned in my answer @jfredsilva. – Sauvik Dolui Oct 29 '15 at 09:15
1

Also deleting the App if you had previously installed it on the simulator – danywarner Jun 07 '16 at 15:50
Worked for me after also deleting Derived Data – fruechtemuesli Aug 04 '16 at 08:54

score 125 · Answer 2 · edited Dec 26 '22 at 02:13

125

Cleaning the build folder resolved the issue for me.

(While holding down the Alt-key: Product > Clean build folder)

edited Dec 26 '22 at 02:13

starball

20,030
7
43
238

answered Jul 01 '15 at 07:52

Hannes Lohmander

1,315
1
8
8

1

This worked for me after I updated to use Cocoapods and the .xcworkspace. – Friendly King May 11 '16 at 16:27
3

This is a must-do after updating to Cocoapods v1.0.0 – Anconia May 24 '16 at 00:56
Best answer so far, tried everything from resetting app + cleaning xcode to deleting and reinstalling all the pods, nothing worked until i found this. – thibaut noah Oct 04 '16 at 08:36

score 33 · Answer 3 · answered Nov 19 '15 at 05:14

33

I tried every other solution listed here. Well, I ported my project from Swift 1.2 to Swift 2.0. The application was stuck even after a lot debugging and launch services error 0 was reported.

solution: It happens because of framework compilation.

App target -> Build Phases -> Embed Frameworks.

So mark copy only when installing on. Clean the project and run it!

answered Nov 19 '15 at 05:14

Alvin George

14,148
92
64

Can you explain more about how "Copy only when installing" fixes the problem? – sethfri Jan 08 '16 at 22:51
@ sethfri : "Copy only when installing" to specify that the build phase copies files only in install builds of the product. https://developer.apple.com/library/mac/recipes/xcode_help-project_editor/Articles/CreatingaCopyFilesBuildPhase.html – Alvin George Jan 11 '16 at 05:30
4

I understand what the words "Copy only when installing" mean. I'm asking how this fixes the problem the question author is facing. – sethfri Jan 16 '16 at 06:48

score 28 · Accepted Answer · answered Sep 17 '14 at 15:30

28

This has now been resolved. The problem was caused by ShareKit library added by CocoaPods for compatibility reasons. After removing the library and all related code, the app successfully launched in simulator. I recommend checking the system log for more details on the issue as to me it pointed me in the right direction (stating the name of conflicting library).

answered Sep 17 '14 at 15:30

Miki

1,262
1
9
10

I just added shareKit and I have the same problem. – YoungDinosaur Sep 25 '14 at 20:41
25

In case this helps anyone: You can access the system log by typing Console in Spotlight. – Nate Cook Sep 09 '15 at 20:21
For me it was the MixpanelAppExtension – villy393 Apr 20 '16 at 07:42
Thanks, this helped me out. XCode 7.3.1 and my log showed "ErrorDescription=Could not hardlink copy". I was setting a version but not build number in Target -> General -> Identity. Once I included a value for Build the problem went away. – William Smith May 30 '16 at 17:52
To check system log try this command in Terminal: tail -f /var/log/system.logiOS Simulator prints directly to stdout, so you can see the logs mixed up with system logs. – vhong Jun 09 '16 at 10:56
ShareKit was not my issue, but the recommendation to check the console log helped me track down the actual issue, which in my case was a bad bundle ID. – Christopher Pickslay Jun 23 '16 at 22:29
Myframework.framework did not have a CFBundleIdentifier in its Info.plist but everywhere the key is present – Abhishek Thapliyal Aug 22 '16 at 11:42

score 16 · Answer 5 · edited Oct 30 '16 at 04:13

In case anyone has this problem in combination with cocoa pods, these steps helped me to solve this error (after few hours):

run pod cache clean
from SRC_ROOT run rm -rf Pods (optionally rm Podfile.lock)
Click on the Simulator app, click Simulator -> Reset Content and Settings...
Go into Xcode, In the Menu bar click Product -> Clean (or click Shift + Command + K).This will to clean your Xcode project.
Create a new Terminal Shell (From menu bar click Shell -> New Window)
run rm -rf ~/Library/Developer/Xcode/DerivedData/

...then try to Build & Run your project.

Note: SRC_ROOT can be found by entering the Navigator, clicking on the project, clicking on the project again from the project and targets list, going into Build Settings, scrolling all the way to the bottom to the User-Defined Section, and the SRC_ROOT will be labeled as PODS_ROOT. Take that and copy it verbatum into the Terminal and proceed with step 2 from the list above.

Hope it helps.

This did it. Thank you! Really should be the accepted answer. — Dan Loewenherz, Sep 18 '16 at 04:45
That solved my issue! Definitely it should be the accepted answer! — Victor Oliveira Antonino, Sep 22 '16 at 17:11

Dharmbir Singh · Answer 6 · 2016-01-06T09:07:54.053

15

I get rid from the issue by the given steps for simulator

1. Way

Reset Content and Settings of Simulator.
Clean your project by Cmd+Shift+K.
Clear your Derived Data.
The last one which is more important change your Bundle Identifier by "com.yourcompanyname.projectname" like "com.facebook.Facebook"

2. Way

You can do only be the given line, it works for me

The last one which is more important change your Bundle Identifier by "com.yourcompanyname.projectname" like "com.facebook.Facebook"

Thanks and enjoy programming.

edited Jan 06 '16 at 09:07

answered Nov 25 '15 at 13:28

Dharmbir Singh

17,485
5
50
66

Do you mean `cmd` instead of `win`? ;) (Or maybe you use a windows keyboard.) – Jeroen Jan 05 '16 at 21:46
@JeroenJK Yes its Cmd. – Dharmbir Singh Jan 06 '16 at 05:07
Wow, the bundle ID change is the one that finally worked for me. Thanks! – ArtSabintsev Jun 18 '16 at 04:56

score 6 · Answer 7 · edited May 23 '17 at 11:47

6

Might be related to this issue: "This app contains an app extension with an illegal bundle identifier" issue

I had to format the bundle identifiers for my app and extension as follows:

com.company.AppName
com.company.AppName.Extension

edited May 23 '17 at 11:47

Community

1
1

answered Dec 01 '15 at 09:48

Azin Mehrnoosh

171
3
3

Same here. I changed the bundle identifier because the extension(widget) was not showing up, and that caused it. Had to lower the extension version from 9.2 to 8.2 and change the bundle as mentioned above. – Dec 21 '15 at 20:28
Thanks, exactly my problem! – Andres Jan 04 '16 at 15:01

score 6 · Answer 8 · answered Feb 17 '16 at 15:44

6

First "Reset Content and Settings"
If you didn't fill the build number and fill it and Run.

It's solved for me.

answered Feb 17 '16 at 15:44

Chathurka

605
6
11

score 4 · Answer 9 · answered Mar 25 '15 at 15:33

4

If you change the name of the supplied class InterfaceController set by default when you start a new project. This class is referenced in the Info.plist under the key RemoteInterfacePrincipalClass. In my case, I got the error mentioned by the OP until I fixed the name of the class in there (see screenshot).

Info.plist: set principal class

answered Mar 25 '15 at 15:33

charles

11,212
3
31
46

That really helped! Thanks! – Vivienne Fosh Aug 10 '15 at 16:21

score 2 · Answer 10 · edited Jul 20 '16 at 10:32

Thanks for pointing this out @Miki and kudos to you. I had the same issue as you yesterday (and I added ShareKit 3.0.0 from CocoaPods to the app a few days ago). I suspected ShareKit giving me this problem, but now I can be confident of exactly which library is causing this. Here is what I found in my log (if it can benefit others):

Error Domain=LaunchServicesError Code=0 "The operation couldn’t be completed. (LaunchServicesError error 0.)" UserInfo=0x7fa836097aa0 {Error=PackageInspectionFailed, ErrorDescription=Failed to load Info.plist from bundle at path /Users/{UserName}/Library/Developer/CoreSimulator/Devices/99FEB34E-6F00-4EFA-861A-A6985AFE96D8/data/Library/Caches/com.apple.mobile.installd.staging/temp.X7eead/extracted/{AppName}.app/Frameworks/LiveSDK.framework}

from your log, how can you know that ShareKit causes the error? — chipbk10, Oct 13 '14 at 13:57
i have the same thing in my log but removing simulators and adding them back doesn't help... how did you fix the error? — Amitay, Oct 20 '14 at 08:59

score 2 · Answer 11 · answered Sep 22 '15 at 14:41

2

If you are here after having issues doing an integration with WatchOS 2.0, go to - ~/Library/Logs/CoreSimulator/[Device UDID]/system.log and if says something like WatchKit 2 app has frameworks; that's not allowed. then follow the link below.

http://zyafa.me/blog/watchos-2-and-embedded-frameworks

answered Sep 22 '15 at 14:41

insanoid

413
2
10

1

Thanks for pointing me to the simulator log file. In my case the log file at `~/Library/Logs/CoreSimulator/CoreSimulator.log` disclosed that my linked framework did not have a `CFBundleIdentifier` in its Info.plist – berbie Nov 11 '15 at 10:27
framework did not have a CFBundleIdentifier in its Info.plist : i'm also getting this what is the solution? not using on watchkit or watchOS – Abhishek Thapliyal Aug 19 '16 at 06:35

score 1 · Answer 12 · answered Oct 20 '15 at 17:33

1

I'm adMob user and I solved enabling "Copy only when installing" in App target -> Build Phases -> Embed Frameworks.

answered Oct 20 '15 at 17:33

Matte.Car

2,007
4
23
41

MuHAOS · Answer 13 · 2015-12-21T11:04:13.623

1

Have the same problem after localizing my app. Especially Info.plist. Seems I had empty CFBundleShortVersionString in InfoPlist.strings, after fixing that the simulator started to work properly.

edited Dec 21 '15 at 11:04

answered Dec 21 '15 at 10:50

MuHAOS

1,108
9
8

That was my problem too. If you see that try to remove all keys that not requires localisation from your InfoPlist.strings files. In my case removing keys below fixed everything: CFBundleName CFBundleShortVersionString CFBundleVersion – lazarev May 30 '16 at 06:24

score 1 · Answer 14 · answered May 07 '16 at 14:45

1

I got this issue by adding a folder reference named "Resources".

If I give it another name, then it runs !

answered May 07 '16 at 14:45

Moose

2,607
24
23

1

This one solved me a similar issue! I was embedding a dylib, and it caused a cryptic "did not have a CFBundleIdentifier in its Info.plist" installation error. After changing the Resources folder to something else it started working again – Sagi Iltus Jul 11 '17 at 14:29
Two birds with one stone ;) – Moose Jul 11 '17 at 21:16

score 1 · Answer 15 · answered Jun 23 '16 at 22:31

1

There are a number of things that can cause this error. The best general answer is to search the console log for CoreSimulator, as the simulator logs the underlying problem when it displays this message.

answered Jun 23 '16 at 22:31

Christopher Pickslay

17,523
6
79
92

score 1 · Answer 16 · answered Aug 11 '16 at 05:45

If you have installed any libraries using CocoaPods while XCode was open, all you have to do is, Close XCode and remove the library from Pod file, run the command pod install it will uninstall that library. then install library again. Please make sure that XCode is always closed while installing and uninstalling libraries.

score 0 · Answer 17 · answered Sep 24 '14 at 13:05

I hade exactly the same problem and it was ShareKit.

On the simulator I had "Error Domain=LaunchServicesError Code=0".

On the iPhone6 device I had "App installation failed Could not inspect the application package."

When I removed ShareKit it worked.

score 0 · Answer 18 · answered Mar 24 '15 at 22:57

0

I had this problem when I added an Apple Watch target to my app, and accidentally removed the InterfaceController.m file. Adding back the file in the target fixed the problem.

answered Mar 24 '15 at 22:57

spybart

2,583
3
22
33

score 0 · Answer 19 · answered Apr 08 '15 at 19:20

There are different things that can cause this. Looking in the console may well give you a clue.

In my case - the issue was an extension built before I changed the name of the product. Xcode didn't clear the old one out, then got stressed at two extensions with the same bundle id.

(Deleting the build folder fixed my particular issue).

score 0 · Answer 20 · answered Sep 17 '15 at 09:33

0

In my case the issue came from an icon set added with some images missing. Once I replaced the icon set with another one, and uninstalled the app in the simulator; I was able to run it again.

answered Sep 17 '15 at 09:33

iyepes

125
1
9

score 0 · Answer 21 · answered Oct 05 '15 at 19:35

0

I removed all my pod files and replaced them all, seems the problem for me was the bolts framework was old, and causing this error. I did a clean & reset content and now it's all good.

answered Oct 05 '15 at 19:35

ReduxDJ

480
7
14

score 0 · Answer 22 · answered Nov 02 '15 at 01:07

0

Do not add the google maps framework to the embedded lib section this solved my build break.

answered Nov 02 '15 at 01:07

Ravi Dalmia

75
5

Removing the embedded framework that wasn't necessary to be there fixed my issue also – manman Jul 19 '16 at 00:30

score 0 · Answer 23 · answered Apr 28 '16 at 12:45

0

I had this error in developing app for Apple Watch after adding in Info.plist: "App Transport Security Settings" and "Allow Arbitry Loads" = YES. (In WatchKit App, in WatchKit Extension is good!!) Deleting this two rows, it keeps working.

answered Apr 28 '16 at 12:45

Alessandro Mattiuzzi

2,309
2
18
24

score 0 · Answer 24 · answered May 24 '16 at 08:02

For me, the problem occurs because I added my framework (GoogleMobileAds.framework in my case) to Embedded Binaries, not Linked Frameworks and Libraries.

For your information, AdMob instructs you to use Add Files to "Your Project" menu on Xcode, but I was too lazy to obey the instruction.

score 0 · Answer 25 · answered Jul 11 '16 at 22:00

I had this problem when trying to run UI tests in a project containing AWS Cognito.

Here's how I resolved it.

Select the UI test target.
Click on the Build Phases section.
Click the plus to add a Copy Files phase
In the Copy Files phase, change the destination to Frameworks (see the last image)
Hit the plus below the Copy Files phase.
Select the framework for which you're receiving an error and hit the Add button (yours will probably not be the first item in your project hierarchy). It should end up looking like this.
Repeat steps 5 and 6 for all frameworks giving you an error.
Run your tests.

Unable to run app in Simulator: An error was encountered while running (Domain = LaunchServicesError, Code = 0)

25 Answers25

Linked