In this story
Where: Settings → Readers & money → Connections → Notifications (Android app (Firebase) section)
Open this page: admin.<your-site>/settings/connections/notifications#kn-push-fcm (replace <your-site> with your site address)
Before you start
- You need an Android app. Only the owner can change keys.
- If your app isn't set up yet, the page says "Waiting for your app's push setup. Keynate sets this up with your app; you don't need to do anything now."
Steps
Automatic (default)
- Open Settings → Readers & money → Connections → Notifications.
- In the Android app lane, check the checklist item "Keynate registered your app for notifications".
- When your app page on keynate.com offers a new app version, accept it. Phones get notifications only from an app version that includes it.
- Open the new app on your phone, then send a test from the wizard with its device token.
Your own Firebase (advanced)
- Turn on Use my own keys.
- In the Firebase console, add a project and an Android app with the package name from your app page.
- In Firebase, open Project settings, Service accounts and press Generate new private key. A .json file downloads.
- In Keynate, under Android app (Firebase), add the Firebase service account (JSON): choose the file or paste its text.
- Check the Firebase project id. It is filled from the file.
- Turn on Send to Android and save.
- Send a test, then rebuild your app.
Common problems
- "This file isn't a Firebase service account. Download it from Firebase → Project settings → Service accounts."
- "Add the Firebase service account file, or turn Android off."
- "Use the project id from Firebase (lowercase letters, numbers and dashes)."
Questions
Frequently asked questions
Is the key shown again after saving?
No. It is stored encrypted and never shown again.
Do I need to do anything for Android by default?
Accept the app rebuild when your app page offers it.