138 results found
-
Firestore return problem path with PERMISSION_DENIED error
While committing a batch to firestore, if a documents breaks one of the security rules, we only receive: Status{code=PERMISSION_DENIED, description=Missing or insufficient permissions., cause=null}
That doesn't tell me which document in the batch has the issue. Can you add the document path the is causing the error? Potentially in the "cause" field?The logic behind this is that we are seeing Crashlytics reports on our android project with these PERMISSION_DENIED errors, and it is near impossible to track it down without more data.
4 votes -
Way to access tracelog of firestore events (onCreate, onUpdate, onDelete)
One frequent and strange bug we are facing with firestore is the dropping of events when designing large batch onWrite-listeners. This leads to unexpected bugs in production code.
For some reason, when executing say 300 to 1000 onCreates at once, different events seem to drop and are never responded too.
A way to access the tracelog of firestore events (in Stage 1 Cloud functions) would help us debug this problem. It would also help replay event streams in case the database is corrupted due to non-responding to the event streams.
4 votes -
Allow running Firestore queries from console
Running quick queries straight from the console is currently impossible, making it hard to make adjustments DB wide without fiddling with code.
4 votes -
Is anyone else unable to sign into the support page?
Whenever trying to sign into the support page to log an issue the page refreshes but does not sign me or my coworkers in, is anyone else experiencing this issue? I have been unable to find any support from firebase, hoping this gets some traction.
3 votes -
Firestore collection group query on document id
Currently, you cannot use Fieldpath.document_id for collection group queries, which is rather shameful considering you can do that in Firebase UI.
Relevant StackOverflow: https://stackoverflow.com/questions/56188250/how-to-perform-collection-group-query-using-document-id-in-cloud-firestore
3 votes -
CMS for Firestore
A CMS for Firestore like Rowy.io & FireCMS
3 votes -
Daily usage limitation chart
We were keep getting the Firestore Quota message tough the usage was just 2% in our billing.
After reaching out to the Firebase team, we found out that there are also daily limitations for each action (Read, Write,..) that was hidden in google cloud console.The suggestion is to make the daily limitation chart visible in Firebase, as this error is effecting the users directly.
3 votes -
request.query security rules
currently security rules can only check, "limit, orderby and offset" properties of "request.query" object. if they could check our own custom properties , for example, when users search a collection by id, and I only want them to see a list of documents which contain their id then i should be able to do this in the rules
posts/{postId} {
list: if request.query.id == request.auth.uid
}
- this would be really beautiful and makes it way easy to secure list request.3 votes -
provide feedback on database restore progress
During a restore, there's no way to know how long it will take or where the progress is. It would be great to have some visibility into the process.
I initiated a restore from a backup created by the automated schedules
gcloud alpha firestore databases restore \
--source-backup=projects/PROJECTID/locations/LOCATION/backups/BACKUPID \
--destination-database='DATABASE_ID'I have seen this take between 20 minutes to over a day.
The documentation for this feature is here:
3 votes -
Firestore: Use C++ implementation directly from Swift
Swift has recently gained direct interoperability with C++.
This would allow the current bridging layer written in Objective-C++ to be removed, which would in turn make it possible to use Firestore from Swift cross platform.The Browser Company have created patches for firebase-cpp-sdk to allow this:
https://github.com/thebrowsercompany/swift-firebase
It could also decrease the maintenance burden by removing the bridging layer code.
3 votes -
Provide a way to document and share models across platforms.
Afaik there is currently no standard way to a) document the structure and organization of Firestore collections and documents stored in a project expected by apps which use it, and b) share the model definition across languages and platforms. Instead, each client requires its own implementation of the app-specific model and conversion to/from Firestore's model which needs to be kept up-to-date as the system involves.
If there were a way to share this model (for ex. proto, JSON schema, other) and easily use it from Firestore APIs, it would reduce dev and maintenance cost and improve developer experience.
3 votes -
3 votes
-
How to reduce reads for static data
I want to ask documentation on how to reduce the number of unnecessary reads. eg. my product data
let query = store.collection("products");
Assuming I have 500 products, one user click on get products = 500 reads ? If 100 users click that function, then all my quota is gone in 1 minute. Is that right?
How can I overcome this.
Please provide a full example. I have seen Mr Duckworth's presentation in a firebase event, but could not see a good example.
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 -
3 votes
-
3 votes
-
3 votes
-
Improve firestore rules debug info
Improve firestore rules debug info:
2 features will really improve the debugging of firestore rules:
- Add a "label" parameter to the debug() function to identify the result in the debug log file of the emulator. Right now, only the value is printed, it is very confusing when you have several debug calls...
- Improve the error message returned to the client so we can understand the permission denied. Right now the message contains very little information and it is not helpful a all..,2 votes -
Put the collection name in the beginning of the page title of the Firebase web console
Right now it goes "Project Name - Database - Data - Firebase console" which can get confusing when i have multiple tabs open.
2 votes
- Don't see your idea?