[question]: Run OneSignal in parallel with expo-notifications

[dgsunesen]

How can we help?

So I'm experiencing some issues with OneSignal (onesignal-expo-plugin) and expo-notifications running in parallel. Ever since I installed and enabled OneSignal in my app, all listeners for handling user interactions on push notifications are not working anymore. For instance, a user sents another user a message, we send a push notification (using expo-server-sdk), the recipient taps the notification and is send directly to the chat.

To achieve this, I would do something like Notifications.addNotificationResponseReceivedListener(listener) with expo-notifications. Unfortunately, ever since OneSignal was enabled, this is not working. Stuff like requesting permission is working just as before, only listeners seems to be broken.

On the other hand, if I listen for push notifications send with OneSignal, I'm able to react to those using the below example:

OneSignal.setNotificationOpenedHandler(openedEvent => {
  console.log("OneSignal: notification opened:", openedEvent);
  const { action, notification } = openedEvent;
});

Isn't it possible to have both running at the same time?

OneSignal Expo SDK version

1.3.1

Platform

No response

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[emawby]

@dgsunesen Thank you for reporting we will need to investigate the compatibility problem. When you send a notification from OneSignal are you able to receive events on the "Notifications.addNotificationResponseReceivedListener" or just the OneSignal handler?

[dgsunesen]

@emawby Only on the OneSignal handler

It seems the issues is only around listening to notification events, whereas e.g. requesting permission like Notifications.requestPermissionsAsync() (https://docs.expo.dev/versions/latest/sdk/notifications/#requestpermissionsasyncpermissions) is still working.

[emawby]

Interesting ok we will investigate. We use something called swizzling to intercept notification events, but we forward them on so that other handlers still receive them. There could be an issue around this when using expo-notifications.

[dgsunesen]

Any news on this?

Let me know if there is anything else you'd need from me in terms of more information or the like

[dgsunesen]

Would be nice to get an update on this :-)

[emawby]

Hello unfortunately we do not have any news to share yet. Are you seeing this warning when your app is started? https://github.com/expo/expo/blob/168ee43f71f005baa11edf98e518593443e1807a/packages/expo-notifications/ios/EXNotifications/Notifications/EXNotificationCenterDelegate.m#L32

[dgsunesen]

Hello unfortunately we do not have any news to share yet. Are you seeing this warning when your app is started? https://github.com/expo/expo/blob/168ee43f71f005baa11edf98e518593443e1807a/packages/expo-notifications/ios/EXNotifications/Notifications/EXNotificationCenterDelegate.m#L32

No, I don't see that warning

[emawby]

Ok I noticed this issue in their repo as well. I will continue trying to dig through their implementation to find the conflict.

[dgsunesen]

@emawby So meanwhile I've been looking into customer.io and they seem to have some of the same issues. You can see it here — maybe you can get more insights on the issue from that.

[emawby]

@dgsunesen That is helpful I will see if we can make a similar fix

[pratikdhody]

Any luck @emawby ?

[dgsunesen]

Any breakthrough @emawby ? :)

[pratikdhody]

Any breakthrough @emawby ? :)

FYI @dgsunesen I’m in the process of figuring this out also. For me, it’s only affecting iOS where as Android is working as expected. I’m going to be trying to figure out how to disable the one signal listener as I believe it’s what is causing the issue. Disabling this should allow the expo-notifications one to handle the request. Will report back this week.