Latest react-native app doesn't work ":CFBundleIdentifier", Does Not Exist #7308

Closed
arun0009 opened this Issue Apr 30, 2016 · 294 comments

Comments

Projects
None yet
@arun0009

On OS X El Capitan v10.11.4

node --version v6.0.0
npm --v 3.8.8
react-native-cli: 0.2.0
react-native: 0.24.1
watchman --v 4.4.0
xcode 7.3

$ react-native init AwesomeProject
$ cd AwesomeProject
$ react-native run-ios

** BUILD FAILED **


The following build commands failed:
    PhaseScriptExecution Run\ Script /development/misc/react/AwesomeProject/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Script-006B79A01A781F38006873D1.sh
(1 failure)
Installing build/Build/Products/Debug-iphonesimulator/AwesomeProject.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist
/development/misc/react/AwesomeProject/node_modules/promise/lib/done.js:10
      throw err;
      ^

Error: Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/AwesomeProject.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

    at checkExecSyncError (child_process.js:470:13)
    at Object.execFileSync (child_process.js:490:13)
    at _runIOS (runIOS.js:91:34)
    at runIOS.js:24:5
    at tryCallTwo (/development/misc/react/AwesomeProject/node_modules/promise/lib/core.js:45:5)
    at doResolve (/development/misc/react/AwesomeProject/node_modules/promise/lib/core.js:200:13)
    at new Promise (/development/misc/react/AwesomeProject/node_modules/promise/lib/core.js:66:3)
    at Array.runIOS (runIOS.js:23:10)
    at Object.run (/development/misc/react/AwesomeProject/node_modules/react-native/local-cli/cli.js:86:13)
    at Object.<anonymous> (/usr/local/lib/node_modules/react-native-cli/index.js:88:7)
@grabbou

This comment has been minimized.

Show comment
Hide comment
@grabbou

grabbou Apr 30, 2016

Collaborator

I saw you posted on StackOverflow as well - any luck so far? I am playing around with master at the moment and I can't reproduce. Maybe it's one of the problems described there, e.g. the sudo or permissions? Also do you have CFBundleIdentifier in your Info.plist ?

Collaborator

grabbou commented Apr 30, 2016

I saw you posted on StackOverflow as well - any luck so far? I am playing around with master at the moment and I can't reproduce. Maybe it's one of the problems described there, e.g. the sudo or permissions? Also do you have CFBundleIdentifier in your Info.plist ?

@arun0009

This comment has been minimized.

Show comment
Hide comment
@arun0009

arun0009 May 1, 2016

I tried deleting all my node modules, clear cache etc and sudo as well with no luck. I do have CFBundleIdentifier in the Info.plist as:

<key>CFBundleIdentifier</key>
<string>org.reactjs.native.example.$(PRODUCT_NAME:rfc1034identifier)</string>

arun0009 commented May 1, 2016

I tried deleting all my node modules, clear cache etc and sudo as well with no luck. I do have CFBundleIdentifier in the Info.plist as:

<key>CFBundleIdentifier</key>
<string>org.reactjs.native.example.$(PRODUCT_NAME:rfc1034identifier)</string>
@dsibiski

This comment has been minimized.

Show comment
Hide comment
@dsibiski

dsibiski May 1, 2016

Contributor

@grabbou Are you trying it with Node 6? I haven't been able to reproduce it, but I've only tried so far with Node 4 & 5, haven't installed 6 yet. Perhaps it's an issue there?

Contributor

dsibiski commented May 1, 2016

@grabbou Are you trying it with Node 6? I haven't been able to reproduce it, but I've only tried so far with Node 4 & 5, haven't installed 6 yet. Perhaps it's an issue there?

@arun0009

This comment has been minimized.

Show comment
Hide comment
@arun0009

arun0009 May 1, 2016

@dsibiski I had node 5.9 before and I had the same issue, I uninstalled node/npm and deleted every node module and reinstalled (that's when I got node 6 on my machine) but I still am stuck with the above exception.

arun0009 commented May 1, 2016

@dsibiski I had node 5.9 before and I had the same issue, I uninstalled node/npm and deleted every node module and reinstalled (that's when I got node 6 on my machine) but I still am stuck with the above exception.

@shinout

This comment has been minimized.

Show comment
Hide comment
@shinout

shinout May 1, 2016

I also encountered a similar error.

On OS X El Capitan v10.11.4

node --version v6.0.0
npm --v 3.8.6
react-native-cli: 0.2.0
react-native: 0.24.1
watchman --v 4.4.0
xcode 7.3

$ react-native init AwesomeProject
$ cd AwesomeProject
$ react-native run-ios

** BUILD SUCCEEDED **

The following commands produced analyzer issues:
Analyze Modules/RCTUIManager.m
(1 command with analyzer issues)
Installing build/Build/Products/Debug-iphonesimulator/AwesomeProject.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist
/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/done.js:10
throw err;
^

Error: Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/AwesomeProject.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

    at checkExecSyncError (child_process.js:470:13)
    at Object.execFileSync (child_process.js:490:13)
    at _runIOS (runIOS.js:91:34)
    at runIOS.js:24:5
    at tryCallTwo (/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/core.js:45:5)
    at doResolve (/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/core.js:200:13)
    at new Promise (/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/core.js:66:3)
    at Array.runIOS (runIOS.js:23:10)
    at Object.run (/Users/shinout/workspace/AwesomeProject/node_modules/react-native/local-cli/cli.js:86:13)
    at Object.<anonymous> (/usr/local/lib/node_modules/react-native-cli/index.js:88:7)

In my case, BUILD seems to succeed. However, the process terminates with the error message above.

shinout commented May 1, 2016

I also encountered a similar error.

On OS X El Capitan v10.11.4

node --version v6.0.0
npm --v 3.8.6
react-native-cli: 0.2.0
react-native: 0.24.1
watchman --v 4.4.0
xcode 7.3

$ react-native init AwesomeProject
$ cd AwesomeProject
$ react-native run-ios

** BUILD SUCCEEDED **

The following commands produced analyzer issues:
Analyze Modules/RCTUIManager.m
(1 command with analyzer issues)
Installing build/Build/Products/Debug-iphonesimulator/AwesomeProject.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist
/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/done.js:10
throw err;
^

Error: Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/AwesomeProject.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

    at checkExecSyncError (child_process.js:470:13)
    at Object.execFileSync (child_process.js:490:13)
    at _runIOS (runIOS.js:91:34)
    at runIOS.js:24:5
    at tryCallTwo (/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/core.js:45:5)
    at doResolve (/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/core.js:200:13)
    at new Promise (/Users/shinout/workspace/AwesomeProject/node_modules/promise/lib/core.js:66:3)
    at Array.runIOS (runIOS.js:23:10)
    at Object.run (/Users/shinout/workspace/AwesomeProject/node_modules/react-native/local-cli/cli.js:86:13)
    at Object.<anonymous> (/usr/local/lib/node_modules/react-native-cli/index.js:88:7)

In my case, BUILD seems to succeed. However, the process terminates with the error message above.

@ms88privat

This comment has been minimized.

Show comment
Hide comment
@ms88privat

ms88privat May 1, 2016

I got the same problem on one of my projects... You could kind work around with only XCode builds. I think it appeared after changing the name of the project.

I got the same problem on one of my projects... You could kind work around with only XCode builds. I think it appeared after changing the name of the project.

@arun0009

This comment has been minimized.

Show comment
Hide comment
@arun0009

arun0009 May 2, 2016

I was able to solve this issue! Looks like port 8081 was in use :

lsof -n -i4TCP:8081
node    7601 CXI624   23u  IPv6 0xc6b249599e5f1169      0t0  TCP *:sunproxyadmin (LISTEN)

So I followed the instructions from React Native Troubleshooting https://facebook.github.io/react-native/docs/troubleshooting.html

kill - 9 7601

and ran the command react-native run-ios again and everything worked as expected (on node 6 as well).

Closing this issue & thanks for your help!

arun0009 commented May 2, 2016

I was able to solve this issue! Looks like port 8081 was in use :

lsof -n -i4TCP:8081
node    7601 CXI624   23u  IPv6 0xc6b249599e5f1169      0t0  TCP *:sunproxyadmin (LISTEN)

So I followed the instructions from React Native Troubleshooting https://facebook.github.io/react-native/docs/troubleshooting.html

kill - 9 7601

and ran the command react-native run-ios again and everything worked as expected (on node 6 as well).

Closing this issue & thanks for your help!

@arun0009 arun0009 closed this May 2, 2016

@dsibiski

This comment has been minimized.

Show comment
Hide comment
@dsibiski

dsibiski May 2, 2016

Contributor

@arun0009 Awesome, thanks for posting the answer back here 👍

Contributor

dsibiski commented May 2, 2016

@arun0009 Awesome, thanks for posting the answer back here 👍

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 13, 2016

@shinout Hello, I have the same problem, you solve?

ghost commented May 13, 2016

@shinout Hello, I have the same problem, you solve?

@shinout

This comment has been minimized.

Show comment
Hide comment
@shinout

shinout May 13, 2016

Not yet... I finally bought a new mac and solved.

shinout commented May 13, 2016

Not yet... I finally bought a new mac and solved.

@consideRatio

This comment has been minimized.

Show comment
Hide comment
@consideRatio

consideRatio May 17, 2016

I solved this issue with the react-native upgrade command, which helped me reset some details in various xcode files. At least that is what I think solved the issue.

I solved this issue with the react-native upgrade command, which helped me reset some details in various xcode files. At least that is what I think solved the issue.

@stief510

This comment has been minimized.

Show comment
Hide comment
@stief510

stief510 May 25, 2016

This isn't working for me. I'm still getting the same error. Node 5.11

This isn't working for me. I'm still getting the same error. Node 5.11

@andreacab

This comment has been minimized.

Show comment
Hide comment
@andreacab

andreacab May 26, 2016

Still getting the error too. Killing process on port 8081 did not work.
react-native-cli: 0.2.0
react-native: 0.26.2
node: 5.3.0
npm: 3.3.12

Tested with a new project setup by running
$ react-native init newProj && cd newProj
$ react-native run-ios

Typing the following doesn't give the issue but a "No devices are booted"..

sudo react-native run-ios

Had another react packager running on 8081. Killing that process made it to work.

andreacab commented May 26, 2016

Still getting the error too. Killing process on port 8081 did not work.
react-native-cli: 0.2.0
react-native: 0.26.2
node: 5.3.0
npm: 3.3.12

Tested with a new project setup by running
$ react-native init newProj && cd newProj
$ react-native run-ios

Typing the following doesn't give the issue but a "No devices are booted"..

sudo react-native run-ios

Had another react packager running on 8081. Killing that process made it to work.

@stief510

This comment has been minimized.

Show comment
Hide comment
@stief510

stief510 May 26, 2016

Running it with sudo does not solve it for me.

Running it with sudo does not solve it for me.

@joshschumacher

This comment has been minimized.

Show comment
Hide comment
@joshschumacher

joshschumacher May 27, 2016

The suggest solution by @consideRatio fixed this problem for me.

react-native upgrade

The suggest solution by @consideRatio fixed this problem for me.

react-native upgrade
@rjain15

This comment has been minimized.

Show comment
Hide comment
@rjain15

rjain15 May 28, 2016

Worked after upgrading XCode to 7.3.1

rjain15 commented May 28, 2016

Worked after upgrading XCode to 7.3.1

@iwgang iwgang referenced this issue in iwgang/GankCamp-React-Native Jun 7, 2016

Open

你好,我IOS run 不起来 #1

@hzalaz hzalaz referenced this issue in auth0/react-native-lock Jun 7, 2016

Closed

Build fails with vanilla project #60

@bradennapier

This comment has been minimized.

Show comment
Hide comment
@bradennapier

bradennapier Jun 11, 2016

Nothing posted here works for me unfortunately :(

Nothing posted here works for me unfortunately :(

@rosiakr

This comment has been minimized.

Show comment
Hide comment
@rosiakr

rosiakr Jun 13, 2016

In my case my ProductName got corrupted.

I had to change my project name, scheme name for my project and Product Name so they are all the same, and after that I started seeing the errors mentioned above.
When I went to Info.plist to check what it says for my CFBundleIdentifier (or just "Bundle identifier" if you are viewing Info.plist in Xcode) I saw:
com.{company}.mobile.$(PRODUCT_NAME:rfc1034identifier)
So It's a path.
So I decided to investigate in Xcode - I clicked on the project name in left pane and went to BuildSettings. Under Packaging my ProductName instead of being, say "MyAwesomeApp" was something like "MyAwesomeAppApp" - last part was repeated twice. Needless to say I had to change it to match my ProjectName (MyAwesomeApp), saved in Xcode and

$ react-native run-ios

worked w/out any problems.
Now it makes sense why it was showing errors:
"An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle."
The "path" was wrong!
Hope it helps someone.

rosiakr commented Jun 13, 2016

In my case my ProductName got corrupted.

I had to change my project name, scheme name for my project and Product Name so they are all the same, and after that I started seeing the errors mentioned above.
When I went to Info.plist to check what it says for my CFBundleIdentifier (or just "Bundle identifier" if you are viewing Info.plist in Xcode) I saw:
com.{company}.mobile.$(PRODUCT_NAME:rfc1034identifier)
So It's a path.
So I decided to investigate in Xcode - I clicked on the project name in left pane and went to BuildSettings. Under Packaging my ProductName instead of being, say "MyAwesomeApp" was something like "MyAwesomeAppApp" - last part was repeated twice. Needless to say I had to change it to match my ProjectName (MyAwesomeApp), saved in Xcode and

$ react-native run-ios

worked w/out any problems.
Now it makes sense why it was showing errors:
"An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle."
The "path" was wrong!
Hope it helps someone.

@yellowbang

This comment has been minimized.

Show comment
Hide comment
@yellowbang

yellowbang Jun 16, 2016

If you have some other applications are always occupying port 8081 no matter how many times you have killed the process, try changing the port:

http://stackoverflow.com/questions/30216417/react-native-port-8081-already-in-use-packager-is-either-not-running-or-not-r

It solves my problem.
Hope it helps someone.

yellowbang commented Jun 16, 2016

If you have some other applications are always occupying port 8081 no matter how many times you have killed the process, try changing the port:

http://stackoverflow.com/questions/30216417/react-native-port-8081-already-in-use-packager-is-either-not-running-or-not-r

It solves my problem.
Hope it helps someone.

@idris

This comment has been minimized.

Show comment
Hide comment
@idris

idris Jun 16, 2016

I still get the same Entry, ":CFBundleIdentifier", Does Not Exist error that this ticket mentions. I've tried:

  • killing processes on port 8081
  • changing the port
  • running it with sudo
  • updating react-native (I'm on the latest version)

Any other ideas?

Interestingly enough, everything works if I open the .xcworkspace in XCode and run it from there.

idris commented Jun 16, 2016

I still get the same Entry, ":CFBundleIdentifier", Does Not Exist error that this ticket mentions. I've tried:

  • killing processes on port 8081
  • changing the port
  • running it with sudo
  • updating react-native (I'm on the latest version)

Any other ideas?

Interestingly enough, everything works if I open the .xcworkspace in XCode and run it from there.

@stief510

This comment has been minimized.

Show comment
Hide comment
@stief510

stief510 Jun 16, 2016

What ended up working for me was that I needed to open up in XCode and change the scheme from building for a Release to Debug. Don't know if that will work for anyone else but it is definitely something to check out. After changing it once, you can then run it react-native run-ios via the command line

stief510 commented Jun 16, 2016

What ended up working for me was that I needed to open up in XCode and change the scheme from building for a Release to Debug. Don't know if that will work for anyone else but it is definitely something to check out. After changing it once, you can then run it react-native run-ios via the command line

@y0unghe

This comment has been minimized.

Show comment
Hide comment

y0unghe commented Jun 18, 2016

@joshschumacher upgrade worked.

@gvlamadrid

This comment has been minimized.

Show comment
Hide comment
@gvlamadrid

gvlamadrid Jun 27, 2016

When nothing fixes, try on Xcode

  1. Go to File -> Project settings
  2. Click the Advanced button
  3. Select "Custom" and select "Relative to Workspace" in the pull down
  4. click done, done

When nothing fixes, try on Xcode

  1. Go to File -> Project settings
  2. Click the Advanced button
  3. Select "Custom" and select "Relative to Workspace" in the pull down
  4. click done, done
@sydneyitguy

This comment has been minimized.

Show comment
Hide comment
@sydneyitguy

sydneyitguy Jul 2, 2016

@stief510 That worked for me! Thanks!

@stief510 That worked for me! Thanks!

@trevorwang

This comment has been minimized.

Show comment
Hide comment
@trevorwang

trevorwang Jul 4, 2016

As @gvlamadrid said

When nothing fixes, try on Xcode

  1. Go to File -> Project settings
  2. Click the Advanced button
  3. Select "Custom" and select "Relative to Workspace" in the pull down
  4. click done, done

5 pic

As @gvlamadrid said

When nothing fixes, try on Xcode

  1. Go to File -> Project settings
  2. Click the Advanced button
  3. Select "Custom" and select "Relative to Workspace" in the pull down
  4. click done, done

5 pic

@shargon

This comment has been minimized.

Show comment
Hide comment
@shargon

shargon Jul 11, 2016

nothing work for me...

shargon commented Jul 11, 2016

nothing work for me...

@jevakallio jevakallio referenced this issue in futurice/pepperoni-app-kit Jul 12, 2016

Closed

Error to build iOS app on fresh clone #77

@cpruijsen

This comment has been minimized.

Show comment
Hide comment
@cpruijsen

cpruijsen Jul 15, 2016

Did not fix it for me (I killed ports, changed project settings, etc etc.)

Did not fix it for me (I killed ports, changed project settings, etc etc.)

@shadowfax92

This comment has been minimized.

Show comment
Hide comment
@shadowfax92

shadowfax92 Jul 17, 2016

Nothing worked for me too. Using node v6.2.2

Nothing worked for me too. Using node v6.2.2

@tomazahlin

This comment has been minimized.

Show comment
Hide comment
@tomazahlin

tomazahlin Jul 20, 2016

I tried all solutions, but nothing works. Great job, react native...

tomazahlin commented Jul 20, 2016

I tried all solutions, but nothing works. Great job, react native...

@uusa35

This comment has been minimized.

Show comment
Hide comment
@uusa35

uusa35 Jul 23, 2016

@trevorwang thank you so much it worked for me

uusa35 commented Jul 23, 2016

@trevorwang thank you so much it worked for me

@VitamintK

This comment has been minimized.

Show comment
Hide comment
@VitamintK

VitamintK Jul 24, 2016

My problem was also that I had something running on port 8081 (discovered by running sudo lsof -n -i4TCP:8081)

Fixed by using an older version of react-native by running react-native init --version 0.27 instead of react-native init to create the project.

Then, I changed the appdelegate.m file and the React.xcodeproj and the RCTWebSocketExecutor.m as detailed in the first step here.

Then, in the project folder, instead of react-native ios-run, I did npm start -- --port 5000, and then ran the project in Xcode with ⌘+R

My problem was also that I had something running on port 8081 (discovered by running sudo lsof -n -i4TCP:8081)

Fixed by using an older version of react-native by running react-native init --version 0.27 instead of react-native init to create the project.

Then, I changed the appdelegate.m file and the React.xcodeproj and the RCTWebSocketExecutor.m as detailed in the first step here.

Then, in the project folder, instead of react-native ios-run, I did npm start -- --port 5000, and then ran the project in Xcode with ⌘+R

@ryanmcgrath

This comment has been minimized.

Show comment
Hide comment
@ryanmcgrath

ryanmcgrath Jul 25, 2016

Mmmm, this issue is one of the top Google results for react-native apps not running in the simulator ("no devices are booted"). Since this seems to still be a lingering issue for people I'm dumping some info here - YMMV.

This used to happen to me when I did iOS work for a living; oftentimes the simulator is just wonky as hell. ps aux | grep Simulator will usually give me something to kill that should've died already. These steps usually work for me:

  1. Kill simulator/debug server.
  2. ps aux | grep Simulator or whatever your preferred shell magic is, see if anything is lingering around that didn't shut down correctly. If there's something, kill it.
  3. Re-run simulator/debug server/build process (react-native run-ios). If it still gives you a "no devices booted" error (and your simulator is a black screen), just reboot the simulator completely via Hardware -> Reboot, then open your app.

Unless you actually have something running on port 8081, you shouldn't need to change it - for some reason I see that as the most answered solution to this stuff around the web. These steps work for me pretty much every time.

Also, keep in mind if you change your NSAppTransportSecurity settings in your Info.plist, it can mess with this stuff.

ryanmcgrath commented Jul 25, 2016

Mmmm, this issue is one of the top Google results for react-native apps not running in the simulator ("no devices are booted"). Since this seems to still be a lingering issue for people I'm dumping some info here - YMMV.

This used to happen to me when I did iOS work for a living; oftentimes the simulator is just wonky as hell. ps aux | grep Simulator will usually give me something to kill that should've died already. These steps usually work for me:

  1. Kill simulator/debug server.
  2. ps aux | grep Simulator or whatever your preferred shell magic is, see if anything is lingering around that didn't shut down correctly. If there's something, kill it.
  3. Re-run simulator/debug server/build process (react-native run-ios). If it still gives you a "no devices booted" error (and your simulator is a black screen), just reboot the simulator completely via Hardware -> Reboot, then open your app.

Unless you actually have something running on port 8081, you shouldn't need to change it - for some reason I see that as the most answered solution to this stuff around the web. These steps work for me pretty much every time.

Also, keep in mind if you change your NSAppTransportSecurity settings in your Info.plist, it can mess with this stuff.

@Bintong

This comment has been minimized.

Show comment
Hide comment

Bintong commented Aug 2, 2016

@joshschumacher works for me too

facebook-github-bot added a commit that referenced this issue Feb 16, 2018

Change irrelevant Products path in ./local-cli/runIOS/runIOS.js
Summary:
#7308
and many of the same

Seems like xcode cli tool isn't create ./build directory any more but place Products
right inside ./Build (may check while creating single view ios application
in XCode)

* edit hardcoded path to {appName}.app

<!--
Thank you for sending the PR! We appreciate you spending the time to work on these changes.

Help us understand your motivation by explaining why you decided to make this change.

You can learn more about contributing to React Native here: http://facebook.github.io/react-native/docs/contributing.html

Happy contributing!

-->

Command `$ react-native run-ios` is often lead to `Entry, ":CFBundleIdentifier", Does Not Exist`
I find out how to fix it in current version of RN and Xcode cli tools

Just try to do `$ react native init {appName}` and then `$ react native run-ios` if everything fine it means my approach is right :)

<!--
Help reviewers and the release process by writing your own release notes

**INTERNAL and MINOR tagged notes will not be included in the next version's final release notes.**

  CATEGORY
[----------]        TYPE
[ CLI      ]   [-------------]      LOCATION
[ DOCS     ]   [ BREAKING    ]   [-------------]
[ GENERAL  ]   [ BUGFIX      ]   [-{Component}-]
[ INTERNAL ]   [ ENHANCEMENT ]   [ {File}      ]
[ IOS      ]   [ FEATURE     ]   [ {Directory} ]   |-----------|
[ ANDROID  ]   [ MINOR       ]   [ {Framework} ] - | {Message} |
[----------]   [-------------]   [-------------]   |-----------|

[CATEGORY] [TYPE] [LOCATION] - MESSAGE

 EXAMPLES:

 [IOS] [BREAKING] [FlatList] - Change a thing that breaks other things
 [ANDROID] [BUGFIX] [TextInput] - Did a thing to TextInput
 [CLI] [FEATURE] [local-cli/info/info.js] - CLI easier to do things with
 [DOCS] [BUGFIX] [GettingStarted.md] - Accidentally a thing/word
 [GENERAL] [ENHANCEMENT] [Yoga] - Added new yoga thing/position
 [INTERNAL] [FEATURE] [./scripts] - Added thing to script that nobody will see
-->
Closes #17963

Differential Revision: D7014984

Pulled By: hramos

fbshipit-source-id: da62f130e6ebf7d3acd09d36525838d5c9684e75

Plo4ox added a commit to Plo4ox/react-native that referenced this issue Feb 17, 2018

Change irrelevant Products path in ./local-cli/runIOS/runIOS.js
Summary:
facebook#7308
and many of the same

Seems like xcode cli tool isn't create ./build directory any more but place Products
right inside ./Build (may check while creating single view ios application
in XCode)

* edit hardcoded path to {appName}.app

<!--
Thank you for sending the PR! We appreciate you spending the time to work on these changes.

Help us understand your motivation by explaining why you decided to make this change.

You can learn more about contributing to React Native here: http://facebook.github.io/react-native/docs/contributing.html

Happy contributing!

-->

Command `$ react-native run-ios` is often lead to `Entry, ":CFBundleIdentifier", Does Not Exist`
I find out how to fix it in current version of RN and Xcode cli tools

Just try to do `$ react native init {appName}` and then `$ react native run-ios` if everything fine it means my approach is right :)

<!--
Help reviewers and the release process by writing your own release notes

**INTERNAL and MINOR tagged notes will not be included in the next version's final release notes.**

  CATEGORY
[----------]        TYPE
[ CLI      ]   [-------------]      LOCATION
[ DOCS     ]   [ BREAKING    ]   [-------------]
[ GENERAL  ]   [ BUGFIX      ]   [-{Component}-]
[ INTERNAL ]   [ ENHANCEMENT ]   [ {File}      ]
[ IOS      ]   [ FEATURE     ]   [ {Directory} ]   |-----------|
[ ANDROID  ]   [ MINOR       ]   [ {Framework} ] - | {Message} |
[----------]   [-------------]   [-------------]   |-----------|

[CATEGORY] [TYPE] [LOCATION] - MESSAGE

 EXAMPLES:

 [IOS] [BREAKING] [FlatList] - Change a thing that breaks other things
 [ANDROID] [BUGFIX] [TextInput] - Did a thing to TextInput
 [CLI] [FEATURE] [local-cli/info/info.js] - CLI easier to do things with
 [DOCS] [BUGFIX] [GettingStarted.md] - Accidentally a thing/word
 [GENERAL] [ENHANCEMENT] [Yoga] - Added new yoga thing/position
 [INTERNAL] [FEATURE] [./scripts] - Added thing to script that nobody will see
-->
Closes facebook#17963

Differential Revision: D7014984

Pulled By: hramos

fbshipit-source-id: da62f130e6ebf7d3acd09d36525838d5c9684e75
@MrIceman

This comment has been minimized.

Show comment
Hide comment
@MrIceman

MrIceman Mar 2, 2018

nothing works........ >=( Everything worked yesterdayf then I had trouble with that new fency Ionic Library I got recommended by React Native official guides. To get this installed I had to face 100 new errors, I endet up removing some stuff I am not sure what it was doing (thanks docs) and now nothing works anymore. I have been sitting on this issue now for the last few hours, it's 2:10 AM and I have to get up in 4 hours to drive to work but I can not sleep now because nothing works

MrIceman commented Mar 2, 2018

nothing works........ >=( Everything worked yesterdayf then I had trouble with that new fency Ionic Library I got recommended by React Native official guides. To get this installed I had to face 100 new errors, I endet up removing some stuff I am not sure what it was doing (thanks docs) and now nothing works anymore. I have been sitting on this issue now for the last few hours, it's 2:10 AM and I have to get up in 4 hours to drive to work but I can not sleep now because nothing works

@arapocket

This comment has been minimized.

Show comment
Hide comment
@arapocket

arapocket Mar 3, 2018

@MrIceman When I had this issue before I tried all of these solutions and nothing worked. I think what I did was I built a brand new project and installed every plugin one by one to determine which ones were giving me the error.

Well I just updated react-native-navigation and react-native-camera and I got the dirty error again, so look into those plugins.

@MrIceman When I had this issue before I tried all of these solutions and nothing worked. I think what I did was I built a brand new project and installed every plugin one by one to determine which ones were giving me the error.

Well I just updated react-native-navigation and react-native-camera and I got the dirty error again, so look into those plugins.

@LorandP

This comment has been minimized.

Show comment
Hide comment
@LorandP

LorandP Mar 3, 2018

If you have updated React-native, you have to also update yoga from pods.
This worked for me after updating RN to 0.54.0.
cd ios && pod update yoga

LorandP commented Mar 3, 2018

If you have updated React-native, you have to also update yoga from pods.
This worked for me after updating RN to 0.54.0.
cd ios && pod update yoga

@boyzhaotian

This comment has been minimized.

Show comment
Hide comment
@boyzhaotian

boyzhaotian Mar 8, 2018

it turns out to be 8081 was in use
nginx -s stop worked out for me.
Lol

it turns out to be 8081 was in use
nginx -s stop worked out for me.
Lol

@migueldoctor

This comment has been minimized.

Show comment
Hide comment
@migueldoctor

migueldoctor Mar 8, 2018

I have just faced the issue and I got it solved by removing and reinstalling react-native-cli

which react-native
rm -R /usr/local/bin/react-native
npm install -g react-native-cli
react native init myapp
cd myapp
react-native run-ios

I hope it helps

I have just faced the issue and I got it solved by removing and reinstalling react-native-cli

which react-native
rm -R /usr/local/bin/react-native
npm install -g react-native-cli
react native init myapp
cd myapp
react-native run-ios

I hope it helps

@syrakozz

This comment has been minimized.

Show comment
Hide comment
@syrakozz

syrakozz Mar 19, 2018

#7308 (comment) did finally work for me.

#7308 (comment) did finally work for me.

@smakosh

This comment has been minimized.

Show comment
Hide comment
@smakosh

smakosh Mar 22, 2018

Updating react using react-native upgrade and overwriting all iOS files is what worked for me!

smakosh commented Mar 22, 2018

Updating react using react-native upgrade and overwriting all iOS files is what worked for me!

@gugat

This comment has been minimized.

Show comment
Hide comment
@gugat

gugat Mar 27, 2018

It happened to me in iOS after I removed a package from package.json and executed npm install . To solve I had to install the package again. I guess I have to find the way to unlink it properly.

In Android I had no problem

gugat commented Mar 27, 2018

It happened to me in iOS after I removed a package from package.json and executed npm install . To solve I had to install the package again. I guess I have to find the way to unlink it properly.

In Android I had no problem

@mateoguzmana

This comment has been minimized.

Show comment
Hide comment
@mateoguzmana

mateoguzmana Apr 2, 2018

This works to me:

rm -rf ios/build/

Just remove the build folder and build the project again. Then, it works fine.

This works to me:

rm -rf ios/build/

Just remove the build folder and build the project again. Then, it works fine.

@alexyashin

This comment has been minimized.

Show comment
Hide comment
@alexyashin

alexyashin Apr 4, 2018

Downgrading from react-native v0.55 to v0.54 worked for me

Downgrading from react-native v0.55 to v0.54 worked for me

@rpmonteiro

This comment has been minimized.

Show comment
Hide comment
@rpmonteiro

rpmonteiro Apr 6, 2018

I had to downgrade allllll the way to v0.52.0. The only version that works for me

I had to downgrade allllll the way to v0.52.0. The only version that works for me

@mateoguzmana

This comment has been minimized.

Show comment
Hide comment
@mateoguzmana

mateoguzmana Apr 6, 2018

react-native v0.55.0 has a problem with this actually. Wait until the fix. #18681

mateoguzmana commented Apr 6, 2018

react-native v0.55.0 has a problem with this actually. Wait until the fix. #18681

@priteshpoddar

This comment has been minimized.

Show comment
Hide comment
@priteshpoddar

priteshpoddar Apr 9, 2018

I tried everything above but nothing worked.My xcode version was 8.3.2.So when I downgraded react-native to react-native v0.50.4 from 0.55.0, it worked.On another laptop I tried where xcode version was 9.3 and react-native v0.55.0 worked perfectly there.

priteshpoddar commented Apr 9, 2018

I tried everything above but nothing worked.My xcode version was 8.3.2.So when I downgraded react-native to react-native v0.50.4 from 0.55.0, it worked.On another laptop I tried where xcode version was 9.3 and react-native v0.55.0 worked perfectly there.

@AbdelMounhim

This comment has been minimized.

Show comment
Hide comment
@AbdelMounhim

AbdelMounhim Apr 9, 2018

same.
Xcode 8.2.1
node v9.3.0

last version of react-native failed to build (0.55.2, 0.55 , 0.54 )
but with react-native 0.53.0 it's ok :

react-native init MyApp --version "0.53.0"

AbdelMounhim commented Apr 9, 2018

same.
Xcode 8.2.1
node v9.3.0

last version of react-native failed to build (0.55.2, 0.55 , 0.54 )
but with react-native 0.53.0 it's ok :

react-native init MyApp --version "0.53.0"

@newzhongdan

This comment has been minimized.

Show comment
Hide comment
@newzhongdan

newzhongdan Apr 9, 2018

react native need specific the RN version: xcode version require, node version or something
for example: rn 0.54 need xcode >9.1 , node >6.5 and android sdk >24 (maybe others dependencies)

react native need specific the RN version: xcode version require, node version or something
for example: rn 0.54 need xcode >9.1 , node >6.5 and android sdk >24 (maybe others dependencies)

@AbdelMounhim

This comment has been minimized.

Show comment
Hide comment
@AbdelMounhim

AbdelMounhim Apr 10, 2018

i have migrated my macbook from captain to sierra.
On sierra, the last version xcode (9.3) can be installed.
and now react-native works.

i have migrated my macbook from captain to sierra.
On sierra, the last version xcode (9.3) can be installed.
and now react-native works.

@lindoelio

This comment has been minimized.

Show comment
Hide comment
@lindoelio

lindoelio Apr 11, 2018

Adding, it works for me, when nothing above fixes:

  1. Install react-native-git-upgrade and update your project. npm i -g react-native-git-upgrade && react-native-git-upgrade
  2. Open Xcode -> File -> Project settings -> Advanced.
  3. Select "Custom", then select "Relative to Workspace" and then click done, done.
  4. Update your CLI. npm i -g react-native-cli
  5. Update your Nodejs 8 and NPM. nvm install --lts and nvm install-latest-npm
  6. Remove ios/build and node_modules (in your project root path)
  7. Proceed again with npm install and react-native run-ios, and give me a hug :-)

It finally works here.

  • Mac OS High Sierra 10.13.4
  • Xcode 9.3
  • NPM 5.8.0
  • Node 8.11.1
  • RN 0.55.2

lindoelio commented Apr 11, 2018

Adding, it works for me, when nothing above fixes:

  1. Install react-native-git-upgrade and update your project. npm i -g react-native-git-upgrade && react-native-git-upgrade
  2. Open Xcode -> File -> Project settings -> Advanced.
  3. Select "Custom", then select "Relative to Workspace" and then click done, done.
  4. Update your CLI. npm i -g react-native-cli
  5. Update your Nodejs 8 and NPM. nvm install --lts and nvm install-latest-npm
  6. Remove ios/build and node_modules (in your project root path)
  7. Proceed again with npm install and react-native run-ios, and give me a hug :-)

It finally works here.

  • Mac OS High Sierra 10.13.4
  • Xcode 9.3
  • NPM 5.8.0
  • Node 8.11.1
  • RN 0.55.2
@raulghm

This comment has been minimized.

Show comment
Hide comment
@raulghm

raulghm Apr 16, 2018

  • Removing ios/ and android/ folders
  • yarn install
  • react-native eject

Solved my problem!

raulghm commented Apr 16, 2018

  • Removing ios/ and android/ folders
  • yarn install
  • react-native eject

Solved my problem!

@TwinkleTrivedi

This comment has been minimized.

Show comment
Hide comment
@TwinkleTrivedi

TwinkleTrivedi Apr 16, 2018

still issue with CfBundleIdentifier

Print: Entry, ":CFBundleIdentifier", Does Not Exist

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app3@0.1.0 ios: react-native run-ios
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app3@0.1.0 ios script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

still issue with CfBundleIdentifier

Print: Entry, ":CFBundleIdentifier", Does Not Exist

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app3@0.1.0 ios: react-native run-ios
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app3@0.1.0 ios script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

@redbluenat

This comment has been minimized.

Show comment
Hide comment
@redbluenat

redbluenat Apr 17, 2018

I had this problem in my VSC console and I did:
Go to File -> Project settings
Click the Advanced button
Select "Custom" and select "Relative to Workspace" in the pull down
click done, done
But error still was the same.
So I opened Xcode and tried to compile, I received an error with react-native-maps. I clicked auto fix and it resolves issue.

I hope it helps somebody :)

I had this problem in my VSC console and I did:
Go to File -> Project settings
Click the Advanced button
Select "Custom" and select "Relative to Workspace" in the pull down
click done, done
But error still was the same.
So I opened Xcode and tried to compile, I received an error with react-native-maps. I clicked auto fix and it resolves issue.

I hope it helps somebody :)

@brascene

This comment has been minimized.

Show comment
Hide comment
@brascene

brascene Apr 17, 2018

Switch from React Native to Swift xD

Switch from React Native to Swift xD

@matheusmonte

This comment has been minimized.

Show comment
Hide comment
@matheusmonte

matheusmonte Apr 18, 2018

just follow this link 👍

https://stackoverflow.com/questions/37461703/print-entry-cfbundleidentifier-does-not-exist

delete your ios/build folder and open Xcode and change build path after this, build again.

I hope help someone and avoid spend 2 hour trying to solve this

just follow this link 👍

https://stackoverflow.com/questions/37461703/print-entry-cfbundleidentifier-does-not-exist

delete your ios/build folder and open Xcode and change build path after this, build again.

I hope help someone and avoid spend 2 hour trying to solve this

@himanshusingh2407

This comment has been minimized.

Show comment
Hide comment
@himanshusingh2407

himanshusingh2407 Apr 22, 2018

Running react-native upgrade fixed the issue for me.

Running react-native upgrade fixed the issue for me.

@kaym0

This comment has been minimized.

Show comment
Hide comment
@kaym0

kaym0 Apr 22, 2018

What worked for me was going into my React-Native project directory (main directory) and deleting the ios directory. Then in terminal type react-native eject, which will then generate another ios folder. After that, it instantly worked for me. It's important to note that if you have anything important in the ios directory to save it, but anything that's automatically generated by ejecting will be recreated and in a way that actually works. I guess this method doesn't work for people using Expo, as ejecting means you can no longer use it. I did not have to delete android folder, but you can do that too as ejecting will generate bother ios and android folders (if and only if they are missing)

kaym0 commented Apr 22, 2018

What worked for me was going into my React-Native project directory (main directory) and deleting the ios directory. Then in terminal type react-native eject, which will then generate another ios folder. After that, it instantly worked for me. It's important to note that if you have anything important in the ios directory to save it, but anything that's automatically generated by ejecting will be recreated and in a way that actually works. I guess this method doesn't work for people using Expo, as ejecting means you can no longer use it. I did not have to delete android folder, but you can do that too as ejecting will generate bother ios and android folders (if and only if they are missing)

@ishigamii

This comment has been minimized.

Show comment
Hide comment
@ishigamii

ishigamii Apr 25, 2018

Running react-native upgrade and resetting all the file fixed it for me. I then used the git to put back all the changes that were needed and it was good to go :) Thanks to @consideRatio for the answer

Running react-native upgrade and resetting all the file fixed it for me. I then used the git to put back all the changes that were needed and it was good to go :) Thanks to @consideRatio for the answer

@midoalone

This comment has been minimized.

Show comment
Hide comment
@midoalone

midoalone May 1, 2018

Updating react using react-native upgrade worked for me

Updating react using react-native upgrade worked for me

@abdullahceylan

This comment has been minimized.

Show comment
Hide comment
@abdullahceylan

abdullahceylan May 1, 2018

It because of the react version. If you upgrade react too, then it will work without problem.

It because of the react version. If you upgrade react too, then it will work without problem.

@kranzky

This comment has been minimized.

Show comment
Hide comment
@kranzky

kranzky May 5, 2018

I fixed this by editing node_modules/react-native/local-cli/runIOS/runIOS.js to change the value returned by getBuildPath to Build/Products/${configuration}-${device}/${appName}.app (removing the initial build/

this reverts the fix in #18700

here's my setup:

Environment:
  OS: macOS High Sierra 10.13.4
  Node: 8.11.1
  Yarn: 1.6.0
  npm: 5.6.0
  Watchman: 4.7.0
  Xcode: Xcode 9.3 Build version 9E145
  Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
  react: 16.3.2 => 16.3.2
  react-native: 0.55.3 => 0.55.3

kranzky commented May 5, 2018

I fixed this by editing node_modules/react-native/local-cli/runIOS/runIOS.js to change the value returned by getBuildPath to Build/Products/${configuration}-${device}/${appName}.app (removing the initial build/

this reverts the fix in #18700

here's my setup:

Environment:
  OS: macOS High Sierra 10.13.4
  Node: 8.11.1
  Yarn: 1.6.0
  npm: 5.6.0
  Watchman: 4.7.0
  Xcode: Xcode 9.3 Build version 9E145
  Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
  react: 16.3.2 => 16.3.2
  react-native: 0.55.3 => 0.55.3
@kranzky

This comment has been minimized.

Show comment
Hide comment
@kranzky

kranzky May 5, 2018

Just to follow this one up, after discussing with the author of the fix in #18700, you need to make sure that the build location in Xcode preferences is set to "unique" (I had it set to something else, which broke things for me):

39661487-0680544e-5074-11e8-8c39-a30907e259eb

You then must set the build location in project settings to "Xcode default":

screen shot 2018-05-05 at 15 09 21

That fixed it for me, with the environment shown in the previous comment (React-Native 0.55.3, Xcode 9.3). No other jiggery-pokery was required; no deleting directories or running upgrade commands or anything else. Hope this helps somebody else.

kranzky commented May 5, 2018

Just to follow this one up, after discussing with the author of the fix in #18700, you need to make sure that the build location in Xcode preferences is set to "unique" (I had it set to something else, which broke things for me):

39661487-0680544e-5074-11e8-8c39-a30907e259eb

You then must set the build location in project settings to "Xcode default":

screen shot 2018-05-05 at 15 09 21

That fixed it for me, with the environment shown in the previous comment (React-Native 0.55.3, Xcode 9.3). No other jiggery-pokery was required; no deleting directories or running upgrade commands or anything else. Hope this helps somebody else.

@bozzmob

This comment has been minimized.

Show comment
Hide comment
@bozzmob

bozzmob May 6, 2018

Contributor

Created a NEW project.

  • Did rm -rf node_modules and rm -rf ios/build.
  • Done with changing paths like @kranzky said.
  • Done doing all crazy Project Settings n stuff on Xcode
  • Done with all the react-native upgrade and some react native git upgrade kinda thing as well, which react-native officially tells you to use.
  • Done with everything SO & GH issues asked me to do.
  • Now, not sure what else to do!

Still fails with the same error.

Tried everything! I never want to give up, but, this is so funny! Everyone comments IT WORKS. And nothing works for me :D #GLHF

react: 16.3.1
react-native-cli: 2.0.1
react-native: 0.55.3
Contributor

bozzmob commented May 6, 2018

Created a NEW project.

  • Did rm -rf node_modules and rm -rf ios/build.
  • Done with changing paths like @kranzky said.
  • Done doing all crazy Project Settings n stuff on Xcode
  • Done with all the react-native upgrade and some react native git upgrade kinda thing as well, which react-native officially tells you to use.
  • Done with everything SO & GH issues asked me to do.
  • Now, not sure what else to do!

Still fails with the same error.

Tried everything! I never want to give up, but, this is so funny! Everyone comments IT WORKS. And nothing works for me :D #GLHF

react: 16.3.1
react-native-cli: 2.0.1
react-native: 0.55.3
@brenmcnamara

This comment has been minimized.

Show comment
Hide comment
@brenmcnamara

brenmcnamara May 13, 2018

None of the above fixed it for me. I had to do the following:

  • Update operating system

  • Update XCode

  • Uninstall and reinstall homebrew

  • Uninstall and reinstall nvm

  • Get the latest version of node

  • Uninstall and reinstall yarn

  • Uninstall and reinstall react-native-cli

  • One or more of those updates ended up fixing the bug.

None of the above fixed it for me. I had to do the following:

  • Update operating system

  • Update XCode

  • Uninstall and reinstall homebrew

  • Uninstall and reinstall nvm

  • Get the latest version of node

  • Uninstall and reinstall yarn

  • Uninstall and reinstall react-native-cli

  • One or more of those updates ended up fixing the bug.

@daronwolff

This comment has been minimized.

Show comment
Hide comment
@daronwolff

daronwolff May 18, 2018

I have the same problem. The app does not work after execute npm run eject

react-native info
Scanning folders for symlinks in /Users/ksquarelabs/dev/courses/ghost/node_modules (14ms)

Environment:
  OS: macOS High Sierra 10.13.4
  Node: 6.9.1
  Yarn: 0.22.0
  npm: 3.10.8
  Watchman: Not Found
  Xcode: Xcode 9.3.1 Build version 9E501
  Android Studio: 2.3 AI-162.3764568

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: ~0.55.2 => 0.55.4

I have the same problem. The app does not work after execute npm run eject

react-native info
Scanning folders for symlinks in /Users/ksquarelabs/dev/courses/ghost/node_modules (14ms)

Environment:
  OS: macOS High Sierra 10.13.4
  Node: 6.9.1
  Yarn: 0.22.0
  npm: 3.10.8
  Watchman: Not Found
  Xcode: Xcode 9.3.1 Build version 9E501
  Android Studio: 2.3 AI-162.3764568

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: ~0.55.2 => 0.55.4
@auxilioivy

This comment has been minimized.

Show comment
Hide comment
@auxilioivy

auxilioivy May 22, 2018

So, I have the same problem and It works by issuing the command below:

cd ./ios/build
mkdir Build
cd Build

then, I symlink the folders:
ln -s ../Products .
ln -s ../Intermediates

and last react-native run-ios to work again
have a nice day :)

So, I have the same problem and It works by issuing the command below:

cd ./ios/build
mkdir Build
cd Build

then, I symlink the folders:
ln -s ../Products .
ln -s ../Intermediates

and last react-native run-ios to work again
have a nice day :)

@AlirezaAkbarix

This comment has been minimized.

Show comment
Hide comment
@AlirezaAkbarix

AlirezaAkbarix May 24, 2018

I had the same issue, in my case the length of fabric node_module dir was too long, so I pulled the repo in the root (~) dir and run it again and everything was OK :) I hope it helps you.

I had the same issue, in my case the length of fabric node_module dir was too long, so I pulled the repo in the root (~) dir and run it again and everything was OK :) I hope it helps you.

@aiavci

This comment has been minimized.

Show comment
Hide comment
@aiavci

aiavci May 24, 2018

Does anyone know the cause? I get this when I try to run the app in a custom directory e.g. react-native run-ios --project-path="../"

aiavci commented May 24, 2018

Does anyone know the cause? I get this when I try to run the app in a custom directory e.g. react-native run-ios --project-path="../"

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.