-
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
Detox device/element is not defined #911
Comments
Someone can help us ? |
got the same problem ! |
I, too, am experiencing this issue. |
@GuillaumeSarfati @Tchangang If either of you figure this out could you please create a demo project? I will do the same if I figure it out 😄 |
Happened to me after upgrading to babel 7 and newest RN. Fix for me was to kill all simulators and do a project clean in iOS. Once the simulator works again, then the detox tests will work as well. Also needed the babel 7 core package ("babel-core": "7.0.0-bridge.0",) . https://jestjs.io/docs/en/getting-started.html#using-babel |
@benburton I have already link the demo project, it is here https://github.com/GuillaumeSarfati/detox-expo-issue ;) |
@GuillaumeSafrati, I don't see any Expo specific integration code for Detox in your repo. Correct me if I am wrong. AFAIR, it does not work out of the box and somebody in the previous issues published their workaround wrapper for Expo. It is said to be not officially supported, but you can try. |
@noomorph Can you point me in the direction of the workaround wrapper? All I really want is to see a working example of latest Expo+Detox, and it's really frustrating that one doesn't exist. |
@noomorph this is an example of "detached" Expo App ( like an app without expo) , I tried to use expo-detox-helpers no more results |
@GuillaumeSarfati me too |
I'll do my best to look into this on the next week. |
is there a workaround to make this work first like degrading some dependencies? |
I have this issue with Xcode 10. |
Yes, there is an issue with Xcode 10 install wrapper AFAIK. I'm aware and
this is in the nearest plan's to fix.
בתאריך יום ד׳, 26 בספט׳ 2018, 10:35, מאת yannDuval <
notifications@github.com>:
… I have this issue with Xcode *10*.
Rolling back to version *9.4.1* seems to be enough for me.
By the way, with Xcode *10*, my first test file runs *OK*, it's my second
test file which triggers the *ReferenceError: device is not defined* .
Good luck for the fix.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#911 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AB3x5Twb9RvOz-ko8rxLwD_MGiLq5p_5ks5uey5HgaJpZM4WTGi4>
.
|
Hi, Is there any solution for this? I am using xcode 9.4 and facing the same problem. The thing is, I tried their app from here: https://github.com/wix/Detox/tree/master/examples/demo-react-native-jest, upgraded to react-native 0.52.0 (the same as I use in my app and it runs with their example) and it works. Then I try with our app, which has the same version of dependencies (rn 0.52.0, detox 9.0) and it does not work. Is maybe problem react-navigation or some other dependencies in package.json? The difference is, I created my app with Expo and then ejected it. Maybe that should be problem? |
Our package.json: { |
got the same problem on Xcode 9.4.1. Is there a plan to fix it? |
For me upgrading my |
It seems like there are too many different issues here, and it will be impossible to address them all at the same time, so I will close this issue now, but try to answer as generally as I can, and if there are still individual issues please open new ones. Sync IssuesThere are only two known ways Detox can reach the test runner's timeout,
Jest:
|
Hello Team :)
Description
My app work fine, but an error appear and say element/device is not defined
i found many issues :
DETOX_INIT_ERROR isn't throw
Steps to Reproduce
See the repository clone and read to reproduce :)
https://github.com/GuillaumeSarfati/detox-expo-issue
Detox, Node, Device, Xcode and macOS Versions
Device and verbose Detox logs
The text was updated successfully, but these errors were encountered: