search

damirarh / damirscorner-utterances

utteranc.es comments for https://damirscorner.com
0 stars 0 forks source link

/blog/posts/20170113-DebugIonic2AppsInVsEmulatorForAndroid.html #42

Open damirarh opened 1 year ago

damirarh commented 1 year ago

Imported

URL: https://www.damirscorner.com/blog/posts/20170113-DebugIonic2AppsInVsEmulatorForAndroid.html

damirarh commented 1 year ago

Imported comment written by sanme98 on 2017-11-09T06:45:33

I used the same launch.js as per above, but I can't attach to the android emulator. It show nothing and no error message. Any input?

damirarh commented 1 year ago

Imported comment written by Damir Arh on 2017-11-09T21:18:38

Since I wrote the blogpost, I've switched from VS Android emulator to Google Android emulator, but I'm guessing you might be encountering the same issue that I have when a breaking change was introduced in version 1.2.12 of Cordova Tools Extension - when "target" is set to "device", the debugger won't attach to an emulator any more. Now, "target" must be set to "emulator". You can check my GitHub issue for more information.

damirarh commented 1 year ago

Imported comment written by sanme98 on 2017-11-10T03:20:53

Thanks for your reply.

I have changed it to emulator, but the debugger seem never able to attach to the android emulator that I have started with my app loaded before run VSCode. Please refer to the screen attached. Any ideas?

Between, I using latest VSCode and Ionic 3. The debug console has no any messages inside.

https://uploads.disquscdn.c...

damirarh commented 1 year ago

Imported comment written by Damir Arh on 2017-11-10T16:21:00

Could another debugger already be attached to the same emulator instance? Or a firewall blocking the connection? Still, I'd expect it to timeout eventually and output something to debug console. You could try calling "adb devices" from command line to see if your emulator is listed there.
You could also check the issues on GitHub (both open and closed) if anything resembles your situation. Or create your own issue. I found the extension authors quite helpful in my case.