1234 results found
-
4 votes
-
4 votes
-
4 votes
-
4 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…3 votes -
Support bulk deletion of completed Remote Config A/B Testing experiments
Firebase currently limits projects to 300 experiments. Teams that run frequent A/B tests eventually reach this limit. The Firebase Console only allows deleting completed experiments one by one, which becomes extremely time-consuming. Please add:
- multi-select with checkboxes;
- “Delete selected”;
- optionally “Delete all completed experiments”.
3 votes -
Allow the App Testing Agent to persist user state between test runs
It would be great if the App Testing Agent could persist a user session or saved app state between test runs. This would allow tests to start from a predefined state instead of always going through the onboarding or login flow, making it much easier and faster to test authenticated features and later stages of the app.
3 votes -
Rap drill
Des musiques social et spirituels pour motiver et faire réfléchir les gens
Vidéo alléchantes3 votes -
restore old firestore browser behavior where only part of long entries where visible.
restore old firestore browser behavior where only part of long entries where visible. Now when browser show entire value of props usability dropds to ZERO for any recored with long texts of maps...
3 votes -
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 -
Provide Native Document Counters and Metadata for Firestore Collections
Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read…
3 votes -
3 votes
-
200
Fo Tamien
3 votes -
Add support for pnpm workspaces
While it does support for pnpm, it does not support pnpm workspaces. The reason for this is because it currently looks for the
pnpm-lock.yamlfile in the workspace app directory, but this file is actually in the root directory when using workspaces. This causes lots it to switch to usingnpmand the build to fail.3 votes -
103605920
5.000$
3 votes -
More information in errors for native sql statements
Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!
3 votes -
3 votes
-
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
3 votes -
Job development
Animated script for game development video prompts analytics workspace for project management
3 votes -
Perform automatic rollouts only for changes to configured app directory
I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.
Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a…
3 votes
- Don't see your idea?