Closed florianbaethge closed 4 years ago
Thanks for reporting!
Please, expect some news here. I will take this topic up, as soon as possible ;)
Please check the latest version 1.3.6 - that should help.
If I may be honest, I haven't reproduced your issue, but I think I found the reason. "Query state" was cleaned up after firebase execution. In case of concurrent calls (like data change listening + read value once), that probably had caused problems.
@florianbaethge have you checked if the latest version works for you :)?
Hi,
sorry for not writing back. I've upgraded the version and tried it. Works for me :) Thank you!
Describe the bug I've just tried to perform several database fetch calls, but it seems that the database instance somehow keeps the filters made on another query.
When I change the order of the queries and fetch the one without filters first, it works! But if the fetch without filter or orderBy settings is called after the other one, it crashes with an IllegalStateException:
To Reproduce
If you change the order of the queries (move the whole
val promise = ...
part above the rest, it works.Expected behavior Calls should work in any order. First call should answer with a list of Highscores, second one an individual one, if the uid has a highscore in the database...
Platform (please check one of the following):
Smartphone (please complete the following information only if platform is Android or iOS):