Fixed
Status Update
Comments
pa...@google.com <pa...@google.com>
je...@google.com <je...@google.com>
ju...@stitchfix.com <ju...@stitchfix.com> #3
Same issue here
am...@google.com <am...@google.com> #4
+1
lu...@gmail.com <lu...@gmail.com> #5
Me too.
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
Failed to open vm 3
Failed to create HAX VM
No accelerator found.
failed to initialize HAX: Invalid argument
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
Failed to open vm 3
Failed to create HAX VM
No accelerator found.
failed to initialize HAX: Invalid argument
vi...@asos.com <vi...@asos.com> #6
Same problem here
am...@google.com <am...@google.com> #7
Hi all,
Thanks for bringing this to our attention. We are working with Intel on how to fix it, and have reproduced the problem in-house as well. Currently there doesn't seem to be a simple workaround. It also looks like macOS 10.13 added new security features that block kernel extensions such as HAXM without explicit user intervention, so we will need to streamline the install part as well.
In the meantime, we've tested Hypervisor.Framework which seems to work on 10.13. Try running the emulator on Canary channel 26.1.x (API 25/26 recommended) with Hypervisor.Framework; put the text "HVF = on" in ~/.android/advancedFeatures.ini (create this file if it doesn't exist already).
Frank
Thanks for bringing this to our attention. We are working with Intel on how to fix it, and have reproduced the problem in-house as well. Currently there doesn't seem to be a simple workaround. It also looks like macOS 10.13 added new security features that block kernel extensions such as HAXM without explicit user intervention, so we will need to streamline the install part as well.
In the meantime, we've tested Hypervisor.Framework which seems to work on 10.13. Try running the emulator on Canary channel 26.1.x (API 25/26 recommended) with Hypervisor.Framework; put the text "HVF = on" in ~/.android/advancedFeatures.ini (create this file if it doesn't exist already).
Frank
ko...@gmail.com <ko...@gmail.com> #8
(x86 32-bit images only on that for now, as well)
ko...@gmail.com <ko...@gmail.com> #9
Worked perfect, thanks
Description
What happened
After upgrading Android Gradle Plugin version to 7.1.0-rc01, and when running
testDebugUnitTest
task, onlytransformDebugUnitTestClassesWithAsm
is being executed, but nottransformDebugClassesWithAsm
. However both tasks are executed if Android Gradle Plugin is downgraded to 7.0.2STEPS TO REPRODUCE:
testDebugUnitTest
,transformDebugClassesWithAsm
is not executed, onlytransformDebugUnitTestClassesWithAsm
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
Sample repository for reproducing:https://github.com/jilulu/sample-agp71-hilt-app
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
Gradle tasks executed inhttps://pastebin.com/EAMxa3tu
testDebugUnitTest
:Studio Build: Bumblebee 2021.1.1 RC 1 Version of Gradle Plugin: 7.1.0-rc01 Version of Gradle: gradle-7.2-bin.zip Version of Java: 14 OS: macOS 12.0.1 (21A559)