Android credentials

Open your app's Settings → Credentials and click Add Application Identifier. The wizard asks for:

1. A Play Store service account, the first time, if your team doesn't have one yet. See Store API keys.
2. An application identifier, such as com.example.my_app. Letters, digits and underscores only.
3. A keystore. Bifrost Managed Credentials generates one for you. Choose Upload an existing keystore if your app is already on Google Play.
4. A Firebase configuration file, optional, for push notifications.

Uploading your own keystore

Use this when your app is already published. Google Play ties an app to its upload key permanently, so builds signed with any other key are rejected until you reset the upload key in Play Console.

You need the .jks file plus three values: the keystore password, the key alias, and the key password. They may all be the same, but be clear which is which.

To create a fresh keystore for a new app without using managed credentials, run this inside your NativePHP project and follow the prompts:

php artisan native:credentials android

It writes the .jks into a credentials folder in your project. Keep the file and both passwords in a password manager and out of git.

The credential page

Each application identifier has its own page under Credentials where you can download the keystore and its upload certificate, replace the service account or Firebase file, rotate the password of a managed keystore, move an existing app onto a managed keystore, and run Check credentials against the Play Developer API.