Detox hangs on device.init() for IOS tests

[brad-miller1]

No description provided.

[rotemmiz]

Simulator log
Log with debug sync

[rotemmiz]

Log with debug sync is still missing

[rotemmiz]

Why did you delete all comments? 😐
What was your solution?

[brad-miller1]

It is still not resolved, but I closed because my company would prefer I not post the logs. Thanks

[rotemmiz]

🙁

[thymikee]

@rotemmiz I face similar issue in a RN v0.55 project on iOS simulator (any kind).

In debug, most of the time detox.init() hangs (the isReady message doesn't get a response from WS server, to be specific). However, if I re-start packager, the init somehow succeeds, just to not being responsive when awaiting an element by.id() for example.
In release it doesn't ever get past init.

However, if I bootstrap the app with a different view (more heavily packed with requests to server) it gets the ready message back and seems to work most of the time.

Sadly I cannot post a repro now, because it's a disclosed project.

Any ideas why this might happen? Tried on Node 10.5, 10.6, 8.11, 8.7, [email protected] and [email protected].

[thymikee]

Turned out it was hanging because of infinite animation I had on a screen.

[brad-miller1]

If this might help anyone, it turns out Cylance (
anti-virus) was blocking the app from connecting in my case.

[noomorph]

@brad-miller1 , any ideas on how to detect such cases? Could you describe how did you come to this conclusion and what can be a symptom for this? I'd like to add some helper code that will detect this kind of issue to prevent similar bug reports in future.

[brad-miller1]

I ended up finding it in my system logs, I have to leave out some of the details, but the log message was something like this:

Jul 10 00:45:50 ******* CylanceSvc[91]: process Blocked by policy - path:/Users/********** pid:12880 violation:DyldInjection occurrences:1 SHA:*********

[noomorph]

@brad-miller1 , did you check what operation got enabled after you "lifted the ban"? Was it opening detox-server on a specifc port, or detox-server to simulator communication? I'd be happy to hear any extra input, since it maybe helpful to the other users.

[noomorph]

I mean it could be cool to add a stricter error handler which will throw a fatal exception instead of hanging up. :)

[brad-miller1]

Basically it was not allowing the app to connect to the detox server, it was not able to connect and therefore could not send the response that the app was ready

[noomorph]

@brad-miller1 , thank you very much!!! 👍
I'll find some time to investigate this.

[brad-miller1]

Your welcome! It would be great if it could somehow log this type of error so it would be easier to debug! Let me know if I can provide any other info, thanks!