|
||||||
/jetified-play-services-basement-17.5.0/res/values/values.xml
|
||||||
Users don't need to (and should not) explicitly include
<meta-data
android:name="com.google.android.gms.version"
android:value="xxx" />
In their AndroidManifest.xml anymore. When they include a Google Play services dependency, one of those .aar files has this flag that gets manifest merged into the user's project.
If the user has this explicitly, and THINKS they are using 1 version, but some dependency requires a newer version and the manifest merge wanted a different value, there could be that inconsistency at runtime.
Recommendation: Publisher should remove <meta-data
android:name="com.google.android.gms.version" ...> from their app's AndroidManifest.xml file.
Please get back to us if this doesn't help you.
Regards,
|
||||||
Hi Jaguan,
Thank you for reaching out to us.
As per checking on the previous response of my colleague, the recommendation on this is you should remove <meta-data android:name="com.google.android.gms.version" ...> from your app's AndroidManifest.xml file. Kindly let us know if this works for you.
Regards,
|
||||||
Hi Jaguan,
Hi Jaguan,
As the rest of the team mentioned, you should remove the <meta-data android:name="com.google.android.gms.version" ...>. The team mentioned that, when you include a Google Play services dependency, one of those .aar files has this flag that gets manifest merged into the user's project. Just let us know if you encounter any errors on this when you remove the recommended approach on this.