The Expo Bare Workflow, Expo Local Notifications, and OneSignal do work together. Of course, warnings don’t prevent your app from running. However, it seems that the warning cautions you that using Expo for remote notifications and OneSignal for remote notification will be in conflict together. I’ve tested it in a production application and it all works well.
The following is some quick background information about my use-case and the reasons I decided to eject and use OneSignal.
- Initially, I was using Expo Local Notifications to schedule future alerts regarding calendar events to a user.
- I needed to integrate remote notifications to alert users when other users joined a calendar event. However, I wanted more control, customization, and features beyond what Expo offered for remote notifications. I decided to eject and install OneSignal, having only used Expo Notifications for local notifications.
TLDR: If you’re hoping to use OneSignal (for remote notifications) with an Expo Bare Workflow project with Expo Notifications (for local notifications only, because OneSignal does not offer local notifications in a convenient way), you can do so–just ignore the warning and go about your day.
Please, do monitor the behavior of having both libraries coexisting as Expo and OneSignal update their SDK. However, at the moment with Expo SDK v40 and OneSignal v4.0.3, everything seems to work smoothly.
Thanks again for the help everyone @notbrent and hope that anyone else that comes across this fairs well.