fix: preserve keepSynced state across Query.get - #8544
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
Have the internal
SyncTree.keepSyncedoperation report whether the requested transition actually added a registration, while retaining idempotent behavior for ordinary publickeepSyncedcalls. CallingkeepSynced(true)andget()on the same Realtime Database query can corrupt the SDK's internal keep-synced bookkeeping after the server response is applied.With persistence disabled and no cached data, call
keepSynced(true), awaitget(), callkeepSynced(true)again for the same path, and await anotherget(); both tasks return the server value without a duplicate-listen assertion; Repeat the second synchronization and read through a newly createdDatabaseReferencefor the same path to verify deduplication followsQuerySpecidentity rather than Java object identity.Fixes #8433