-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SimulatorDriver] semantics of device.name has been unexpectedly changed since 7.4.0 #853
Comments
It appears the semantics of the The reason that it is very important to us to be able to select a specific simulator for the UI tests, is because the UI test simulator has configurations that are not ergonomic for normal development use simulator; eg no hardward keyboard. output of
output of
If this was the intended behaviour before 8.0.0 and the functionality we rely on was a bug to begin with, can you let us know how we could specify a specific simulator using the configuration? |
It does look like a not documented breaking change, but not sure yet. I'll advise with @rotemmiz on this. |
This is not good and must be resolved. There is no reason to break this. |
@LeoNatan, I agree and I'll speak to Rotem at the first opportunity. |
Yeah, this also broke our hand-rolled parallelization of Detox tests we are using on pre-8.0 versions. We are using xcrun to script creation of 'n' simulator devices with unique names (but same underlying device type and iOS version) and using gulp to split our tests to run against them, then using an env var to tell Detox which simulator instance to use for each batch. Detox 8 seems to have broken this; I believe because the semantics of It feels to me that the new behaviour is designed around the assumption your Simulators are using "standard" names, like out-of-the-box simulators. Unfortunately this change in semantics is preventing an incremental upgrade and conversion of our hand-rolled parallelization support to use Detox's inbuilt support :( |
There is an open issue from 8.0.0 and upward: wix/Detox#853 (comment)
is it still planned to be fixed? The pull request seems to be ready but it is not yet merged. |
The same error happens when I try to run the react-native ios example. How can detox be used until the PR is merged? Older versions fail with the post install script. |
Similar issue happened to me. I tried to create a dedicated simulator for my e2e test on CI using The entry in my package.json looks like this:
But detox can't find the device:
even though applesimutils finds it:
Env
|
What's the workaround for this? We're trying to add E2E testing with Detox, but not being able to specify a device name is pretty much a blocker for us. |
@SEAPUNK, planned for June, as far as I am concerned. |
FYI I believe that the code in #1404 fixes this (although it raises question on the parameter name) |
Description
After upgrading to Detox 8.0.0 from 7.3.3, detox is not able to find the same iOS simulator using the name of the simulator. After downgrading, it works again, with no changes to the simulator config in between.
Output of
xcrun simctl list
Steps to Reproduce
7.3.3
Detox, Node, Device, Xcode and macOS Versions
Device and verbose Detox logs
The text was updated successfully, but these errors were encountered: