Package name you entered when creating the google-services.jsonįile. Q: I can't find the symbol 'R.string.gcm_defaultSenderId',Ī: Make sure the package name in your adle file matches the

If none of the members of client match the package name, an exception is thrown.įor the rest of this document we will use folder if you are using multiple build types.

If the package name matches this value, return the member object.

Check the value of client_info/android_client_info/package_name.

When processing the JSON file for your Android app, the plugin only uses theĬlient object that matches your package name (for the current build Project, while each member of the client array contains informationĪbout the clients (Android apps) that you have added to the project. The project_info object contains general information about your The google-services.json file has the following basic structure: When product flavors are in use these more complicated directory structures are You to maintain a separate Firebase project for your production APKs. Note: Providing a google-services.json file in the release directory allows All of the following directory structures are valid: Of version 2.2.0 the plugin supports build type and product flavor

The google-services.json file is generally placed in theĪpp/ directory (at the root of the Android Studio app module). You can see the result of this step by running Plugin in your app/adle file, like so:Īpply plugin: '-services' This step requires that you apply the Google Services Gradle See Adding the JSON File more information.Īdd dependencies for basic libraries required for the services you haveĮnabled. Resources that can be used in your application'sĬode. Process the google-services.json file and produce Android.

The google-services plugin has two main functions: As part of enabling Google APIs or Firebase services in your AndroidĪpplication you may have to add the google-services plugin to yourĬlasspath ':google-services:4.3.15'

Androidgradleplugin