1477 results found
-
1 vote
-
Hosting should preserve the client's IP address when proxying to Cloud Run
When using hosting with rewrites to Cloud Run (e.g., routing all requests to /api/** to a Cloud Run container), the clientIp always reflects the IP address of a Google server rather than the actual client’s IP address. As a result, filtering incoming requests by IP address in the logs viewer becomes impossible.
It would be great if the x-forwarded-for header could be used to populate this field instead.2 votes -
Think Different: Gemini Subscription Rant
Dear product manager, Gemini in Firebase is far from a good and useful product compared to the competition. The usability really sucks yet, however you're already trying to sell a subscription of it.
Firebase sounds awesome and I'm making some trials. But make a decision:
Or you try to sell Firebase making it really easy to test and conclude projects using AI with trully integrated Gemini with great workflow usability to built Apps and write code or you try to sell general Gemini subscription here. Other AIs are bringing better results to develop Firebase solutions.
I'm not buying an early…
1 vote -
Beting
প্রথম ডিপোজিটে ১০%পার্সেন্ট বোনাস
1 vote -
Flutter previews (IOS)
Well, I think that in the first instance I could suggest to correct a small problem that IOS previews have because perhaps depending on the size of the device that is being used the image quality and visibility of the texts is affected, another thing I saw is that when using useMaterial3: true the result is not very similar to doing it using the android emulator or ios locally.
ah and if you can put the theme monokai ocean would be super hahaha.34 votes -
Stability score
Currently firebase crashlytics shows crash free users and crash free sessions, although ANRs are also equally important. ANRs create a bad user experience which is comparable to a crash.
By showing a stability score which considers ANRs as well as crashes, we can show a true representation of app health. This can be at the session level.
2 votes -
Web SDK generation to also export schema types
Currently the dataconnect:sdk:generate command in firebase-tools will generate functions for queries and mutations. There are cases where having TypeScript interface reflections of the schema types would also be beneficial.
AFAIK there's no existing tooling that will conveniently do this mapping (due missing types that one can find in .dataconnect/schema/prelude.gql when the emulator is running).
2 votes -
notes
Add Crashlytics Issue Notes to the Crashlytics Schema [1] for BigQuery Export [2]
[1] https://firebase.google.com/docs/crashlytics/bigquery-export#schema-columns
[2] https://firebase.google.com/docs/crashlytics/bigquery-export3 votes -
Support storing unstructured json in Postgres jsonb column
Postgres support jsonb column that can store arbitrary jsonb objects, very suitable to store unstructured / semi-structured API output.
Postgres also supports index on fields within jsonb.
Can data connect support jsonb column? Mapping fields of API object to Postgres columns can be a headache
11 votes -
Real Android TV devices in Firebase Testlab
At the moment we only have emulators for Android TV. Would be nice to have the option to have Android TV real devices as well.
12 votes -
multiplatform
full support for KMM android, web, ios and desktop.
What is the point of not supporting all of these?we build the best car but you can only use one wheel. Not a great theory for adoption.
1 vote -
Have a Realtime Database located in Australia ( Sydney or Melbourne )
As of this writing, our only option for Database location is US Central, Belgium and Southeast Asia. Having a new region under Australia would be great.
1 vote -
4 votes
-
Do not require third-party cookies
A service released in 2023 should not require third-party cookies to be allowed.
If not for the privacy and usability for its users, then for the project itself, since many browsers are phasing out support for third-party cookies. Firefox already blocks them and chrome will soon do the same:
https://developer.chrome.com/en/docs/privacy-sandbox/third-party-cookie-phase-out/75 votes -
API Revoke Token
Simple API to revoke the token/refresh token from a backend without using the SDK.
19 votes -
Remember sort order for remote config view.
Remember sort order for remote config view so you don't have to change the sort every time the console page is refreshed.
1 vote -
Disables support for TLS 1.0 and TLS 1.1 as these are vulnerable versions
Is there a plan to disable support for TLS 1.0 and 1.0 version across the domains e.g. firebase console, fcm.googleapis.com and other services?
1 vote -
Fix GitHub integration
Issues:
- In the app hosting wizard: Connecting a GitHub account that is not the owner of the GitHub repository and then removing it breaks the GitHub integration process and the App Hosting set up process.
- Being just a collaborator to a GitHub repo doesn't make it visible in the App Hosting Set Up wizard, you have to connect with the GitHub account of the owner of the repo.
Error messages:
- Connection verification failed: unable to verify the authorization token: GET https://api.github.com/user: 401 Bad credentials []: failed precondition.
- Error: Request to https://developerconnect.googleapis.com/v1/projects/PROJECT-ID/locations/europe-west4/connections/firebase-app-hosting-github-oauth:fetchGitHubInstallations had HTTP Error: 400, Failed to list GitHub installations
…
2 votes -
The errors thrown for a wrong password and an account that does not exist should be different
This is a problem I have encountered while using Firebase with Swift. I want to be able to prompt the user to sign up if they do not have an account. However, the error returned from Auth.auth().signIn(withEmail, password) is the same if the user enters the wrong password or an email the doesn't exist. If the errors were different I would be able to show the sign up prompt only if that specific error is thrown.
1 vote -
Hard Spending Limit on Firebase Resources
A Hard Spending Limit option in Firebase Billing settings would allow developers to set an absolute cap on resource spending for their Firebase projects. Once this limit is reached, Firebase would automatically pause or throttle resources to prevent any charges beyond the specified amount. This feature would enhance budget control and predictability for developers and organizations of all sizes.
4 votes
- Don't see your idea?