Obsolete
Status Update
No update yet.
Comments
pe...@longcheer.corp-partner.google.com
Same here. I have links in a local html file referencing file:///android_res/drawable/ and on all gradle build flavors using another applicationId (added suffix) the Webview only shows broken links.
This behaviour seems not to be connected solely to Android 5.0 since it occurs on Android 4.4.4 too (tested with current cyanogenmod 11 build).
This behaviour seems not to be connected solely to Android 5.0 since it occurs on Android 4.4.4 too (tested with current cyanogenmod 11 build).
ra...@google.com
pe...@longcheer.corp-partner.google.com
As a hotfix I added the following code to the gradle buildscript, which generates an additional R.java with changed java package for every flavor. I don't like this solution though.
android.applicationVariants.all{ variant ->
variant.javaCompile.doFirst{
copy {
from "${buildDir}/generated/source/r/${variant.dirName}/com/example/application/R.java"
into "${buildDir}/generated/source/r/${variant.dirName}/com/example/application/${variant.buildType.name }/"
}
File rFile = file("${buildDir}/generated/source/r/${variant.dirName}/com/example/application/${variant.buildType.name }/R.java")
String content = rFile.getText('UTF-8')
String newPackageName = "com.example.application.${variant.buildType.name }";
content = content.replaceAll(/com.example.application/, newPackageName)
rFile.write(content, 'UTF-8')
}
}
android.applicationVariants.all{ variant ->
variant.javaCompile.doFirst{
copy {
from "${buildDir}/generated/source/r/${variant.dirName}/com/example/application/R.java"
into "${buildDir}/generated/source/r/${variant.dirName}/com/example/application/${
}
File rFile = file("${buildDir}/generated/source/r/${variant.dirName}/com/example/application/${
String content = rFile.getText('UTF-8')
String newPackageName = "com.example.application.${
content = content.replaceAll(/com.example.application/, newPackageName)
rFile.write(content, 'UTF-8')
}
}
ra...@google.com
I've recenly encountered this issue and I must say it's quite a nuisance. Searched half of the Internet just to find out that the problem lies in Gradle's applicationIdSuffix :). I think this bug should be reported to Android SDK Build Tools devs, because only they can do something about it.
ra...@google.com
IMHO it's the case of Android platform problem. Resources are packed, WebView tries to load them from wrong place. It's not build tools that put them in wrong place.
And by the way it's very frustrating bug.
And by the way it's very frustrating bug.
Description
Suite / Plan VTS / vts Suite / Build 15_r2 / 12273510 VT test brush: signed-gsi-arm64-img-12271965 Reproduction steps: run vts-m keystore_2-cient_tests Test : keystore2_client_tests#keystore2_client_attest_key_tests::keystore2_generate_attested_key_fail_to_get_aaid Result :fail Details: ---- keystore2_client_attest_key_tests::keystore2_generate_attested_key_fail_to_get_aaid stderr ---- thread 'main' panicked at system/security/keystore2/tests/keystore2_client_attest_key_tests.rs:743:13: assertion failed: result.is_err() thread 'main' panicked at ./system/security/keystore2/test_utils/run_as.rs:323:17: Child did not exit as expected Signaled(Pid(11593), SIGABRT, false)
Local description: This project uses Android 15 and encountered an error during VTS testing (test item: keystore_2-cient_tests). The error item is as shown above, We found that the read error is located in the keystore_2-cient_tests tool. Could you please help me check which tool your company used to fix this issue? Which GSI tool can you provide to fix this issue? In addition, we ran the device after flashing gsi_arm64-img-12211298, and the test results were normal. However, when we flashed signed-gsi-arm64-img-12271965, the test results were fail, as shown above. May I ask which of these two tools is the latest?