Not signed in
Copyright © 2026 Unity Technologies
[Android] Check for Play Libraries was fixed to ignore Play Core-Common libraries and only throw errors for Play Core as expected. Tests were modified following the fix, and changed for efficiency.
[Android][2023.2] Check for Play Libraries was fixed to ignore Play Core-Common libraries and only throw errors for Play Core as expected. Tests were modified following the fix, and changed for efficiency.
[Android][2023.1] Check for Play Libraries was fixed to ignore Play Core-Common libraries and only throw errors for Play Core as expected. Tests were modified following the fix, and changed for efficiency.
[Android][2022.3] Check for Play Libraries was fixed to ignore Play Core-Common libraries and only throw errors for Play Core as expected. Tests were modified following the fix, and changed for efficiency.
[Android][2021.3] Check for Play Libraries was fixed to ignore Play Core-Common libraries and only show warnings/log messages for Play Core as expected. Tests were modified following the fix, and changed for efficiency.
Reproduction:
Expected Result: No errors or messages
Actual Result: "Can't determine version..." error and debug message detecting play core library when it has not been included
Details:
CheckPlayLibraryAdded in ExtensionModule.cs uses Regex to find Google PlayCore or PlayAssetDelivery dependencies included in Gradle template files.
Due to the format of the search (mentioned in slack thread), it is confusing the "com.google.android.play:core" and "com.google.android.play:core-common" libraries, leading to "Can't determine version" and upgrade prompts. Regex needs to be fixed so as not to confuse the libraries, as the Core-Common library is unrelated to asset delivery and does not interfere if asset delivery libraries were to be added.
Reproducible Versions: 2023.3.0a1, also suspected to reproduce on: 23.2, 23.1, 22.3 and 21.3
Reproducible Devices:
Sign in to see your voted issues