Ehsan

Once https://github.com/firebase/firebase-js-sdk/issues/7711 is resolved, we can implement the same solution here.

This only happens if the query result set is _very_ large; so large that it would get the `UNAVAILABLE after 60 sec` error (as described in https://github.com/googleapis/nodejs-firestore/issues/964. To address this,...

For the time being, if such consistency guarantee _is not needed_ by the developer (or if they know the data is _not_ fast changing), one could manually paginate these requests...

Thanks for the recommendation @ZLY201 . We will take it into consideration.

Thanks for reporting @sergiocampama. I will start looking into this. In the meantime, if there has been any developments over the past few weeks, please provide an update here. Thanks

Thanks @sergiocampama . I'm sorry to hear about the inconvenience. I've been trying to find meaningful pointers to look into from the crash report, but there's nothing that can point...

Thanks for reporting @fkolar and for providing a reproduction repository.

Thanks for reporting @vojto . Can you point me to the repo that I can clone to reproduce?

Thanks for the Loom, @vojto. It appears to be an IndexedDB bug. We could try to confirm this by using a different iOS version [perhaps using the iOS simulator?]

Thanks for reporting @asaadjaber. Have you installed the [@firebase/rules-unit testing](https://www.npmjs.com/package/@firebase/rules-unit-testing) package in addition to the firebase package? I see the RulesTestEnvironment [exported](https://github.com/firebase/firebase-js-sdk/blob/3f8cbcd18f47fcae8c0d8060fd8c245c025784c0/packages/rules-unit-testing/src/public_types/index.ts#L159).