Troubleshooting
In this page you'll learn what are the most common mistakes when implementing the Notificare Expo plugin together with React Native library.
Switching to Production
While Android doesn't require any additional steps to ensure the development settings work in production, when you're using a single Firebase app, iOS does require different configurations. Therefore, it's recommended you always set up at least two environments in your app and at Notificare, Development and Production.
Always check if the correct NotificareServices.plist is being included in your app. Whenever you build your app directly from Xcode in a device you will be using APNS sandbox servers, so the app keys must target a Notificare DEV application. If you archive your application for Ad Hoc, App Store or Enterprise distribution you should make sure the app keys target a Notificare PROD application. Failing to set this correctly will prevent Notificare from sending notifications to the correct device tokens, since you will be registering invalid device tokens in Notificare.
Expo < 52
Expo 51 and earlier can't correctly link React Native libraries built with builder-bob. This is a known problem in Expo, and it was addressed in Expo 52. If you are experiencing an error as shown below, upgrade to the latest version of Expo.
CommandError: Package "react-native-notificare" does not contain a valid config plugin.
Cannot use import statement outside a moduleConsider using version 3.x in case you're unable to upgrade to Expo 52 for the time being.
Additional native troubleshooting
For more information on common issues when integrating the native part of our library, please take a look at the native SDKs documentation.