react-native run-ios can not find any simulator #23282

eric-PearSports · 2019-02-03T21:32:54Z

Environment

React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 6.76 GB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
IDEs:
Android Studio: 3.1 AI-173.4819257
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.57.8 => 0.57.8
npmGlobalPackages:
create-react-native-app: 1.0.0
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7

Description

I have been facing an issue where 'react-native run-ios' can not start, regardless of the simulator I add to the --simulator argument.
XCode has the correct location for the 'command line tools'

I am always getting the error:
Could not find iPhone X simulator

Error: Could not find iPhone X simulator
    at resolve (/Users/eric/.../swim/node_modules/react-native/local-cli/runIOS/runIOS.js:149:13)
    at new Promise (<anonymous>)
    at runOnSimulator (/Users/eric/.../swim/node_modules/react-native/local-cli/runIOS/runIOS.js:134:10)
    at Object.runIOS [as func] (/Users/eric/.../swim/node_modules/react-native/local-cli/runIOS/runIOS.js:106:12)
    at Promise.resolve.then (/Users/eric/.../swim/node_modules/react-native/local-cli/cliEntry.js:117:22)

Reproducible Demo

Installed XCode from scratch.
Brand new 'react-native new app'

'react-native run-ios' always complain about not finding the simulator, regardless of the --simulator option.

My temporary fix is to change:
/node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js

line 42, to:
if (!version.startsWith('**com.apple.CoreSimulator.SimRuntime.**iOS') && !version.startsWith('tvOS')) {

The text was updated successfully, but these errors were encountered:

eric-PearSports · 2019-02-04T01:05:09Z

just tried a brand new project with:
react-native: 0.58.3 => 0.58.3

and same issue

kelset · 2019-02-05T04:16:44Z

Can you check which iOS simulator are installed on your machine?
You can always pass which simulator you want to target via the react-native run-ios —device=“XXXXXX’

osunnarvik · 2019-02-05T12:40:33Z

I have the same issue here as well.
When I changed to
if (!version.includes('iOS') && !version.includes('tvOS')) {
continue;
}

all is well, since the prefix "com.apple.CoreSimulator.SimRuntime." is included in the device-list, the pure check for startsWith fails for all simulators.

osunnarvik · 2019-02-05T13:06:34Z

I created pull request #23293 for this issue

kelset · 2019-02-05T14:25:25Z

Hey @osunnarvik thanks for creating the PR! Could you explain bit more (maybe in the PR) why is this happening now? I mean, when did the prefix changed? In latest Xcode? 🤔

osunnarvik · 2019-02-05T14:32:46Z

I have updated the description of the PR now to say a bit about when it startet happening and added some version information of XCode and xcrun

eric-PearSports · 2019-02-05T18:07:15Z

@kelset yes, I believe the format of the list of devices has changed with the latest XCode.

kelset · 2019-02-05T19:20:46Z

Awesome - thanks folks :)

We have already merged the PR to 0.58 (since 0.59 etc will have the CLI separated) and next patch release (0.58.4) will have the fix 💪

osunnarvik · 2019-02-05T19:44:51Z

@kelset I noticed the comment in react-native-community/cli#138 regarding when you specify the simulatorString (comment from @canterberry ). I only checked with empty simulatorString and not with one set. Let me know if you would like me to take a look at the case where the simulatorString is set.

kelset · 2019-02-05T20:23:25Z

Uhm oh yeah probably it would be better to have the check also when the string is set. 🤔

osunnarvik · 2019-02-05T20:52:58Z

ok, I will take a look tomorrow morning.

osunnarvik · 2019-02-06T06:36:22Z

I created #23305 to handle dotted input-versions for simulatorString

keshavkaul · 2019-03-22T17:19:36Z

@osunnarvik This issue is still present in react-native version 0.59.1

tedi · 2019-03-26T01:31:23Z

It's having issues doing the string search on the simulator version in node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js on this line: if (!version.startsWith('iOS').

I replaced it with includes as such: if (!version.includes('iOS') which seems to have solved the problem for me.

szm1002 · 2019-03-26T07:51:00Z

It's having issues doing the string search on the simulator version in node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js on this line: if (!version.startsWith('iOS').

I replaced it with includes as such: if (!version.includes('iOS') which seems to have solved the problem for me.

It works for me.Thanks.

dmateja724 · 2019-03-26T19:03:48Z

It's having issues doing the string search on the simulator version in node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js on this line: if (!version.startsWith('iOS').

I replaced it with includes as such: if (!version.includes('iOS') which seems to have solved the problem for me.

awesome thanks !!

YLD1 · 2019-03-27T07:37:04Z

It's having issues doing the string search on the simulator version in node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js on this line: if (!version.startsWith('iOS').

I replaced it with includes as such: if (!version.includes('iOS') which seems to have solved the problem for me.

I really can't comprehend how this situation even existed

evanoralph · 2019-03-27T12:24:51Z

are this fix with the new versions ?

buschco · 2019-03-27T13:13:10Z

@evanoralph If you got this issue today like me you can try to modify the findMatchingSimulator.js in node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js.
First boot a Simulator then run xcrun simctl list --json devices and search the one with "state" : "Booted",.
Then add at the top in the findMatchingSimulator function:

return {
    udid: <uuid from booted device>,
    name: <Name of the booted simulator>,
    booted: true,
    version: "com.apple.CoreSimulator.SimRuntime.iOS-12-2",
}

version might vary. But it is the parent key of the booted device object. But this is not a fix! It is a workaround.

sabun123 · 2019-03-27T14:25:05Z

It's having issues doing the string search on the simulator version in node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js on this line: if (!version.startsWith('iOS').

I replaced it with includes as such: if (!version.includes('iOS') which seems to have solved the problem for me.

Updated to macOS 10.14.4 and XCode updated to 10.2 and this issue started happening for me. Your solution has helped (even though this is only a temporary solution).

j133y · 2019-03-27T14:42:10Z

It's having issues doing the string search on the simulator version in node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js on this line: if (!version.startsWith('iOS').

I replaced it with includes as such: if (!version.includes('iOS') which seems to have solved the problem for me.

Awesome! Although temporary it's working perfectly. Thanks!

Subway19 · 2019-09-23T09:52:55Z

Getting this error on XCode 11. God bless software updates !!

maxkomarychev · 2019-09-23T10:55:37Z

you can update your @react-native-community/cli to 1.9.8 react-native-community/cli#414 (comment)

Subway19 · 2019-09-23T11:33:54Z

@maxkomarychev

react-native --version
react-native-cli: 2.0.1
react-native: 0.59.8

raldred · 2019-09-23T11:35:16Z

@maxkomarychev I'm using @react-native-community/cli@2.9.0 and having this issue.

Subway19 · 2019-09-23T13:32:40Z

@galkahana Thanks. That worked. But modifying node_modules are deadly hacks which should be avoided. Should raise a PR for that

heritiermwalila · 2019-09-23T13:48:12Z

Can you check which iOS simulator are installed on your machine?

You can always pass which simulator you want to target via the react-native run-ios —device=“XXXXXX’

just install iphone X device in xcode

dmurchie · 2019-09-23T20:50:01Z

Same error following a recent Xcode update which added new phone simulators AND removed some older ones:

Launch Simulator
From menus: Hardware > Device > Manage Devices
Choose "Simulators" tab/button, then click the "+" at the bottom left and add whatever device your run error is complaining about (take the defaults - i.e., don't fill in the name field).

Hope this helps someone...

danielcampo · 2019-09-23T21:02:45Z

If you're still experiencing the error after following @dmurchie's steps above, you may need to also update your @react-native-community/cli.

You can follow the steps here to do so:
https://github.com/react-native-community/cli#updating-the-cli

marcoantoni0 · 2019-09-24T18:57:22Z

Updated to xcode 11. couldn't find device.
problem is with interpreting the output of xcrun simctl list --json devices that's used by the script to find out installed devices.
Went into the code of findMatchingSimulator. in the condition stating
            if (
                simulator.availability !== '(available)' &&
                simulator.isAvailable !== 'YES'
            ) {
                continue
            }
added new form of isAvailable (Which is now a plain boolean):
            if (
                simulator.availability !== '(available)' &&
                simulator.isAvailable !== 'YES' &&
                simulator.isAvailable !== true
            ) {
                continue
            }
this sorted things out.

Awesome. This works like a charm. Thanks man

pqminh · 2019-09-25T02:55:38Z

@TchernyavskyDaniil You save my time. Tks so much!
RN 0.58.3
Xcode 11
Having this issue.
Fix this issue by follow below step:

From project open file:
code ./node_modules/react-native/local-cli/runIOS/findMatchingSimulator.js
replace
version.indexOf('iOS') !== 0
to
!version.includes('iOS')

replace
simulator.availability !== '(available)'
to
simulator.availability !== '(available)' &&
simulator.isAvailable !== 'YES' &&
simulator.isAvailable !== true
3. Run react-native run-ios
By default react native will run simulator iPhone 11 Pro Max.
See list current simulator:
xcrun simctl list devices
You can change simulator:
react-native run-ios --configuration Debug --simulator='Your simulator' --scheme 'Your Scheme'
Example
react-native run-ios --configuration Debug --simulator='iPhone 11 Pro Max' --scheme 'HelloWorld'

jamonholmgren · 2019-09-25T03:09:52Z

Another option that works for me.

# to find what simulators you have
xcrun simctl list

# to run a specific simulator
rn run-ios --simulator "iPhone 11"

KittiKing · 2019-09-25T07:34:42Z

Updated to xcode 11. couldn't find device.
problem is with interpreting the output of xcrun simctl list --json devices that's used by the script to find out installed devices.
Went into the code of findMatchingSimulator. in the condition stating
            if (
                simulator.availability !== '(available)' &&
                simulator.isAvailable !== 'YES'
            ) {
                continue
            }
added new form of isAvailable (Which is now a plain boolean):
            if (
                simulator.availability !== '(available)' &&
                simulator.isAvailable !== 'YES' &&
                simulator.isAvailable !== true
            ) {
                continue
            }
this sorted things out.

It's work for me.
Thanks man!

ilkinnamazov · 2019-09-25T20:22:41Z

Hi All,

I found other solution without changing any source code in node_modules directory.

Create react-native project folder (command: react-native init projectName)
Open file projectName/ios/projectName.xcodeproj file in Xcode 11
Choose device that you want to use (iPhone X not in list anymore after releasing iPhone Pro, so you need click on plus button and add to current list of devices)
When your new device in list you can close Xcode 11 and try to run emulator from Terminal (react-native run-ios)

if you need any screenshots how to do that just let me know.

This is my first comment in github by the way so congrats me :)

Thank you.

S-Cardenas · 2019-10-01T22:35:01Z

@ilkinnamazov Could you send screenshots of your solution please?

ilkinnamazov · 2019-10-02T19:53:06Z

When you open .xcodeproj file in ios folder it will start Xcode IDE and there you will be able to choose particular simulator.
See screenshots below.

You can choose device from this list.

But if you do not see iPhone X you can easily add it to your list of devices.

If you have any questions let me know.
Thanks.

marcosalberto · 2019-10-03T00:51:08Z

If doesn't work after add iPhone X simulator in XCode

Delete node_modules
Delete yarn.lock or package-lock.json
Run yarn or npm install

lucianomlima · 2019-10-04T05:51:58Z

If doesn't work after add iPhone X simulator in XCode

Delete node_modules

Delete yarn.lock or package-lock.json

Run yarn or npm install

Delete lock files may be problematic under certain circumstances. Do it carefully

avtarnanrey · 2019-10-13T01:47:21Z

If you just want to run any specific device. It might be missing in Simulators list. To add a device do the following steps:

Open Xcode
Press Command+Shift+2 it will open Devices & Simulators option.
Go to Simulators tab and press + icon on the left bottom and add iPhone X or any missing device you want.

nanadjei · 2019-10-19T22:42:55Z

Please kindly try this solution. It might work for you.

#24450 (comment)

robincsamuel · 2019-10-26T05:31:24Z

I found this the simplest,

react-native run-ios --simulator "iPhone 11 Pro Max"

jamonholmgren · 2019-11-05T03:12:45Z

This doesn't seem to be a problem anymore for me. Maybe some update in the meantime fixed it?

njt1982 · 2019-11-22T11:48:28Z

@danielcampo 's suggestion of upgrading the CLI fixed it for me.

I had to add this to my package.json:
"@react-native-community/cli": "@^1.12.0", as, for some reason, the lock wouldn't upgrade paste 1.11.2 without it.

Now it finds simulators without problem.

prescindivel · 2019-11-28T19:49:24Z

Updated to xcode 11. couldn't find device.
problem is with interpreting the output of xcrun simctl list --json devices that's used by the script to find out installed devices.
Went into the code of findMatchingSimulator. in the condition stating
            if (
                simulator.availability !== '(available)' &&
                simulator.isAvailable !== 'YES'
            ) {
                continue
            }
added new form of isAvailable (Which is now a plain boolean):
            if (
                simulator.availability !== '(available)' &&
                simulator.isAvailable !== 'YES' &&
                simulator.isAvailable !== true
            ) {
                continue
            }
this sorted things out.

This worked to me! Thanks guy!

Ref: facebook/react-native#23282 (comment)

McMainsLiam · 2020-01-09T21:21:36Z

If someone is still looking for the findMatchingSimulator.js file to manually edit it, you can currently find it at this path:
node_modules/@react-native-community/cli/build/commands/runIOS/findMatchingSimulator.js

I hope this helps someone down the line!

kelvinlemus · 2020-01-26T16:22:19Z

Also remember to pass IOS version within parenthesis:

--simulator "iPhone 11 Pro Max (13.2)"

anastely · 2020-02-10T08:46:04Z

@kelvinlemus I have

react-native-cli: 2.0.1
react-native: 0.61.5

And i want to change default simulator "iPhone X"
I'm trying to run react-native run-ios --simulator='iPhone XR' Or Others
but in every time just iPhone X launched

eric-PearSports added the Bug Report label Feb 3, 2019

react-native-bot added the Platform: iOS iOS applications. label Feb 3, 2019

This comment has been minimized.

Sign in to view

react-native-bot added the Resolution: Old Version label Feb 3, 2019

hramos removed the Resolution: Old Version label Feb 4, 2019

react-native-bot added the Bug Report label Feb 5, 2019

hramos removed the Bug Report label Feb 6, 2019

cpojer mentioned this issue Mar 19, 2019

RN Issue Triage Group 1 #24028

Closed

Titozzz closed this as completed Mar 19, 2019

SounD120 mentioned this issue Nov 7, 2019

Could not debug - error code 604 microsoft/vscode-react-native#1150

Closed

grahammcculloch added a commit to appdevdesigns/adroit-mobile that referenced this issue Dec 2, 2019

Attempt to fix issue with simulator not being found

620de44

Ref: facebook/react-native#23282 (comment)

facebook locked as resolved and limited conversation to collaborators Mar 19, 2020

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Mar 19, 2020

react-native run-ios can not find any simulator #23282

react-native run-ios can not find any simulator #23282

Comments

eric-PearSports commented Feb 3, 2019

Environment

Description

Reproducible Demo

This comment has been minimized.

eric-PearSports commented Feb 4, 2019

kelset commented Feb 5, 2019

osunnarvik commented Feb 5, 2019

osunnarvik commented Feb 5, 2019

kelset commented Feb 5, 2019

osunnarvik commented Feb 5, 2019

eric-PearSports commented Feb 5, 2019

kelset commented Feb 5, 2019

osunnarvik commented Feb 5, 2019

kelset commented Feb 5, 2019

osunnarvik commented Feb 5, 2019

osunnarvik commented Feb 6, 2019

keshavkaul commented Mar 22, 2019

tedi commented Mar 26, 2019

szm1002 commented Mar 26, 2019

dmateja724 commented Mar 26, 2019

YLD1 commented Mar 27, 2019

evanoralph commented Mar 27, 2019

buschco commented Mar 27, 2019 • edited

sabun123 commented Mar 27, 2019 • edited

j133y commented Mar 27, 2019

Subway19 commented Sep 23, 2019

maxkomarychev commented Sep 23, 2019

Subway19 commented Sep 23, 2019

raldred commented Sep 23, 2019

Subway19 commented Sep 23, 2019

heritiermwalila commented Sep 23, 2019

dmurchie commented Sep 23, 2019

danielcampo commented Sep 23, 2019

marcoantoni0 commented Sep 24, 2019

pqminh commented Sep 25, 2019

jamonholmgren commented Sep 25, 2019

KittiKing commented Sep 25, 2019

ilkinnamazov commented Sep 25, 2019 • edited

S-Cardenas commented Oct 1, 2019

ilkinnamazov commented Oct 2, 2019

marcosalberto commented Oct 3, 2019

lucianomlima commented Oct 4, 2019

avtarnanrey commented Oct 13, 2019

nanadjei commented Oct 19, 2019

robincsamuel commented Oct 26, 2019 • edited

jamonholmgren commented Nov 5, 2019

njt1982 commented Nov 22, 2019 • edited

prescindivel commented Nov 28, 2019

McMainsLiam commented Jan 9, 2020

kelvinlemus commented Jan 26, 2020

anastely commented Feb 10, 2020

buschco commented Mar 27, 2019 •

edited

sabun123 commented Mar 27, 2019 •

edited

ilkinnamazov commented Sep 25, 2019 •

edited

robincsamuel commented Oct 26, 2019 •

edited

njt1982 commented Nov 22, 2019 •

edited