Assigned
Status Update
No update yet.
Comments
vi...@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).
vi...@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')
}
}
ta...@kochartech.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.
Description
While our solution works seamlessly on Google Pixel devices, we are encountering issue in automatically enabling VoLTE/ VoWiFi/SMSoIP on other Android mobile device OEMs. On further issue diagnosis, we found that we are getting carrierId = -1 in the error response, which prevents MDM APP from utilising carrier privileges.
1. On Samsung devices , we were getting CarrierId=-1
CarrierIdentifier{mcc=417,mnc=50,spn=Rcell,imsi=[****],gid1=null,gid2=null,carrierid=-1,specificCarrierId=-1}
2. On Google Pixel , initially CarrierId was -1 and after load config , CarriedId changed to 2646
1739881230164 : Info: Carrier Config change detected
1739881230070 : Info: +++++++++++++++++++++++++++
1739881230063 : Info: CarrierIdentifier{mcc=417,mnc=50,spn=Rcell,imsi=[****],gid1=null,gid2=null,carrierid=2646,specificCarrierId=2646}
1739881230055 : Info: +++++++++++++++++++++++++++
1739881229384 : Info: Carrier Id -1
1739881229378 : Info: Sub Id -1
1739881229372 : Info: Slot Id 0
1739881229362 : Info: Carrier Config change detected
1739881229281 : Info: +++++++++++++++++++++++++++
1739881229275 : Info: CarrierIdentifier{mcc=,mnc=,spn=,imsi=[****],gid1=null,gid2=null,carrierid=-1,specificCarrierId=-1}
As the mobile operator is new, is there any way to override this limitation as there is a huge dependency on other mobile device OEMs to push OS patch with the updated carrier ID list?