Dave Holoway

Thanks for your suggestion. I need a bit more information to understand what the best solution is here (I've not used the remote development feature, so I'm unsure how it...

If the decompiler produces valid Java code which matches the line numbers encoded in the app debug info, I think this should work. Normally `appSrcRoot` is set to the root...

Yes, it's a common problem with decompilers - the line numbers are encoded in the compiled files so the decompiled files should be formatted to match, but many don't bother...

My understanding is that VSCode is responsible for triggering intellisense based on your settings (but I may be wrong). It's definitely the case that the extension does not look for...

Do you have debugging turned on your device? Is Android Studio able to see your device? If you execute `adb devices` from a command window, does it list your device....

@morgan-misty As far as i know, the current set of Java language support extensions (red-hat, etc) unfortunately do not support Android development. The Android debugger extension doesn't have a language...

Hi @juanrh - thanks for reporting this. At the moment, there's no way to set multiple source root folders, but it should be possible to update the extension to support...

The Android debugger extension only works for pure Java and Kotlin code - the JDWP commands won't work for JNI libraries or native code. Once the native library is loaded,...

The latest version of the debugger now attempts to extract the manifest directly from the built APK and uses the source file as a fallback. This should fix this issue,...

VSCode currently supports: - [ ] Condition (truthy-expression) breaks - [x] Hit-count breaks Note that only supporting hit-count breaks causes a breakpoint warning to appear - but the functionality still...