Bring back printing of device logs location

[Niryo]

Description

In previous versions of detox, on every successful installation on the device, detox was printing the location of the device's log (line 10):

On the newer version of Detox, we cannot see the location of the device log unless we turn on loglevel verbose or loglevel trace, but then the logs contain too much information for day to day usage:

Please bring back the logs to the standard loglevel, it was very useful and made life easier.
Thanks!

[noomorph]

What do you think if you could have used Detox log artifacts? Or there's something unusable in your case about it?

[Niryo]

can you explain?

[noomorph]

I mean this feature: https://github.com/wix/detox/blob/master/docs/APIRef.Artifacts.md

[Niryo]

Without going deeply into that solution, I think it's an overkill for what I am asking for. I just want the path to the device logs so I could read them in my terminal. It was a very convenient feature of old detox versions- just copy the path, paste it in the terminal and see the logs. no boilerplate.

[noomorph]

Okay, I see.

@rotemmiz, in general, do you mind if we return the former behavior back where it was?

[rotemmiz]

We should probably stop using that and start using xcrun simctl spawn booted log stream --level=info --predicate {somePredicate} instead

[rotemmiz]

But to answer your question, sure, why not.

[LeoNatan]

We should be using the new log system.

[LeoNatan]

And so can @Niryo to get his log

[rotemmiz]

@LeoNatan what do you mean? xcrun simctl spawn {deviceudid} log ?

[LeoNatan]

Yes. In the case @Niryo, he can limit his log output using that command to only his app, which is preferable for him.

In the case of Detox, we shouldn't use any predicate but collect everything.

[Niryo]

the problem is not limiting the log output, but locating the device logs. look at the first picture, back at the good old days, detox was printing the location of the device logs and it was very convenient.
But maybe I got your answer wrong.

[LeoNatan]

You are missing the point. You don't need to locate anything. Using the new log command, you can get the output of your app's log to just stream in your terminal.

[LeoNatan]

@Niryo Read here: https://www.iosdev.recipes/simulator/os_log/

[Niryo]

@noomorph hi, this issue has been fixed in detox 13, but now it looks like the logs are gone again (in 14)

[LeoNatan]

What do you mean @Niryo ? The command to print logs is no longer printed?

[LeoNatan]

Please don't reopen old issues. Open a new one and provide a description of the problem as it exists today. Thanks