615 results found
-
3 votes
-
3 votes
-
3 votes
-
3 votes
-
Robo test have full compatibility with unity game engine
We've been trying to create automations utilising Robo test on our games built with Unity, but were unable to record the UI inputs due to our project being built with the NGUI framework which is not currently supported within the automation framework provided so any attempts to set up testing steps are not being recognised.
We'd like to suggest that Firebase Robo test have full compatibility with 'Unity game engine' in order to get around this problem and be able to consider the different types of UIs used within in games and apps as this would allow us to proceed…
2 votes -
3 votes
-
Shows message to user that SSL will not show immediately
When i connected custom domain to Firbase, site url showed as insecure, with red warning. This made me purchase SSL CERTIFICATE on my domain provider just to realize at the end the firebase does provide SSL, but it is notpropagated immediately. This is a bad customer experience. A clear warning shoud be shown to the user, telling him the red "insecure" mark will take time to disappear!
1 vote -
Support for WebAssembly in Cloud Functions
Many languages requested in other posts—Swift, Rust, Kotlin, etc.—can be implemented all at once by adding WebAssembly (WASM) and WebAssembly System Interface (WASI) to the list of Cloud Functions’s supported runtimes (and—importantly—supplying high-quality documentation).
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."1 vote -
Apply filters from crash issues list (eg. state = open) to the graphs above.
This can be either done by directly adding the filter option to the graphs above, or by a toggle which applies filters from the list to the graphs. (not by default, to prevent confusion/regression from current behaviour)
1 vote -
Supports Cloud SQL connection with Firebase Functions V2 natively as it was with V1
Migrating a Firebase Functions project from V1 to V2 using Cloud SQL is not feasible. It appears that Cloud SQL connections are not yet supported in V2. Cloud SQL connection works automatically and required no actions in V1. It would be beneficial if connecting to a Cloud SQL instance using V2 could be made as simple as it was before.
1 vote -
2 votes
-
Allow developers to enable authentication limit to a certain collection/document(in cloud firestore) and to a certain node (in RTDB)
Currently, there is no optimal way to achieve this. If we could write a cloud function for it, then it'd be great.
1 vote -
Firebase. ML
Hi ba
1 vote -
2 votes
-
CI & CD for deployments
Git based CI & CD auto deployments would really be a game changer, it can be integrated to things like cloud run and enable this. Half the time I use tools like vercel and netlify because of lack of auto deployments in firebase
2 votes -
Persisted indexes in the Realtime Database
The indexes in the Realtime Database are created in-memory and on-the-fly - and they are 'garbage collected' when memory is needed for something else.
This makes it expensive (meaning high CPU usage, not costly) to query large collections of data in the Realtime Database.
Collections can also become so large that they are not queryable through the SDKs, but only using the firebase cli tool. One hope would be that with an actual persisted index, it would always be possible to iterate through a collection of nodes, no matter the number of nodes in the collection.
2 votes -
Add event ids for browser viewing into Crashlytics BigQuery tables
I had trouble with finding a specific crash event in the group of crashes. BigQuery gave me an event_id, but I was not able to use this id in the URL query param to open a specific crash in browser. Browser event ids and bigquery event ids are different. Not sure if I’ll need it in the future again, but it was a bit annoying to get all the threads and stacktraces from bigquery
2 votes -
Enable deployments that don't delete previous artifacts
Have an option to deploy and keep previous deployment artifacts instead of deleting them.
Even better would be an option for this with a TTL on previous deployment artifacts (that haven't been updated or re-deployed in subsequent deployments).
2 votes -
An automated way to create test cases
Enable developers to use code script as an input and create test cases of this code script.
1 vote
- Don't see your idea?