Playing your scene from within Unity (using the play button at the top) Visual Studio is now debugging your. By default, this list appears at top left of DDMS window. At this point you should be able to debug your game by: Opening Visual Studio from the Unity project (using Open C Project) Selecting the Attach to Unity debug button at the top of the window: Setting some breakpoints in the code. Select the process name of your widget from the list of processes shown. After this I've been able to keep the debugger attached, even if I attached it manually. You can either do this by pressing the DDMS labeled button on your top right corner or if you can’t find it, then do it by going to Window->Open Perspective->DDMS. Activating logcat and following error messages helped me track down and fix the likely cause. Solution to problem 2: Automatic process closures seemed to have been crashes caused by thrown exceptions (without any notification by OS). Is there any method that would allow uninterrupted widget debugging? Automatic debugger attachment would be a bonus. Problem 2: I found out I can attach debugger manually, with some patience, but widget process seems to stop on it's own and disconnect the debugger when it happens. Waiting for application to come online: com.example.|Ĭould not connect to remote process. Problem 1: When using "Debug app" option (with both physical devices and virtual), it will just go through series of: I'm using Android Studio 2.3.2 (latest) while attempting to make a widget and I've noticed debugger is close to impossible to attach.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |