Files
breeze/droid/app/gplay-classpath.gradle
waozi cf1323ac8f Keep Firebase's Gradle plugin in the Google Play edition
Only the -gplay edition may read a Google library. The google-services
plugin's classpath moves from the root plugins block into
droid/app/gplay-classpath.gradle and its application into
droid/app/gplay.gradle, both applied only in a Gradle run whose tasks name
gplay. Such a run refuses release or debug tasks beside it, so the Makefile
and the release workflow build the normal and gplay APKs in separate runs,
and the normal and F-Droid builds never resolve the plugin. The Moto check
builds only the normal APK and no longer writes the Firebase config.

CI checks the Gradle files with Kryon's google-free action, the release
workflow checks the normal, per-ABI and -fdroid APKs and finds Play
Billing in the -gplay APK, and the F-Droid workflow checks F-Droid's own APK.
2026-10-29 16:22:59 -03:00

11 lines
326 B
Groovy

// The Google Play edition's Firebase Cloud Messaging plugin, which
// build.gradle adds to its own classpath (beside the Android plugin it
// extends) only in a Gradle run that builds the gplay build type.
repositories {
google()
mavenCentral()
}
dependencies {
classpath 'com.google.gms:google-services:4.5.0'
}