This is an umbrella bug to track issues related to mobile-install v1.
adb push permissions issue https://github.com/bazelbuild/examples/issues/77java.lang.NoSuchMethodException: android.content.res.AssetManager.ensureStringBlocks [] https://groups.google.com/forum/#!searchin/bazel-discuss/mobile-install%7Csort:date/bazel-discuss/A4B8-GmBHxI/yoVNKuQ1BAAJ Note that mobile-install v1 will be deprecated as soon as mobile-install v2 (written in Starlark) is open sourced, so we'll need to revisit these issues and ensure that mi-v2 fixes them.
cc @jgavris
Update: I'm drafting a plan to open source mi-v2, which involves open sourcing a lot of its tool dependencies.
Unfortunately I don't think I can share this document as it has references to internal infra, but there will be documentation for v2 once it's released.
Hi Jin, I'm facing the same bug on Android 9.
java.lang.RuntimeException: Unable to create application com.google.devtools.build.android.incrementaldeployment.StubApplication: java.lang.IllegalStateException: java.lang.NoSuchMethodException: ensureStringBlocks []
In addition, I can't disable incremental build with either "--noincremental" or "--incremental=false" flag. bazel mobile-install always use incremental deployment instead of full build.
@JiamingFB I have a fix pending for the installation bug.
I also have a fix pending for the incompatibility with aapt2.
@JiamingFB fix it out, you'll need to build Bazel at HEAD to use it, or use Bazel 0.22 when it's released.
Thanks @jin! So this will definitely land in 0.22?
Yes!