122 results found
-
39
Subject: Phone Auth - Real numbers failing with error code 39 despite correct configuration (Blaze plan)
Project ID: washgo-1582e
We are experiencing a persistent issue with Firebase Phone Authentication on Android (React Native / @react-native-firebase/auth). Test phone numbers work correctly, but real phone numbers consistently fail.
Error observed:
[auth/unknown] An internal error has occurred. [ Error code:39 ]Steps already taken:
- Firebase project upgraded to Blaze (Pay-as-you-go) plan
- App signing key SHA-1/SHA-256 (Play App Signing) added to Firebase Console
- Upload key SHA-1/SHA-256 also added to Firebase Console
- OAuth 2.0 Client ID (Android) manually created in Google…1 vote -
Update new prefix MSISDN
Dear Google,
I contact from Movitel in Mozambique,
Currently we deploy new Prefix +25888xxxxx for MSISDN , but it not yet update by google, to ensure services for customer when receive otp from google applicaition.
I want to contact to need your help1 vote -
Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release
Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release a service that after staring into your devices camera for 20 seconds will log you into any account email platform or social media that's ever log your face and stored it in the cloud
3 votes -
Email OTP Verification Code
We should open a Firebase community discussion about Email OTP authentication.
Firebase currently does not support native email-based OTP login (only email link or password auth).
I want to build a passwordless system where:
- Users sign in with email only
- A one-time code (OTP) is sent to email
- No passwords are stored
- Same OTP flow is used for login, signup, and account actions
This would provide a simpler and more secure authentication method without requiring phone numbers or passwords.
10 votes -
Add official React Native / Expo SDK with Clerk-like DX: protected routes, RBAC components, and declarative auth UI
The Firebase Auth SDK for React Native requires significant boilerplate
to implement properly — auth state listeners, Firestore role fetching,
route protection, and error handling all have to be wired up manually
in every project.The developer experience gap compared to alternatives like Clerk is
significant. Clerk provides:• <SignedIn> / <SignedOut> declarative components
• <Protect role="admin"> role-based rendering
• Automatic route guards for Expo Router
• Pre-built auth screensI built an open-source package called react-native-fireguard that fills
this gap for Firebase developers:npm install react-native-fireguard
It wraps Firebase Auth with:
• <FirebaseAuthProvider> — single setup, handles everything
•…1 vote -
"Verify Email Address" page should be translated
We notice an inconsistency where the initial Firebase email verification page displays in English (the one with the 'Complete verification' button), despite the URL containing the lang=fr parameter, while the final success message correctly appears in French.
This appears as a bug.1 vote -
Firebase Auth Expose Email Verification Status and Attempts
Firebase Auth Expose Email Verification Status and Attempts
We have a user that is having problems verifying. However there is no logging or debugging for this feature on firebase.
- Add an interface under auth to see which users have requested verification
- Add information about if the email was recieved, spammed, blocked, expired
- Visually show which accounts are not validated, pending validation, and validated.
- Be able to reset validation, or manually validate
2 votes -
Native support for RBAC (Role-Based Access Control)
Native RBAC (Role-Based Access Control) management
Currently, to manage roles (admin, editor, client), you have to use Custom Claims via the Admin SDK (Node.js) or store the roles in Firestore. This is cumbersome for a beginner.The improvement: Being able to define roles directly from the Firebase console and have them automatically appear in the
request.authobject of Security Rules without additional code.1 vote -
Improve Firebase Auth integration with Server side rendering (Next.js)
Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.
I hope Firebase will consider my…
1 vote -
1251 end
VIP NUMBER
1 vote -
1 vote
-
Support adding a note to each authorized domain in the auth settings
We have a lot of authorized domains added by different team members. We'd like to remove unused ones, but we have no idea which ones are actually being used or why they were added. It'd be great if we could add a note to each item for future reference.
1 vote -
সাইন-আপ
সাইন-আপ
1 vote -
1 vote
-
Firebase Auth with IP address whitelist & blacklist
Blacklist scenario: Let's say that a device is detected for fraud/scam activity. I want to blacklist the device for 1 year based on the previously logged-in IP address, so the scammer is no longer able to use their devices. Even though the scammer created a new Firebase account, they won't be able to do that because of the IP address blacklist.
Whitelist scenario: Let's say that I have an internal app. I want this app to be used by my employees only, so only specific devices are allowed to login.
5 votes -
Add Native Invitation Email Flow for Firebase Authentication (Multi-Tenant Apps)
In many multi-tenant applications, an invitation is a time-limited, one-time handshake between two parties inside an app context (e.g. organization, workspace, team, or document).
After the invitation email is accepted, the link should bring the recipient into the app at a specific contextual entry point (for example, a workspace, organization, or document reference). From that point:
Existing users continue through the regular sign-in flow (if not already signed in)
New users continue through the standard sign-up flow
At that point, the application takes full control of the user experience and logic.
From Firebase’s perspective, the responsibility would primarily be to…
1 vote -
Save phone
Idea save
1 vote -
Session Management & Device Visibility for Firebase Authentication
Add optional session management to Firebase Authentication that creates and tracks individual login sessions per user, allowing developers/users to view active sessions with device and operating system information (derived from the User-Agent), approximate location (city/country), session creation time, and last active timestamp. The feature would enable per-device logout and selective session revocation via the Firebase Admin SDK, with optional read-only access for clients to build “logged-in devices” security UIs, while remaining privacy-safe, opt-in, and configurable without exposing raw IP addresses or User-Agent strings.
View Complete Proposal/Request here: https://gist.github.com/12fahed/42e802890b5b887b93c66d94ceadeb2d
34 votes -
BUILD
LOVE
2 votes -
Multiple Roles
As of now, firebase only supports single role. We want multiple role support. Example, Employer, Employee, Admin etc.
3 votes
- Don't see your idea?