[RichNotifications]: how to enable rich push notifications with the expo plugin?

[mvolonnino]

What problem are you facing?

I have push notifications all setup with expo project and braze working. But i know with my bare RN app, i had to setup a rich service extension to allow images to be attach to push notifications.

Is that currently available in the expo plugin? If not, how can that be added?

Workarounds

Not sure - attaching images to iOS push notifications do not show up in the push notification

Ideal Solution

that can be added to either the plugin config setup, or steps to add a plugin to add the rich service extension to the expo project

Other Information

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

[jerielng]

Hey @mvolonnino, you would have to integrate rich push notifications at the native level from Xcode by following these setup steps here. Let us know if you have any issues with these steps.

[mvolonnino]

Hey! Yup thank you I have used and setup Braze rich notifications already on a bare RN app. My issue is stemming from an expo manager app, how would I be able to setup rich notifications?

My work is switching from a bare RN to an expo managed App, and everything so far is hooked up for Braze besides being able to attach pictures to push notifications.

I've been looking into the expo config plugins, along with withXcode functions they give.

Not sure how to get the BrazeNotificationService in the expo project, as when I inspect the braze react native SDK node module, I'm not seeing anywhere I can link to it with the expo config plugin!

Any guidance or ideas would be awesome, thanks again!

[jerielng]

Got it, thanks for the additional context! Unfortunately, we don't currently have support to add the BrazeNotificationService to an Expo Managed workflow, so this is something our team will need to look into and add. At the moment, we don't have a timeline for this, but we will take a closer look and will keep you updated on the progress in this thread.

[mvolonnino]

Okay thanks again! I will keep watch on this thread as that is pretty important to our business in having that rich notification support with Braze.

Let me know if theres anything I can do as well or if its possible somehow to get that BrazeNotificationService within the @braze/react-native-sdk or the @braze/expo-plugin": "^1.1.2 for that matter!

[renatoalvesmh]

would be good if its possible to add it. I also need it as well. Thank you
expo/expo#25162

[jerielng]

@renatoalvesmh Thanks for sharing the link! We're still working on prioritizing this feature along with other Xcode extension-based features, but hope to have an update for you soon.

[YentingChen]

It would be wonderful if you could add it soon, as we have the need too.

[jerielng]

Hi all, we've just released version 2.1.0, which introduces Expo automation for Rich Push notifications and Push Stories in iOS. You can refer to the changelog entry for usage details. Feel free to reach back out if you have further questions. Thanks!

[mvolonnino]

@jerielng - now this is awesome! One question though as I am running into build errors when updating everything to expo sdk50 & updating to the latest 2.1.0 version.

Getting this build error in the eas-build process:

Starting from Xcode 14, resource bundles are signed by default, which requires setting the development team for each resource bundle target.

and from inspecting the xcode logs, im seeing this issue:

        ➜ Explicit dependency on target 'BrazeExpoRichPush' in project 'Volo'
        ➜ Implicit dependency on target 'BrazeUI' in project 'Pods' via options '-framework BrazeUI' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'ExpoAdapterBraze' in project 'Pods' via options '-framework ExpoAdapterBraze' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'braze-react-native-sdk' in project 'Pods' via options '-framework braze_react_native_sdk' in build setting 'OTHER_LDFLAGS'
        ➜ Explicit dependency on target 'BrazeKit' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeLocation' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeUI' in project 'Pods'
        ➜ Explicit dependency on target 'ExpoAdapterBraze' in project 'Pods'
        ➜ Explicit dependency on target 'braze-react-native-sdk' in project 'Pods'
    Target 'ExpoAdapterBraze' in project 'Pods'
        ➜ Explicit dependency on target 'braze-react-native-sdk' in project 'Pods'
    Target 'braze-react-native-sdk' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeKit' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeLocation' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeUI' in project 'Pods'
    Target 'BrazeUI' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeKit' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeUI-BrazeUI' in project 'Pods'
    Target 'BrazeUI-BrazeUI' in project 'Pods' (no dependencies)
    Target 'BrazeLocation' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeKit' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeLocation-BrazeLocation' in project 'Pods'
    Target 'BrazeLocation-BrazeLocation' in project 'Pods' (no dependencies)
    Target 'BrazeKit' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeKit-BrazeKit' in project 'Pods'
    Target 'BrazeKit-BrazeKit' in project 'Pods' (no dependencies)
    Target 'BrazeExpoRichPush' in project 'Volo'
        ➜ Implicit dependency on target 'Pods-BrazeExpoRichPush' in project 'Pods' via file 'Pods_BrazeExpoRichPush.framework' in build phase 'Link Binary'
    Target 'Pods-BrazeExpoRichPush' in project 'Pods'
        ➜ Explicit dependency on target 'BrazeNotificationService' in project 'Pods'
    Target 'BrazeNotificationService' in project 'Pods' (no dependencies)
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.2.99. (in target 'BrazeLocation-BrazeLocation' from project 'Pods')
/Users/expo/workingdir/build/ios/Volo.xcodeproj: error: Signing for "BrazeExpoRichPush" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'BrazeExpoRichPush' from project 'Volo')
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.2.99. (in target 'BrazeUI-BrazeUI' from project 'Pods')
/Users/expo/workingdir/build/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 11.0, but the range of supported deployment target versions is 12.0 to 17.2.99. (in target 'BrazeKit-BrazeKit' from project 'Pods')

Looks like its failing on the signing for the Rich Push notifications. I could not find anything on this for the expo config plugin - so wondering how to handle this here and allow the rich push notifications in the latest 2.1.0!

[YentingChen]

Hi @jerielng

Thank you for implementing the new updates that allow the use of rich push notifications.

However, I am experiencing the same issues mentioned above.
I started to get the build error in the eas-build process after integrating the rich push notification:

Starting from Xcode 14, resource bundles are signed by default, which requires setting the development team for each resource bundle target.

It would be greatly appreciated if you could provide us with some suggestions or any updates on how to solve the issue. Thank you 🙏

[renatoalvesmh]

@jerielng

[mvolonnino]

opened a new issue here: #30 to see if we can get any answers!