@Tomas1856
Hi Tomas,
Do you know what is happening here? I am testing on Mumu Player android emulator and I cannot see the messages.
The terminal shows them and can see them fine in Android Studio.
What if you do adb logcat from terminal?
You can see the terminal output in the second image
Oh sorry, hmph, in logcat window in top right corner under three dots, there internal log, locate adb logcat command there, and try executing the same command in terminal.
It’s kind a hard to say what’s wrong, it feels like log message parsing fails.
I used that way of calling the adb as I read it on your other thread. The image if from the built in terminal.
To avoid confusion what exactly the command line you’ve used?
adb logcat -s Unity
That’s not the command logcat window is using. Like mentioned above, check Internal Log to see how command is executed
There are 4/5 adb commands, which one should I check?
This one return the above “adb.exe -s 127.0.0.1:7555 logcat --pid=4032 -v year *:V”
Then it should work… P.S in your screenshot above you’re filtering by launcher app, I assume you don’t see anything if filtering by Unity app too?
Same if I chose the app. The log messages are read fine, because it can see the timestamp, tag,etc. Only the message itself is not parsed, like it there is some character screwing the parser. In some occasions I see some messages but they are like preceded by like 200 spaces, have to scroll to the right to see it.
can you do
adb.exe -s 127.0.0.1:7555 logcat -v year *:V > C:\temp\test.txt
and attach test.txt here ?
Sure, the problem is now it stopped doing it…
I just thought, I have some custom server side stuff which reply with a JSON which I output on the console for debugging purpose. Could it be some character screwing things up?
Anyway when it will restart doing it I will send the log.
1 Like