Firebase实时数据库触发器推送：如何向特定iOS用户发送通知

Hey there! Let's break down your questions clearly since you're just getting started with Firebase Cloud Functions and Node.js.

1. Does the current code send notifications to all stored device tokens? #

Not exactly—let's look at the logic:
The code fetches tokens from /users/${followedUid}/notificationTokens, which are the device tokens belonging to the user being followed (the followedUid). Then it sends notifications only to those tokens. So it's not broadcasting to every token in your entire database, just all devices linked to the specific user who gained a follower.

2. How to modify the code to send notifications only to a specific user? #

This depends on what triggers your notification, but the core idea is to target the specific user's token node instead of the followed user's. Here's a concrete example:

Suppose you want to trigger a notification when a new message is sent to a specific user. You'd adjust the function to:

• Pull the target user's UID (either from the trigger path, or from the data being written)
• Fetch only that user's tokens from their dedicated /users/{targetUid}/notificationTokens node
• Send the payload to those tokens

Here's a modified snippet to illustrate:

exports.sendSpecificUserNotification = functions.database.ref('/messages/{targetUid}').onCreate((snapshot, context) => {
  const targetUid = context.params.targetUid; // Get the specific user's UID from the trigger path
  const messageData = snapshot.val();

  // Fetch only the target user's device tokens
  const getDeviceTokensPromise = admin.database().ref(`/users/${targetUid}/notificationTokens`).once('value');

  return getDeviceTokensPromise.then(tokensSnapshot => {
    if (!tokensSnapshot.hasChildren()) {
      return console.log(`No notification tokens found for user ${targetUid}`);
    }

    // Build your notification payload
    const payload = {
      notification: {
        title: 'New Message!',
        body: `${messageData.senderName} sent you a message: ${messageData.text}`,
        icon: messageData.senderPhotoURL
      }
    };

    // Extract tokens from the snapshot
    const tokens = Object.keys(tokensSnapshot.val());

    // Send to the target user's devices
    return admin.messaging().sendToDevice(tokens, payload).then(response => {
      // Clean up invalid tokens (same as original code)
      const tokensToRemove = [];
      response.results.forEach((result, index) => {
        const error = result.error;
        if (error) {
          console.error('Failed to send notification to', tokens[index], error);
          if (error.code === 'messaging/invalid-registration-token' ||
              error.code === 'messaging/registration-token-not-registered') {
            tokensToRemove.push(tokensSnapshot.ref.child(tokens[index]).remove());
          }
        }
      });
      return Promise.all(tokensToRemove);
    });
  });
});

3. Is storing each user's tokens in separate nodes a viable solution? #

Absolutely—this is actually the recommended best practice for Firebase push notifications!

By storing tokens under /users/{uid}/notificationTokens, you:

• Keep user-specific token data organized and isolated
• Can easily fetch only the tokens needed for a specific user (no need to filter through all tokens in your database)
• Simplify cleanup when a user logs out or uninstalls your app (you just remove tokens from their node)

Your original code already uses this pattern, so you're on the right track. This approach makes it trivial to target any specific user by just referencing their UID in the database path when fetching tokens.

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