Play Core library used in sdk is incompatible with targetSdkVersion 34
Closed this issue · 12 comments
Got the following email from Play Console:
Update your Play Core Maven dependency to an Android 14 compatible version! Your current Play Core library is incompatible with targetSdkVersion 34 (Android 14), which introduces a backwards-incompatible change to broadcast receivers to improve user security. As a reminder, from August 31, Google Play requires all new app releases to target Android 14. Update to the latest Play Core library version dependency to avoid app crashes: https://developer.android.com/guide/playcore#playcore-migration
The sdk is currently using the com.google.android.play:core-common:2.0.2 library which seems to be incompatible with targetSdkVersion 34 (Android 14).
SDK Version
13.1.1
React Native, Android Versions
Android 14
Any update?
This issue has been automatically marked as pending feedback because we need additional information to be able to investigate it further. It will be closed in 7 days if it remains inactive. Thank you for your contributions.
Getting same warning from google any update?
No updates... @manasbatchservice You are sure that it is this particular package causing the Google play warning right?
Run the following command to check all the dependencies listed in the app, and check which one has the com.google.android.play:core dependency, by exporting all the dependencies to a text file dependencies.txt
./gradlew app:dependencies > dependencies.txt
Yes, our mobile app, we are also facing same issue, please fix this ASAP.
This issue has been automatically marked as pending feedback because we need additional information to be able to investigate it further. It will be closed in 7 days if it remains inactive. Thank you for your contributions.
if anyone finds a solution please comment it out here
any updates anyone?
This issue has been automatically marked as pending feedback because we need additional information to be able to investigate it further. It will be closed in 7 days if it remains inactive. Thank you for your contributions.
This issue has been automatically closed since we haven't heard back from you. Please feel free to re-open the issue if you have more information to add.
Still looking for a fix here