but still, I have no clue how to do it, and what to do…
people are writing their comments as if it is obvious how to use these commands, but nothing work for me cause I can’t find a proper tutorial for new comers.
I really need a step by step guide, I would highly appreciate it, thanks.
If you’re using Unity with android, you must have already installed adb through Android SDK. Given that, yeah, it should be simple and obvious. And Ben is right. You didn’t seem to google enough or take any effort here… But I just hate simple unanswered questions.
So, quoting updated parts from Herman, there are just a couple things to assure:
Make sure USB debugging is enabled on the Android device (check under Settings → Development).
Run adb through the command prompt (with command line argument logcat) that comes with the Android SDK while running the game on the Android, still connected via USB to the computer.
And then, quoting eriQue, here’s a good command line to filter out stuff:
Finally, if the Android Debug Bridge can’t help you, I’m not sure what could. There was this one time, actually, it couldn’t help me… But I was ignoring a unity warning, so I did the debugging checklist in the wrong order.
Simple,
You don’t need to do nothing (if you use studio), just open the logcat console and see the Unity debug prints there, you can also add a Unity tag to make it more readable.
You will see all your Debug.Log prints.
I had a problem where the debugger was showing no output. I am running OSX Mojave on a 2017 Macbook Pro (The horrible keyboard/touchbar/usb-c one). In order to get the logger working for me, I had to:
Run adb shell
Run adb logcat -s Unity ActivityManager PackageManager dalvikvm DEBUG from within the shell.
Then everything started working as expected, but this SHOULD NOT have to happen, so there’s some sort of underlying bug at play here, that I’m sure won’t get fixed because I believe it’s on Apple’s side.