Denver Coneybeare
Denver Coneybeare
Hi @KoryNunn. I noticed that you've reported this issue against v8.10.1. We are no longer making releases of the v8 SDK, except in the case of emergency security vulnerabilities (e.g....
Hi @KoryNunn. If you continue using v8 then there isn't anything I can do to help. Your option would be to maintain your own fork with the required patches. This...
Thank you for the information, @KoryNunn. I've changed this issue to a feature request since this sounds like a reasonable thing for the API to expose. I've also logged b/243138668...
Hi @jorroll. Thank you for taking the time make a thorough bug report. I'll take a look.
I've been able to reproduce this issue for myself using a much simpler repro app: https://github.com/dconeybe/FirestoreJsIssue6511. There is definitely a bug here and I'll dig into it further.
@jorroll Through bisection, it appears that this bug was introduced in v9.6.10. Could you try downgrading to v9.6.9 and see if that fixes this bug for you, as a temporary...
One workaround that came to mind would be to add a field to the documents with the value `serverTimestamp()`. And every time you update that document you also set it...
@jorroll Thanks for confirming that downgrading to 9.6.9 fixes the bug for you. You are right that deploying a new version of your app that downgrades from 9.9.2 to 9.6.9...
Just an update that investigation is continuing. No updates yet (I've just returned from vacation).
Hello @anisabboud. I am working with the AppCheck team to investigate. I'll reply back once I have any updates. The 403 error that you're seeing means that Firestore SDK has...