Sign-in and notifications on WordPress

Before you start

• The FluxNative plugin is active on your site (install it).
• Your app is in a Firebase project, with its iOS app and Android app added under Project settings › General › Your apps, using the app's bundle ID and package name.
• Each part below matches a line on the plugin's tab, with a How to link back here.

Google sign-in

1. In the Firebase console, open Authentication › Sign-in method and turn on Google.
2. For Android, open your Android app under Project settings › General and choose Add fingerprint: add the SHA-1 and SHA-256 from Build › Signing key › Advanced, and Google Play's app signing key once the app is on Play. Without the fingerprint of the key that signed the app, Google offers no account on Android.
3. Under Your apps, download GoogleService-Info.plist from the iOS app and google-services.json from the Android app. Download them after steps 1 and 2: older copies miss the sign-in IDs.
4. In WP admin, open FluxNative › Mobile app › Sign-in. Under Fill from your app's files, choose both files and press Save.
5. The notice says how many IDs were added, and Google sign-in says Ready.

• The plist adds the iOS client ID and the bundle ID; the JSON adds the web client ID and your Android app's client ID. A project's JSON often lists several Android apps: the plugin takes the one under Android package (from App links, or type it once). IDs already saved stay, the files are not kept, and Saved IDs lists each one with where it came from.
• Android sign-ins are issued to the web client ID, so it must be among the saved IDs. The JSON and FluxNative's sync both add it; typing IDs by hand, add it too.
• No Google client ID in it means Google was off when you downloaded the file: turn it on, then download it again.
• Edit by hand lists the saved IDs. Delete a line to stop accepting it.

Sign in with Apple

1. In Apple Developer › Certificates, Identifiers & Profiles › Identifiers, open your app's App ID, tick Sign In with Apple and save.
2. Upload GoogleService-Info.plist as in step 4 above: its bundle ID fills Apple IDs, and Apple sign-in says Ready.

• No Firebase file? Type the bundle ID under Edit by hand › Apple IDs.
• Offering Google sign-in on iOS? Offer Sign in with Apple too, or Apple may reject the app (App Store guideline 4.8).

Android notifications

1. In Firebase, open Project settings › Service accounts, choose Generate new private key and confirm. A JSON file downloads once.
2. In WP admin, open FluxNative › Mobile app › Notifications, then Android key (Firebase). Choose the file and press Save key.
3. Android says Ready with your Firebase project.

• The same key serves phone sign-in and deletes a person's Firebase user with their account (Sign-in › Advanced › Firebase users).
• To take it away, tick Remove and press Save key.

iOS notifications

1. In Apple Developer › Certificates, Identifiers & Profiles › Keys, press +, name the key, tick Apple Push Notifications service (APNs), then Continue, Register and Download. The file AuthKey_<Key ID>.p8 downloads once.
2. Copy your 10-character Team ID from Apple Developer › Membership details.
3. In WP admin, open Notifications › Apple key (APNs). Choose the .p8 file, leave Key ID empty to read it from the file name, enter the Team ID and press Save key.
4. iOS says Ready with the key and team.

• One APNs key serves every app of your Apple team. Renamed the file? Type the Key ID.
• Apple needs HTTP/2: the tab says when your server's PHP can't use it, and your host updates curl.

What the lines mean

Related

Connect your store and website · Push notifications · Android signing keys