122 results found
-
Authentication feature in Android Wear / WearOS application
The ability to handle autentication and registration feature in android wear / wearos applications, using FirebaseUI or the official firebase auth library in gradle.
Ideally, the same features promoted to android apps but in the wearable world, taking in account the considerations related to battery, performance and data fetching and processing applied to wearables.
2 votes -
Whitelisted email address for testing with passwordless email link
It would be great to have a whitelisted email address to use for testing, like we have for SMS authentication, to avoid this message:
"[firebase_auth/too-many-requests] We have blocked all requests from this device due to unusual activity. Try again later."2 votes -
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 -
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 -
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
-
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 -
Alternate Authentication Options
Adding alternate methods of authentication for Meta apps and google platform like facial recognition and/or eye scanning to make it even more secure 🔐
1 vote -
Enable testing in production apps
We use phone numbers as our primary auth method. We often need to test new user experiences which requires us to create a new account with a real phone number or a test number.
There are two problems we run into:
1. A real phone number will be rate limited after multiple logins
2. Our workaround to (1) is to use test numbers. However, a cap of 10 test numbers is limiting our use caseWe have a GenAI app that is highly personalized for each account. Thus, we often find we need to QA against more than 10 test…
1 vote -
Allow changing the form of email links to a deep link
Currently, Apple app links can require up to 24 hours to start working (due to a delay on downloading the AASA files). This can be worked around by using a deep link instead in the form of myapp://mydomain. When links are generated server-side, I can change the form myself, but that isn't possible client-side.
1 vote -
1 vote
-
Allows Roslyn to create YoungEnterprises@yahoo.com
There's always Theft of my Intellectual Properties, and I'm tired of it. I want to be paid for my creations.
1 vote
- Don't see your idea?