-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firebase Database GET request changes its response when you listen to the parent node's data #12225
Comments
Hi @russellwheatley , |
@maneesht |
@mortenbekditlevsen Sorry about the slow progress. After some investigation, the full fix is more challenging than we hoped and we don't have an ETA. |
No worries - I only spotted this one specific issue, so that's all I focused on in the PR. |
If there's anything I can do to help you out, by the way, please let me know! 😊 |
Hi all, I'm in the same situation. If you need any information I will be glad to provide it to you. 😊 |
Description
Firebase Database GET request changes its response when you listen to the parent node's data. It should not change and should always reflect the data on the path of the Firebase Database.
Discovered based on an old issue opened a year ago: firebase/flutterfire#10145
So this is a longstanding bug in the Firebase iOS SDK.
Reproducing the issue
I have created a reproduction repo for you to follow: https://github.com/invertase/database-ios-bug
The instructions are in the README, here they are for clarity:
GoogleService-Info.plist
to this project.pod install
in the root of the project.The response changes after observing the parent nodes data.
Firebase SDK Version
10.19
Xcode Version
15.2
Installation Method
CocoaPods
Firebase Product(s)
Database
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetThe text was updated successfully, but these errors were encountered: