Node.js+Firebase SDK发送FCM通知报invalid-argument错误求助

Hey Daniel, let's work through this FCM error you're facing. The "invalid argument" message almost always ties back to an issue with the data you're sending to the FCM API, so let's break down the most likely fixes step by step:

1. Check Your Device Token (Most Common Fix) #

Looking at the token you provided:

let token="f8mNlJq4VOY:APA91bF5_8ldOZEm34ajCfNx7hZ9_LhjUBQFDwZbtSnCNEzb1bEtMsXKlM8upyicvmnJ92xELZzDSxTMaeZrCrrau"

FCM tokens are typically 150+ characters long, and this one looks truncated (it ends abruptly at "rau"). That's a huge red flag.

• Double-check that you copied the full, unmodified token from your client app (Android/iOS/Web). Tokens can get cut off if you're copying from a log or console that truncates long strings.
• Test the token directly in the Firebase Console's Cloud Messaging tab (send a test message to the token). If the console also throws an error, the token is definitely invalid — either expired, linked to an uninstalled app, or corrupted.

2. Validate the Message Object Structure #

While your code matches the official docs, let's rule out subtle structure issues:

• Confirm all fields in notification and data are strings (you're already doing this with score and time, which is good — FCM rejects non-string values in these fields).
• Make sure there are no extra, undocumented fields in the message object. FCM will reject requests with unrecognized parameters.
• Add a log to print the full message before sending, to confirm nothing is being modified unexpectedly:

  console.log('Sending message payload:', JSON.stringify(message, null, 2));
  

3. Update Your Firebase Admin SDK #

Outdated SDK versions can have compatibility gaps with the latest FCM API endpoints. Run this command to upgrade to the latest stable version:

npm install firebase-admin@latest

4. Verify Admin SDK Initialization #

Even though you said the SDK loads correctly, double-check your service account setup:

• Ensure your service account key has the Cloud Messaging Sender role (it should have this by default if you generated it from the Firebase Console).
• Confirm your initialization code is properly structured, like this:

  const admin = require('firebase-admin');
  const serviceAccount = require('./path-to-your-service-account-key.json');
  
  admin.initializeApp({
    credential: admin.credential.cert(serviceAccount)
  });
  

Bonus: Get More Specific Error Details #

Modify your catch block to log extra error context — sometimes the SDK hints at exactly which argument is invalid:

.catch((error) => {
  console.log('Error sending message:', error);
  if (error.details) {
    console.log('Detailed error info:', error.details);
  }
});

Start with verifying the token — that's 90% of the time the fix for this error. Let me know if any of these steps resolve your issue!

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