Hi there! I have an issue with my build: android build failed with error 256. Tested both in 3731 and 3736.
Execution failed for task ':App:checkReleaseAarMetadata'.
> Could not resolve all files for configuration ':App:releaseRuntimeClasspath'.
> Could not resolve com.google.android.gms:play-services-auth:20.2.+.
Required by:
project :App
> Failed to list versions for com.google.android.gms:play-services-auth.
> Unable to load Maven meta-data from https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-auth/maven-metadata.xml.
> Could not HEAD 'https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-auth/maven-metadata.xml'.
> Read timed out
Excluding the plugin.gpgs.v3 plugin from the build solve the issue.
This isn’t a Solar2D issue as such. It’s a network issue.
By looking at the logs, it says gpgs.v3 plugin depends on play-services-auth:20.2.+ and that request is timing out in your log. Excluding the plugin fixes the build, because it removes that dependency.
So the thing to check on your end is whether you can reach Google’s Maven repository at all. You can just try curl with the URL from the logs, i.e.
If that hangs, times out, etc. then the issue is with your connection.
I googled that play-services-auth:20.2.+ and it seems that because of the +, Gradle has to ask dl.google.com which 20.2.x version is newest and it re-checks once a day even when the library is already cached.
I guess pinning it to a specific version should resolve the caching issue and help out developers with connection issues, but I don’t know if there’s a particular reason for the cache busting (like too frequent updates to pin the version, etc.) that I’m overlooking.