Firestore requests tab is unordered making it mostly unusable
See original GitHub issueThe requests list at /firestore/requests
is unordered. This makes it mostly unusable as it’s very hard to find new requests as they happen. The page should be ordered by timestamp.
firebase-tools: 9.16.6 platform: MacOS arm64 (M1) 11.5.2 browser: Firefox 92.0b6
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Best practices for Cloud Firestore - Firebase
The following best practices describe how to avoid situations that create contention issues. Updates to a single document. As you design your app,...
Read more >Why is "Content Downloaded" in the network tab over a ...
1 Answer. Save this answer. Show activity on this post. The Firestore JavaScript SDK uses web channel as its protocol for talking to...
Read more >How to fix Firestore Error: PERMISSION_DENIED - Medium
A simple solution for handling Firestore error. That's by far the most common and annoying error that you can get when you try...
Read more >Error: Firestore: The service is currently unavailable ... - GitHub
It's strange because its not reproducible when the app lost the connection. But suddenly it comes online again. In the most case after...
Read more >Firestore Security Rules - How to Hack a Firebase App
Learn how to hack a Firebase app, then configure solid Firestore Database security rules to ensure data integrity.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for looking into this, @cristianberroeta! There are two separate issues here. First, as you’ve observed, the top-level
time
field should be used. This should fix the display on the list view discovered by OP @AndrewMorsillo.There’s still an underlying issue as to why
rulesContext.time
is in the past for the third request, which we’re looking into right now internally. That part is within the Firestore Emulator, which is not open source.no problem @yuchenshi.
I also noticed that if you follow these steps:
then these are the logged requests:![image](https://user-images.githubusercontent.com/17519897/132422682-78f0a753-9858-40fc-b7a7-0bca35f44710.png)
I’m not sure if that is the expected behavior, but if you have a website in which you don’t clean the listeners and your page is reloaded multiple times, then you can apparently end up with multiple GET requests being sent after an UPDATE, like this:![image](https://user-images.githubusercontent.com/17519897/132423004-42a084d7-3a5a-4bdb-835d-0848af1013be.png)
In this case, I did the “start listening - refresh” sequence 8 times, and then pressed the button to update, which generated an UPDATE request, followed by 8 GET requests.