Redirect simulator stdout to runner stdout in --verbose mode.

[DanielZlotin]

Logging should be printed to the console or at the very least to some log file

[LeoNatan]

Which logging do you mean? Simulator output? NSLog from inside the app?

[DanielZlotin]

Let's start with all stdio. Just dump it somewhere for starters.

[DanielZlotin]

I'm guessing we don't have logs from react because of #73 , but what about crash logs? I think even in release it should print something...

[LeoNatan]

What does "somewhere" mean? Where did you use to get it until now?
Building React in release could be the reason console.log are not printed in stdout, however NSLog should work normally.

[DanielZlotin]

Well we can send logs to the detox server and print it out to console/file if we have a --verbose flag for example...

[LeoNatan]

Right now, --verbose is for a different purpose. I don't think it has ever been used to route simulator stdout, but I could be wrong. In the past, where did you see the stdout output?

[DanielZlotin]

don't know

[talkol]

this was working

we had to implement it to debug issues with detox on One App in the CI in detox version 3.x

when the tests were failing or the app was crashing we added the output of the simulator to detox so it will appear in the build log and we could debug what went wrong inside the app

[LeoNatan]

Where was the output redirected to?

[LeoNatan]

stdout of fbsimctl?

[talkol]

this was a very long time ago so I don't fully remember, but pretty sure this was the commit:

a02ea22

[LeoNatan]

Interesting. There haven't been made changes to simulator.js for those flows, so they could be broken due to extraneous factors. Detox 3.x has not been tested on modern development environment (Xcode 8, Sierra).

[LeoNatan]

@rotemmiz I think we can close this, right? The tail command can be routed to Detox output or to some file in output dir?