-
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
DetoxRuntimeError: Detox worker instance has not been installed in this context (DetoxPrimaryContext). #4362
Comments
Logs? |
What's in your e2e/jest.config.js? |
|
And if you append --showConfig to your |
|
This issue seems to have a dramatically wrong description. From your logs (which you have deleted), I can see that your app is busy and Detox can't wait long until it finishes its activities. We write some basic information about it here: It can be due to Sentry/Firebase/whatever instrumenting and logging like here: It can be due to animation Try to analyze your app with Flipper, record CPU and React rendering activity, and maybe you'll find something. I can't help further than that. |
@noomorph my workaround is to disable detox tests while running jest, and run after jest is completed. |
See Jest config.
https://jestjs.io/docs/configuration#testpathignorepatterns-arraystring
https://jestjs.io/docs/configuration#testmatch-arraystring
Thank you for telling why you need this. We will add that notice to the
docs!
BOTTOM LINE: You don't need the workaround, you just need a proper config for your non-Detox tests.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
What happened?
When I run "yarn jest" I got this error. That's weird because when I run "detox test" works like a charm.
Error:
When I run the detox test
What was the expected behaviour?
Run all the tests without errors.
Was it tested on latest Detox?
Help us reproduce this issue!
As I said, I just run the tests and it happens.
In what environment did this happen?
Detox version: ^20.17.1
React Native version: 0.67.5
Has Fabric (React Native's new rendering system) enabled: not sure.
Node version: 16.14.0
Test-runner (select one): jest / other
Detox logs
No response
Device logs
No response
More data, please!
No response
The text was updated successfully, but these errors were encountered: