-
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
error in clearDeviceRegistryLockFile() when running detox test #771
Comments
If nobody takes this issue, I can try to reproduce after June 10th, after I return from vacation. Or maybe @simonbuchan might want to take a look? |
Hmm, I migrated up to 7.4.0 without trouble. Looks like it just hasn't created the data directory, so if that got broken, shouldn't be too hard to track down (and maybe isn't even windows?) |
That was the essence of my inquiry. Thanks much, Simon! |
Thanks for the replies! |
This is an actual issue. We need to ensure the directory will be created if doesn't exist |
Fixed in #781 |
For usage help, ask a question on Stack Overflow with the
detox
tag. The issues section of the project is meant for opening bug reports and enhancement requests of Detox. We use it to automatically track the change logIMPORTANT: Use search before opening an issue. Duplicate issues will simply be closed.
Description
Since detox 7.4.0 I cannot start detox test. It fails on clearDeviceRegistryLockFile that was added in #609.
I'm using windows.
$ detox test -c android.emu.release --loglevel verbose
fs.js:646
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^
Error: ENOENT: no such file or directory, open 'C:\Users\stina\AppData\Local\data\Detox\device.registry.state.lock'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.writeFileSync (fs.js:1299:33)
at clearDeviceRegistryLockFile (C:\Users\stina\code\App\powerup\node_modules\detox\local-cli\detox-test.js:171:6)
detox 7.3.7 works fine (with some minor manual changes )
Detox, Node, Device, Xcode and macOS Versions
The text was updated successfully, but these errors were encountered: