To allow Firebase on Android to use the credentials, the google-services plugin must be enabled on the project. Configure Firebase with Android credentials Then, you can add those keys to the 'SHA certificate fingerprints' on your app in Firebase console.ĭownload the google-services.json file and place it inside of your project at the following location: /android/app/google-services.json. You have to copy both 'SHA1' and 'SHA-256' keys that belong to the 'debugAndroidTest' variant key option.
To generate a certificate run cd android &. The debug signing certificate is optional to use Firebase with your app, but is required for Dynamic Links, Invites and Phone Authentication. Local projects package name which can be found inside of the manifest tag within the /android/app/src/main/AndroidManifest.xml The "Android package name" must match your
On the Firebase console, add a new Android application and enter your projects details. To allow the Android app to securely connect to your Firebase project, a configuration file must be downloaded and added I pieced these steps together from the information found here and here.# Using npm npm install -save Using Yarn yarn add module must be installed before using any other Firebase service. & new File(project.property("yourprojectname.properties")).exists()) section into the condition in which the props variable is assigned then try again. if(project.hasProperty("yourprojectname.properties") (example for Windows) yourprojectname.properties=c:\\Users\\\\signing\\yourprojectname.propertiesģ) Create yourprojectname.properties file in the location you specified in Step 2 with the following information: keystore=C:\\path\\to\\keystore\\yourapps.keystoreĤ) Modify your gradle.build file to point to yourprojectname.properties file to use the variables. The location for this file depends on your OS: /home//.gradle/ (Linux)Ģ) Add an entry pointing to yourprojectname.properties file.
With this solution you get the control of using your own keystore and the magic of automation during debug and release builds.ġ) Create a gradle.properties (if you don't already have one). Yes you can go to File -> Project Structure and assign signing keystores and passwords in the Signing tab but that will put plaintext entries into your gradle.build file which means your secrets might be disclosed (especially in repository commits). This solution also gives you the ability to store your keys outside of the project directory as well as enjoy automation in the signing process. You can specify your own debug keystore if you wish. If you use Windows, probably the location is like this:Ĭ:\User\YourUser\.android\debug.keystore Solution 3 It is at the same location: ~/.android/debug.keystore Solution 2
0 kommentar(er)
