- SDK Version: 3.19.2
- Platforms(Android/iOS/web/all): all
I am building a mobile app using Firestore. I’m noticing that when I do a hard refresh (and maybe even a hot reload) that it appears to cause more document reads from the Cloud Firestore database.
I’ve read some stackoverflow questions that indicate there are likely no reads on a hot reload, but hard refreshes of the simulator cause the snapshot listener to disconnect and reconnect initiating a fresh set of reads.
Is that what’s happening? Is there a way to stop extra reads on hard refresh?
Currently I’m using Firestorter as a store, and it claims to handle caching, but the reads seem too high. Though if a hard refresh causes the snapshot listener to disconnect and reconnect, maybe that’s the problem?