Fixed
Status Update
Comments
gh...@google.com <gh...@google.com>
gm...@gmail.com <gm...@gmail.com> #2
Really I've waited more than 4 minutes to attach to the process, and it didn't finish.
Even trying to cancel it using the button failed, and I had to kill the process of the IDE
Even trying to cancel it using the button failed, and I had to kill the process of the IDE
mr...@gmail.com <mr...@gmail.com> #3
Attached logs of the IDE after I started it , after killing it.
Otherwise I can't do it because it's an annoying dialog that doesn't let me do anything except looking at it being stuck.
Otherwise I can't do it because it's an annoying dialog that doesn't let me do anything except looking at it being stuck.
mr...@gmail.com <mr...@gmail.com> #4
Attached screenshot. This occurs also when pressing the debug button...
be...@gmail.com <be...@gmail.com> #5
The dialog says "processing classes for emulated method breakpoints"
gh...@google.com <gh...@google.com> #6
Thank you for reporting this issue, we are aware that some older version of the emulator are unable to handle method breakpoint (Internal bug:
The temporary workaround is to use normal breakpoint instead of method breakpoints. The video you attached does not show if you have created such a breakpoint. Another workaround is to use a real device which does not seem to exhibit this issue.
ma...@gmail.com <ma...@gmail.com> #7
@6 Please fix this.
I can't reach your link.
I can't reach your link.
Description
Symptom
If you are using Android Studio 4.2.0 and have upgraded to Kotlin plugin 1.5.0, then new Kotlin projects created by Studio will fail to build due to the follow Gradle sync error:
A fix is planned for Android Studio 4.2.1.
Workaround
Replace "1.5.0-release-764" with "1.5.0" in the project's build.gradle files.
Related issues
After applying the workaround, you may still see a false-positive warning in the editor saying:
This warning comes from the Kotlin plugin. The upstream bug is KTIJ-7657 and the fix should land in Kotlin plugin 1.5.10.
Background
The original issue was filed at https://issuetracker.google.com/182701888 --- I created this issue to make it easier for users to find the workaround.