-
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 failed to start testing in my react native project #548
Comments
Hi, Thanks for reporting. Thanks |
All, did you fixed this issue because i have the same issue in my project:
|
@paulvelzeboer Were you able to fix this? Same issue for me |
@BenBach nope still same issue... hopefully someone has a solution? |
@paulvelzeboer In #645, I asked for an example project reproducing the issue with TrustKit. Please provide that so I can take a look. |
Hey @BenBach & @paulvelzeboer Could you create a demo project, so that we can reproduce and find the bug? It would be cool if it would be something like the smallest project possible that shows this error 👍 Thank you for helping us :) |
Ah @LeoNatan two idiots one idea ✋ 🤣 |
Please don’t reopen old issues. Once the demo project exists, open a new issue. |
@DanielMSchmidt Hehe. I asked for a demo project twice, but I was never provided with one. |
I wanted to provide one but I don't know how as I'm not an iOS developer... I'll try to do it next week. |
I meant a React Native demo project. Please open a new issue with the project. |
Same here i know you need a project and will discus with our developers if they can create a demo project (project we are working on now i cannot share) and will send it to you, if there is an issue already open than i can add mine or if im the first one open a new issue |
Great, thanks |
I'm using react native 0.52.0 and detox 7.0.1. I got the error messages as below, and I cannot find a similar issue.
The build built by detox can be opened without crash when I directly open it in the simulator, just crashed when I run detox test
The text was updated successfully, but these errors were encountered: