Token Registration issue after Braze SDK update

[abdulbasitaym]

Hello there.
After updating appboy-segment bundled SDK to v13.0.0 with android 13 changes from braze, we are facing an issue in FCM token registration for the first time. On detailed debugging and analysis we find out that this method onNewToken in BrazeFirebaseMessagingService is not invoked for the very first time (in some cases it's not getting invoked even after the first time). Although this method should invoke whenever there's a new token and because that token is not getting registered on Braze that results in no push notifications getting received by the end-user and the user have to kill the app and restart the session multiple times to receive a push notification that is not a good user experience.
It would be super helpful if you guys can look into this issue on top priority.

PS. I have also updated SDK to 14.0.0 but still facing the same issue.

Proposed changes: To resolve this issue, we are setting the FCM token by explicitly calling this method setRegisteredPushToken. Please let me know your thoughts on this resolution. For getting FCM token we are using Firebase BoM with version 28.3.0 for messaging SDK.

Code snippet:

FirebaseMessaging.getInstance().getToken().addOnCompleteListener(task -> {
   if (task.isSuccessful()) {
      braze.setRegisteredPushToken(task.getResult());
   }
});

[radixdev]

Can you share verbose logs and your configuration (braze.xml or BrazeConfig)?

[abdulbasitaym]

Hello,
Please find the config and logs below. Please note logs are filtered out using braze keyword by enabling logs as mentioned in the above link.
Note: After doing some code changes push notifications started getting received with the below code snippet.
Logs are before the code changes where we are not able to receive push.

braze-filtered-logs.pdf