This help page is for users in Creator 6. If you are in the older version (Creator 5), click here. Know your Creator version.

• Generating keystore file
  
• Download Firebase config file and Firebase Service Account file

Generating keystore file

Note:

1. It is highly recommended to store the App Signing Keystore file and its related information used during your first app submission to the Google Play Store in a secure location. This file verifies your identity and is required for publishing any future updates to your app. If this file is lost, you will not be able to update the existing app on the Google Play Store.
   
2. If you are using the Upload Keystore file as your App Signing Keystore for publishing, ensure that this file is also stored securely.
   
3. To generate the App Signing Keystore file for Android, you must have a Java Development Kit (JDK) or Java Runtime Environment (JRE) set up. Alternatively, you may use Android Studio.

1. Open the Terminal or Command Prompt.
2. Replace <my-release-key> and <alias_name> with the desired file name and alias name, respectively, then:
   
   keytool -genkeypair -v -keystore <my-release-key>.keystore -alias <alias_name> -keyalg RSA -keysize 2048 -validity 20000 -storetype jks

   You will be prompted to set your Keystore password.

3. Set your Keystore password and memorize it. You'll need this again when you code sign your app for Android.
4. Enter the details as prompted.
5. Set your Key password:
   
   • Enter the required password.
   • Else, press the RETURN or ENTER key in your keyboard to set the Keystore password as the Key password.

The Keystore file will be generated and downloaded in the path where you executed the above commands.

Note: You might encounter the error message "The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format." Kindly ignore this message and proceed further.

Download Firebase config file and Firebase Service Account file

Note:

1. Firebase Cloud Messaging server key has been deprecated on June 21, 2024. To continue using push notifications, update your new service account JSON file (FSA file) instead of the deprecated FCM server key before the above mentioned date. 
2. The Firebase config file and Firebase Service Account file are required to enable push notification support in your Android app.
   

1. Download Firebase config file

1. Sign in to your Firebase console.
2. Select the required project. If you haven't created a project yet, then:
   
   1. Create a project in Firebase. Learn how
   2. Register your app with Firebase. Learn how
3. Click the Settings icon, then select Project settings.
4. Navigate to the General tab.
5. In the Your apps card, select the package name of the app for which you need a config file.
6. Click the google-services.json button. Your Firebase config file will be downloaded to your device.

2. Download Firebase Service Account file

1. Access your Google firebase console.
2. Select the required project.
3. Click Settings and then select Project Settings.
4. Navigate to the Service accounts tab and click Generate New Private Key. A confirmation popup will be shown, and the Firebase Service Account file will be downloaded once you confirm it.
5. Securely store the JSON file containing the key and upload it your Creator account to enable the push notifications.
   

Points to note

1. Please be aware that the idle session timeout configured for portals will not affect sessions on code-signed mobile apps for customers.

Related topics

• Understand download as mobile app
• Code sign Android app for users
• Code sign Android app for customers