[Bug]: Push notifications on Android do not arrive

[steunobravo]

Which Platforms?

Android

Which React Native Version?

0.70.8

Which @braze/expo-plugin version?

1.1.1

Which @braze/react-native-sdk SDK version?

4.1.0

Repro Rate

100%

Steps To Reproduce

After adding to the Braze project, when from the Tool of Expo notifications (https://expo.dev/Notifications) I try to send a notification on an Android device, the device does not receive the push notification.
If, on the other hand, I remove the Braze dependencies and try to send a notification, the device receives notifications again.

• "@braze/expo-plugin": "^1.1.1"
• "@braze/react-native-sdk": "^4.1.0"

Expected Behavior

Even after setting braze, notifications must continue to work the same.

Actual Incorrect Behavior

Android devices do not receive notifications

Verbose Logs

Braze v24.3.0 .Braze FirebaseMessagingService( 1683): Remote message did not originate from Braze. Not consuming remote message: com.google.firebase.messaging.RemoteMessage

Additional Information

No response

[radixdev]

Hi @steunobravo ,

We're actively exploring a way to have notifications be able to be dually served either from our Braze Firebase service or a default service of your choosing. This would fix the manifest priority issue that you're seeing. We'll update this issue when we have more updates.

[jordanjoecooper]

Hi @radixdev & @hokstuff

In version 1.1.2 I can see there some info to the change log around androidFirebaseMessagingFallbackServiceClasspath & androidFirebaseMessagingFallbackServiceEnabled.

Looking at the code commits both of those values have been added to a constants file but do not appear to be used in the code and therefore it would not seem that they solve the issue. Is that right or is there another version to be released that utilises them?

I tried using the values after updating but the issue reported here persisted, although, I may be jumping the gun, apologies if I am and please let me know if there is anything we can do to help!

[renatoalvesmh]

I have same issue as well. Please fix that with new version. I subscribe everything that jordanjoecooper said

[radixdev]

Hi @jordanjoecooper @renatoalvesmh ,

Those new configuration options are indeed relevant to this issue but require Android SDK 28.0.0 to properly work. I.e. setting the expo push notification classpath (via https://www.braze.com/docs/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=android#optional-forward-android-push-to-another-firebasemessagingservice) and having Android SDK 28.0.0 as the native SDK version would result in expo notifications appearing properly and Braze notifications also appearing properly.

We're currently updating our React SDK to Android 28.0.0 and then this expo SDK afterwards but please feel free to just bump your Android SDK to 28.0.0 and use those configuration values in order to achieve forwarding as expected. Please let us know if this accomplishes your use case.

[renatoalvesmh]

Hi @radixdev

We are using react-native in our project. We followed that guide: https://www.braze.com/docs/developer_guide/platform_integration_guides/react_native/react_sdk_setup/#prerequisites-and-compatibility

We installed @braze/react-native-sdk and @braze/expo-plugin. There is a way to pass that issue in react-native braze package ? We saw that was added in last version on @braze/expo-plugin constants for androidFirebaseMessagingFallbackServiceClasspath & androidFirebaseMessagingFallbackServiceEnabled but nothing logic around that constants

[steunobravo]

Hi @jordanjoecooper @renatoalvesmh ,

Those new configuration options are indeed relevant to this issue but require Android SDK 28.0.0 to properly work. I.e. setting the expo push notification classpath (via https://www.braze.com/docs/developer_guide/platform_integration_guides/react_native/push_notifications/?tab=android#optional-forward-android-push-to-another-firebasemessagingservice) and having Android SDK 28.0.0 as the native SDK version would result in expo notifications appearing properly and Braze notifications also appearing properly.

We're currently updating our React SDK to Android 28.0.0 and then this expo SDK afterwards but please feel free to just bump your Android SDK to 28.0.0 and use those configuration values in order to achieve forwarding as expected. Please let us know if this accomplishes your use case.

Hi @radixdev Using expo and updating:

• "@braze/expo-plugin": "^1.1.2",
• "@braze/react-native-sdk": "^7.0.0",

But, searching on node_modules/@braze/react-native-sdk/android/build.gradle I saw this:
dependencies {
api 'com.braze:android-sdk-ui:27.0.1'
api 'com.facebook.react:react-native:+'
}

So I am using the android sdk version 27.
How can I use the version 28?

[jennybonato]

Hi everyone, I still experience this bug using

• "@braze/expo-plugin": "^1.1.2",
• "@braze/react-native-sdk": "^8.0.0"

which uses the Braze Android SDK 29.0.0.
Any updates on this?

[PCOffline]

Hey, I am also experiencing this bug. @radixdev any updates?

[andresouza-maple]

Any updates?

[AbdulmalekAlshugaa]

Any update and where I can find my androidFirebaseMessagingFallbackServiceClasspath