Closed mateot1 closed 1 year ago
Sales
the identifier of the channel or the name of it? The SDK requires the id.Sales
is the ID, not the name. We use a translatable string from the name that is slightly different. Can you email this to support@braze.com? We'd need unedited logs and more detailed implementation specifics which would be better handled securely as you pointed out. We need more steps to reproduce your issue.
@radixdev just sent. Got an automated message that it's a company holiday, so... hope you get it tomorrow!
following up on 5 re the channel creation:
Channels are created using NotificationManagerCompat.from(context)
and calling createNotificationChannel(notificationChannel)
. Each channel is initialized with NotificationChannel(channelId, name, notificationImportance)
where (as you noticed) channelId
is for some reason a capitalized string, name
is a translatable string, and notificationImportance
is almost always NotificationManager.IMPORTANCE_DEFAULT
except for one case where we use IMPORTANCE_HIGH
. I am certain these were created before attempting to send the push from braze using one of the ids.
@radixdev apologies, I just realized my test device had do not disturb on! Notifications are displaying. The only bug on Braze's end is not recognizing the channel id when the string is capitalized — I tried just using lowercase "sales" and that seems to work. I'll continue to debug and open an issue with mparticle if it seems to be with their integration.
Hello @mateot1 ,
Please re-open a new issue with clean reproduction steps on how to reproduce notification channels being case-sensitive. This is not an issue we're aware of and could potentially just be an issue with mParticle as you're pointing out.
Thanks, Julian
@radixdev the mparticle sdk doesn't create our channels and I was encountering the bug while bypassing mparticle for receiving and displaying pushes so seems unlikely that it has anything to do with it, but it's a much less serious bug so I'll reopen once we get to the root cause of the main issue.
Braze Android SDK Version
23.3.0, possibly as early as 18.0.0
Steps To Reproduce
We recently were made aware that our marketing push notifications have been broken for quite some time. In-app messages still work, so the integration is working enough that it is receiving push notifications and displaying those, but is failing when it comes to the system push notifications.
We are currently using the sdk via this wrapper, which could certainly be part of the issue, but in order to ensure messages are forwarded to the sdk and bypass mparticle's wrapper I've temporarily added a call to
BrazeFirebaseMessagingService.handleBrazeRemoteMessage
in our ownFirebaseMessagingService
and I've been able to debug the issue far enough to confirm that a push is received and the sdk is attempting to callnotify
with a notification, it just never is shown on the device.Looking at the logs, the only thing I noticed that seems to be going wrong is that the notification channel id from the payload is not being used (the sdk says it is invalid even though we have created one with this id). However, even after creating a channel with the default id (
com_appboy_default_notification_channel
), it still does not display.Expected Behavior
The sdk should display a system push notification, with the correct channel (the logs say no channel with id found, even though one does exist).
Actual Incorrect Behavior
No push notification is displayed
Verbose Logs
Additional Information
In-app messages still work, but pushes have apparently been broken ever since we updated mparticle some months ago (5.35.1 to 5.38.2, which I believe corresponds to 17.0.0 to 19.0.0 of the braze sdk). I am hoping we can roll forward so I have been debugging with the latest version of mparticle which pulls in 23.3.0 of the sdk. I have been testing on a device running Android 13.