Status Update
Comments
ph...@gmail.com <ph...@gmail.com> #2
We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
uc...@google.com <uc...@google.com> #3
It's extremely frustrating that it's apparently now impossible on android 13 to write to data/obb without rooting devices. People hated this change in 11, hated it in 12, and now it's been done again. Please let us access the device we payed for. No one asked for this change.
Description
AGP: 3.0.0-beta2 / 3.0.0-beta3
Android Studio: 3.0.0-beta2
Kotlin: 1.1.4-3
If we use Kotlin in another module (e.g. lib “:foo” ) that applies the “java-library” plugin instead of the “java’” plugin, the kotlin classes will be compiled to a different folder than the java classes. If we try to reference a Kotlin class “Foo” that resides in the “:foo” lib from a test in the “:app” module, studio will fail with a “java.lang.NoClassDefFoundError: com/developerphil/javalib/Foo”.
The reason seems to be that the ‘foo/build/classes/java’ is added to the test classpath but “foo/build/classes/kotlin” isn’t.
I have a attached a test project to reproduce this issue.
Run “com.developerphil.kotlintestclasspathwithjavalib.ExampleUnitTest#addition_isCorrect” to reproduce this error.
This can also be observed when a java-library depends on another java-library in “com.developerphil.javalib.FooJavaTest#someTest”
Everything works from the CLI, it only fails form studio.
Build: 3.0 Beta 2, AI-171.4263559, 201708101859,
AI-171.4263559, JRE 1.8.0_152-release-915-b01x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.12.6 unknown, screens 2560x1440, 1440x900