1234 results found
-
Security vulnerability on using SHA-1 weak hash algorithm
Firebase using SHA-1 weak hash algorithm. This is being raised as Security vulnerability. Recommended to upgrade the hash algorithm.
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…
3 votes -
3 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.
3 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
3 votes -
Rules Debugger with Breakpoints
Imagine how cool it would be to have a debugger for my rules, where I can put breakpoints and see what exact data or condition is causing my rules to fail or pass.
Often times I had to spend so much time in trial and error when writing complex rules for my application. If there is a debugger like I mentioned which is more like any other IDE, it would be super easy and a great developer experience.
3 votes -
A "--no-document-updates" flag for Firestore import
It has happened to me that I accidentally deleted some documents. While you can restore a collection from a backup, there is no option to not overwrite existing data.
This unfortunately makes it impossible to restore accidentally deleted documents, without also affecting other documents that have changed since you last made that backup. The restore would undo lots of changes that happened after the backup was made.
I think a very effective and simple solution could be to allow only injecting those documents from the backup that do not exist in de target collection. So no document is ever overwritten/updated…
3 votes -
Remix support
Have out of the box support for Remix framework implementing SSR which also work with the Emulators.
3 votes -
The Firebase target apply command has also to update the firebase.json with the target name!
The Firebase target apply command has also to update the firebase.json with the target name!
3 votes -
3 votes
-
3 votes
-
3 votes
-
3 votes
-
3 votes
-
3 votes
-
3 votes
-
Our Project has been suspended last two days
Our Project is suspended from last two days and has been restored yet..
2 votes -
I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the righ
I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the right sidebar, which is visually unpleasant. New configurations can't be created immediately, unlike in the previous mode. Starting a test requires creating a new condition; otherwise, the test won't be at the highest priority under the same configuration, and users will end up using other conditions within the same configuration. It's difficult to use, very difficult to use.
2 votes -
First-class Firebase SDK support for Kotlin/Wasm and Compose Multiplatform Web
Please add first-class Firebase SDK support for Kotlin/Wasm, especially for Compose Multiplatform Web apps.
Kotlin/Wasm is becoming an important target for sharing Kotlin and Compose UI across Android and Web. Today, Firebase works well on Android and through the JavaScript SDK on Web, but Kotlin/Wasm integration is still awkward and requires wrappers, JS interop, REST calls, or platform-specific abstractions.
It would be very useful to have official support for Auth, Remote Config, Realtime Database, Firestore, Analytics, and Storage from Kotlin/Wasm.
2 votes -
Allow Firebase project root to be configured independently of firebase.json location
The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.
While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.
This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.
It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.
Example
Consider an Nx monorepo structured like this:
repo/
├── apps/
├──…2 votes
- Don't see your idea?