Firebase安卓端注册阶段无需验证获取手机号的实现方法咨询

Hey there! Great question—let's break down how to implement this for your Android app.

Firebase's built-in Phone Authentication is designed specifically to verify a user owns the phone number, so it will always require a verification code. But since your goal is just to collect a phone number during registration without verifying it, you don't need to use that module at all. Instead, you can store the phone number as a custom user field alongside your existing email-based auth flow.

Step-by-Step Approach #

• Keep your existing email registration flow: Use Firebase Auth's createUserWithEmailAndPassword() method to create the user account as you already do.
• Add a phone number input to your registration form: Let users enter their phone number here (you can add basic front-end validation like checking length or format to reduce invalid inputs, but no verification code is needed).
• Store the phone number after registration:
  1. Option 1 (No backend required): Save the phone number to Firebase Firestore or Realtime Database in a user-specific document (e.g., a users collection where the document ID matches the user's Firebase UID). This is the simplest approach for client-only implementations.
  2. Option 2 (With backend): If you have a backend server, you can use the Firebase Admin SDK to set the phoneNumber field directly on the Firebase Auth user record. Client-side code can't modify this field directly (it's restricted to admin/verified servers), so your backend would handle this via an API call after the user registers.

Key Notes #

• Since you're not verifying the phone number, keep in mind that you won't have confirmation the user actually owns that number. If you need to validate it later (for password resets, notifications, etc.), you can trigger Firebase's Phone Authentication flow at that point to verify and update the stored number.
• Always add basic front-end validation for the phone number (e.g., checking it matches your region's format, isn't empty) to avoid garbage data, but this is just for user experience—not security/verification.
• If using the Admin SDK approach, never expose the Admin SDK credentials in your Android app—only run it on your trusted backend server.

Example Android Code (Kotlin) #

Here's a quick snippet showing the email registration + Firestore storage flow:

// Initialize Firebase Auth and Firestore
val auth = FirebaseAuth.getInstance()
val firestore = FirebaseFirestore.getInstance()

// Handle registration button click
binding.btnRegister.setOnClickListener {
    val email = binding.etEmail.text.toString().trim()
    val password = binding.etPassword.text.toString().trim()
    val phoneNumber = binding.etPhone.text.toString().trim()

    // Basic input validation
    if (email.isEmpty() || password.isEmpty() || phoneNumber.isEmpty()) {
        // Show error to user
        Toast.makeText(this, "Please fill all fields", Toast.LENGTH_SHORT).show()
        return@setOnClickListener
    }

    // Create user with email and password
    auth.createUserWithEmailAndPassword(email, password)
        .addOnCompleteListener { task ->
            if (task.isSuccessful) {
                val currentUser = auth.currentUser ?: return@addOnCompleteListener
                
                // Store phone number in Firestore
                val userData = hashMapOf(
                    "email" to email,
                    "phoneNumber" to phoneNumber,
                    "createdAt" to FieldValue.serverTimestamp()
                )

                firestore.collection("users")
                    .document(currentUser.uid)
                    .set(userData)
                    .addOnSuccessListener {
                        // Registration complete—navigate to home screen
                        Toast.makeText(this, "Registration successful!", Toast.LENGTH_SHORT).show()
                        // Add your navigation logic here
                    }
                    .addOnFailureListener { e ->
                        // Handle Firestore save error
                        Toast.makeText(this, "Failed to save user data: ${e.message}", Toast.LENGTH_SHORT).show()
                    }
            } else {
                // Handle registration failure (e.g., email already exists)
                Toast.makeText(this, "Registration failed: ${task.exception?.message}", Toast.LENGTH_SHORT).show()
            }
        }
}

内容的提问来源于stack exchange，提问作者Uğurcan Çetindağ