

If you want to be sure, you can verify it by Settings -> System -> About Phone -> Status -> Serial number.If everything goes smoothly, you should see a message like “List of devices attached \n device”.If you did not allow USB debugging before, the phone will ask you for your permission.


Change location where you extracted ADB:.Extract the content (I extract it to C:\ADB).Download the latest platform tools for Windows from Android.So, I suggest you to start by downloading and extracting ADB somewhere reasonable, such as C:\ADB You most likely don’t have ADB in your system. You do not need to keep USB debugging and ADB debuggins options active all the time, but do not forget to activate them before you start debugging, unless you want to get angry in front of your devices and keep screaming “Why the you don’t work?!”. Find allow ADB debugging in charge only mode (or something like that) and activate it.Find USB debugging option and activate it.Go to Developer Options (Settings -> System -> Developer Options).It will either directly activate Developer Mode (and inform you with a toast message) or you will see a pop-up for a confirmationĪfter you activate Developer Mode, you also need to allow USB and ADB debugging.Start tapping on Build Number (Some legends say that you should tap 7 times).

Go to Settings -> System -> About Phone.But, as long as, you have a Windows machine and Visual Studio, I don’t expect any problems.īefore we start, you should be sure that you activated Developer Mode on your phone: So, I wrote the steps according to these components. I use Unity 2018.3 on a Windows 10 machine and Visual Studio 2017. Here, I will focus on Unity running on Windows machines and using Visual Studio as the IDE(?). So, I blended the steps I found on the Internet with my own experience and wrote this article for the future reference and fellow sufferers. However, using ADB wasn’t straightforward too, and the steps making it work were spread around the Internet. Unfortunately, Unity still () cannot provide a straight forward debugging tools for such situations, but my Google search provided me a tool called ADB (Android Debug Bridge). So, we needed to debug the project line by line, while it runs on the device. Recently, we faced with a really weird bug only happening on Android devices, and couldn’t find any real reason for it. Unity keeps improving its debugging tools, but the things still can get very painful, especially for Android development when it comes to debugging.
