FCM returns SenderIDMismatch when the device's push token was issued by a different Firebase project than the credentials Pushwoosh uses to send. It is a project-mismatch error, not a value you type into Pushwoosh — with the Firebase Cloud Messaging API (V1) there is no Sender ID or Server Key field in Pushwoosh any more.
In an Expo project, check the following:
- One Firebase project everywhere. The
google-services.jsonyou point Expo at (expo.android.googleServicesFileinapp.json) must belong to the same Firebase project as the service-account JSON private key uploaded in Pushwoosh (your project → Configure platforms → Android → upload the JSON private key from Firebase Project settings → Service accounts → Generate new private key). If you switched Firebase projects, re-upload the key and rebuild. - Package name matches. The Android app registered in that Firebase project must use the same package name as
expo.android.package. - FCM API (V1) is enabled for the Google Cloud project (
console.cloud.google.com/apis/library/fcm.googleapis.com). - Re-issue stale tokens. Tokens minted against the old Firebase project keep failing — reinstall the app (or clear its data) on test devices after re-configuring, so the SDK registers a fresh token.
- Correct plugin wiring.
pushwoosh-expo-pluginis a config plugin applied at prebuild; the runtime SDK ispushwoosh-react-native-plugin. Install both, add the config plugin inapp.jsonwith your Pushwoosh API token, and initialize at runtime with the app code only:
There is noimport Pushwoosh from 'pushwoosh-react-native-plugin'; Pushwoosh.init({ pw_appid: 'YOUR_PUSHWOOSH_APP_CODE' }); Pushwoosh.register();project_numberparameter, andpushwoosh-expo-pluginexposes no runtimeinit().
Comments
0 comments
Please sign in to leave a comment.