Firebase initialization fails
Firebase initialization fails
Confirm that
google-services.json belongs to the app package and the Google Services plugin runs for the app module. The SDK reuses the default Firebase app when one exists.No installation appears
No installation appears
Call
Pushctl.initialize from Application.onCreate, confirm internet access, verify that the embedded token uses the Client preset, and call waitForRegistration to receive the exact failure.Registration times out
Registration times out
Confirm Firebase initializes with the app’s
google-services.json and that the device can reach Firebase and the Pushctl API.A Firebase identifier exists but registration fails
A Firebase identifier exists but registration fails
Inspect the error from
waitForRegistration or onRegistrationFailed. Verify network access, the Client token, and the Android platform configuration in Pushctl.Android 13 never asks for permission
Android 13 never asks for permission
Call
requestPermission from a visible Activity. Do not call it only during background startup.The notification uses the wrong icon or channel
The notification uses the wrong icon or channel
Initialize with
PushctlConfiguration and set notificationIcon, notificationChannelId, and notificationChannelName. Existing channel properties may need to be changed by the user in system settings.Notification opens are not routed
Notification opens are not routed
Register the click listener early, or forward a custom activity intent through
handleNotificationOpen.The user association is missing
The user association is missing
Wait for confirmed registration, then call
login after authentication and handle its callback. A later successful login replaces the previous ID, and a successful logout makes the installation anonymous.Login or logout fails
Login or logout fails
Identity methods report an error when the installation is not registered or the Pushctl API rejects the update. Do not treat invocation alone as success.