iOS via FCM

Some libraries (Flutter with firebase_messaging, React Native with @react-native-firebase/messaging, Cordova with Firebase plugins and Capacitor with @capacitor-firebase/messaging) give you an FCM token on iOS, not an Apple one. In that case the send to iOS goes through Firebase, and Firebase delivers it to Apple.

Pushtifly detects the token type when it's registered, so you don't have to specify it.

What you need

1. The Firebase service account uploaded to Pushtifly. See Firebase.
2. In Firebase, the Apple key so Firebase can deliver to iOS: Project settings → Cloud Messaging → Apple app configuration → APNs authentication key. Upload your .p8 there with its Key ID and Team ID.

How to know which token your app has

In Devices, each iOS device shows its token type: APNs or FCM. You can also choose the app's default iOS mode: direct APNs or via FCM.

Common errors

• THIRD_PARTY_AUTH_ERROR: Firebase doesn't have the APNs key, or it's wrong.
• It arrives on Android but not on iOS: check step 2 and that the app has the Push Notifications capability in Xcode.
• Capacitor with @capacitor/push-notifications: that plugin gives you the Apple token, not the FCM one. You need the .p8 credential in Pushtifly (direct APNs). It's the most common configuration mistake; the wizard warns you about it.