Express+Cloud Functions中req.query始终为空的问题求助

Let's break down why your req.query is coming up empty and how to fix it step by step:

First, Verify Your Request URL #

The most common pitfall here is using an incorrect URL to hit your Cloud Function. Firebase Cloud Functions require your project ID in the URL structure. Your request should look like this:

https://us-central1-YOUR_PROJECT_ID.cloudfunctions.net/users?email=mymail@test.com

If you're omitting YOUR_PROJECT_ID, the request might still reach a default endpoint but won't carry over query parameters correctly.

Debug the Request Flow #

Add debug logs to confirm what's actually reaching your function. This will help you rule out if the query params are being lost before your handler runs:

const checkUserName = (req: any, res: any) => {
  if (req.method !== 'GET') {
    return res.status(405).send(`${req.method} is not allowed`);
  }
  
  // Add these lines to debug
  console.log(`Full request URL: ${req.url}`);
  console.log(`Raw query object: ${JSON.stringify(req.query)}`);

  // ... rest of your code
};

After deploying, check the Cloud Functions logs (via Firebase Console or firebase functions:log) to see if req.url includes the ?email=... part. If it doesn't, the issue is with how you're sending the request, not your code.

Fix Your Express & Firebase Initialization #

Your code is missing some critical Firebase Admin setup and Express best practices. Here's the corrected version with explanations:

const cors = require('cors');
const express = require('express');
const app = express();
// Import Firebase Admin properly
const { initializeApp, firestore } = require('firebase-admin');

// Initialize Firebase Admin (required for Firestore access)
initializeApp();

app.use(cors({ origin: true }));
// Explicitly add urlencoded middleware (ensures consistent parsing of request data)
app.use(express.urlencoded({ extended: true }));

const checkUserName = (req: any, res: any) => {
  if (req.method !== 'GET') {
    return res.status(405).send(`${req.method} is not allowed`);
  }

  console.log(`Request query: ${JSON.stringify(req.query)}`);

  // Simplify email validation
  if (!req.query.email) {
    return res.status(400).send('Email not provided');
  }
  
  const email = req.query.email.trim();
  if (!email) {
    return res.status(400).send('Invalid email address');
  }

  firestore()
    .collection('users')
    .doc(email)
    .get()
    .then((doc: any) => {
      // Return a serializable JSON response instead of the raw DocumentSnapshot
      return res.status(200).json({
        emailExists: doc.exists,
        userData: doc.data() || null
      });
    })
    .catch((error: any) => {
      console.error('Error checking email:', error);
      // Always send an error response to the client (don't just log it)
      return res.status(500).send('Failed to check email uniqueness');
    });
};

// Your route matches the root of the /users function, which is correct
app.get('/', checkUserName);

exports.users = functions.https.onRequest(app);

Test Locally with Firebase Emulators #

Deploying to the cloud for every test slows you down. Use the Firebase Emulator Suite to test locally:

1. Run firebase emulators:start --only functions
2. Access your function at:

   http://localhost:5001/YOUR_PROJECT_ID/us-central1/users?email=mymail@test.com
   

This lets you see logs in real-time and iterate faster.

Key Fixes Summary #

• Proper Firebase Admin initialization: You were missing explicit imports for initializeApp and firestore, which could cause silent failures.
• Serializable responses: The raw Firestore DocumentSnapshot can't be directly sent as a response—we convert it to a JSON object instead.
• Error handling: We now send an error response to the client when Firestore throws an error, instead of just logging it.
• Debug logs: These help you confirm if query params are actually reaching your function.

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