FCM无法向iOS NativeScript应用推送消息问题求助

It’s frustrating when APNs pushes work flawlessly—even when the app is terminated—but FCM won’t deliver messages, especially after you’ve checked basics like Bundle ID and SSL certificates. Let’s walk through the most likely fixes step by step:

1. Double-Check Your Firebase Console Configuration #

Even if you think you got this right, tiny details can break FCM:

• Exact Bundle ID Match: iOS is case-sensitive here—make sure the Bundle ID in Firebase Console exactly matches what’s in your NativeScript project’s App_Resources/iOS/Info.plist (look for CFBundleIdentifier). Don’t miss any hyphens or capitalization differences.
• Correct SSL Certificate/Authentication Key: If using a certificate, confirm it’s for the right environment (Development for test devices, Production for App Store builds). If you switched to an Authentication Key, verify the Key ID and Team ID are accurate in Firebase, and that the key has Push Notifications enabled in your Apple Developer account.
• Valid GoogleService-Info.plist: Ensure this file is in App_Resources/iOS, hasn’t been renamed, and its values (like GCM_SENDER_ID, CLIENT_ID) match what’s in Firebase Console. Sometimes downloading a fresh copy fixes hidden mismatches.

2. Validate Your NativeScript Push Plugin Setup #

• Update the Plugin: Outdated versions of nativescript-push-notifications or @nativescript/firebase-messaging can have compatibility bugs with newer iOS or Firebase versions. Run npm install @nativescript/firebase-messaging@latest (or your plugin of choice) and rebuild the project.
• Check Token Retrieval & Initialization: Make sure you’re initializing FCM correctly after getting APNs permissions. Log the FCM token when it’s retrieved—if it’s null or empty, that’s a red flag. Look for errors in Xcode’s console during app launch (like FirebaseMessaging error messages) that might point to initialization issues.
• Verify Info.plist Config: Add or confirm this entry in App_Resources/iOS/Info.plist to avoid delegate conflicts:

  <key>FirebaseAppDelegateProxyEnabled</key>
  <false/>
  

3. Test FCM with a Proper Payload #

FCM relies on APNs for iOS delivery, so your payload must include valid APNs fields—even when sending via FCM:

• Use the Right Structure: When testing via Firebase Console or curl, include the aps payload under the apns section. For example, a valid curl request would look like:

  curl -X POST -H "Authorization: key=YOUR_FCM_SERVER_KEY" -H "Content-Type: application/json" -d '{
    "to": "YOUR_FCM_TOKEN",
    "notification": {
      "title": "FCM Test",
      "body": "This should work!"
    },
    "apns": {
      "payload": {
        "aps": {
          "alert": {
            "title": "FCM Test",
            "body": "This should work!"
          },
          "sound": "default"
        }
      }
    }
  }' https://fcm.googleapis.com/fcm/send
  

• Test for Terminated Apps: For the app to receive FCM pushes when terminated, the aps payload must be present—FCM can’t deliver silent notifications without it. Ensure content-available is set to 1 if you need background updates.

4. Check APNs-FCM Bridge Health #

FCM acts as a middleman to APNs, so any issue here will block delivery:

• Confirm APNs Auth Status: In Firebase Console, go to Project Settings > Cloud Messaging > iOS app. Check that your APNs credential (certificate or key) shows as "Active". If it’s "Inactive", re-upload the credential or regenerate it in Apple Developer Portal.
• Apple Developer Portal Checks: Verify your Push Notification certificate hasn’t expired or been revoked. Also, ensure your app ID has Push Notifications enabled under Capabilities.

5. Clean & Rebuild Your Project #

Sometimes cached build files can cause configuration mismatches:

• Run ns clean to clear NativeScript’s cache.
• Open Xcode and clean the build folder (Product > Clean Build Folder), then rebuild the app with ns run ios.

内容的提问来源于stack exchange，提问作者Jonatious