If you are experiencing Push Notifications issues when using the ForgeRock Authenticator for Android, perform the following steps:
- Check the WiFi or cellular connection
- Ensure push notifications are enabled
- Disable software battery optimizations
- Check the Do Not Disturb mode
- Check if Background Data is enabled
- Check if Data Saver is enabled
- Check if the app is allowed to run in the background
- Restart the device
- Check required ports and hosts
- Update the OS
- Check Google FCM delivery issues
A weak WiFi or cellular data connection can delay or prevent you from receiving a Push notification.
On Android devices, notifications are sent from Amazon SNS to the Google Firebase Cloud Messaging service (FCM).
The FCM sends the notification to the registered device over a mobile data or WiFi network.
To check if Push Notifications are enabled for the ForgeRock Authenticator:
- On the Android device, open Settings.
- Select Apps.
- Scroll down and select Authenticator.
- Ensure notifications are allowed.
- Fully close the ForgeRock Authenticator app.
- Open the ForgeRock Authenticator again.
Android uses AI-based software optimizations to preserve battery life, and prevent apps you don't regularly use from remaining active in the background.
The algorithms that power the optimizations can affect the notification system.
To check if Battery Optimizations is turned ON:
- On the Android device, open Settings.
- Select Battery.
- Select Adaptive Battery.
- Click on the switch button to turn the setting off for all apps.
To disable battery optimizations on a per-app:
- Open Settings > Apps > Authenticator > Advanced > Battery > Battery optimization.
The Do Not Disturb mode is designed to suppress all notifications except for a handful you choose to let through.
To check if Do Not Disturb mode is enabled:
- On the Android device, go to Settings.
- Under Sound or Notifications (depending on your specific Android device) review the Do Not Disturb mode.
- If you can't find it in either of these places, search for Do Not Disturb from the bar present at the top of Settings.
Since Android Oreo, you can prevent apps from accessing the mobile data in the background.
While you probably didn't toggle this setting by accident, it's still worth checking out when you have a notification problem.
To check if Background Data is enabled:
- On the Android device, open Settings > Apps > Authenticator > Advanced > Data Usage > Background Data.
The Data Saver feature lets you restrict the amount of data apps use when the device is not connected to WiFi.
To confirm that data saver mode isn't causing any issues, use your phone with the setting disabled (if you currently have it enabled).
To check if Data Saver is enabled:
- On the Android device, go to Settings > Connections > Data Usage > Data Saver.
Since Android Oreo, you can prevent apps from running when you're not actively using them.
Unfortunately, Android can modify this setting without your interaction.
You should review the Background Restriction setting for apps with notification problems.
To check if Background Restriction is enabled:
- On the Android device, go to Settings > Apps > Authenticator > Advanced > Battery > Background Restriction.
If Push notifications are still not working, reboot the device.
A fresh start can eliminate minor glitches that might cause this issue.
Your wireless network must allow communication with Google Firebase Cloud Messaging (FCM) servers over certain ports.
Ensure your Firewall rules do not block any of the following ports:
- TCP port 5228
- TCP port 5229
- TCP port 5230
- TCP port 443
Google releases Android updates often, including new features and fixes that may affect notifications.
If you haven't updated the phone in a while, apps that rely on notifications may be affected.
Make sure the system is updated with the latest Android release.
To troubleshoot Google FCM delivery issues, you can use the Android 'FCM Diagnostics' tool (depending on availability/compatibility):
- Open the Phone app and go to the keypad.
*#*#8255#*#*to open the FCM Diagnostics app.
- Verify that the connection to FCM is established (that is, the text 'Server: Connected' appears).
- Tap the EVENTS button and check the log for any connectivity errors. For example, 'Close err:6 ...'.
You can check the status of this service on the following website: https://status.firebase.google.com/
If the previous suggestions do not help, we recommend that you re-register the affected account with the ForgeRock Authenticator app.
See User cannot log in using Push authentication in AM (All versions) for further information on doing this in AM.