Repository navigation
[firebase_remote_config] RemoteConfig.instance Future already completed #120
Description
Activity
Here is the MCVE: https://gist.github.com/IchordeDionysos/849d1ec5ec409487f1f2640c9c806e9f
If you run it in Debug mode you'll stop at theFuture already completeerror.Of course, this example seems a bit useless, but consider the second
RemoteConfig.instancebeing called somewhere else in the source code independent from the first call.Facing the same issue
Unhandled Exception: Bad state: Future already completedif running:
final RemoteConfig remoteConfig = await RemoteConfig.instance;multiple times in parent-child widgets at the same time. Any workarounds?Facing the same issue
Unhandled Exception: Bad state: Future already completedif running:
final RemoteConfig remoteConfig = await RemoteConfig.instance;multiple times in parent-child widgets at the same time. Any workarounds?Same issue here
☹️ - addedimpact: crowdAffects many people, though not necessarily a specific customer with an assigned label. (P2)Affects many people, though not necessarily a specific customer with an assigned label. (P2)
on Apr 23, 2020 this problem occurs only when i am using MVC architecture.
I have the same problem.
I'm experiencing the same problem!
Given the age of this issue and that Remote Config has had a major rework since; I'm going to close this issue in favour of trying the latest release.
Ah yes, forgot to close this issue.
This is definitely fixed with the new version!
- locked and limited conversation to collaborators
on May 2, 2021
Describe the bug
When calling RemoteConfig.instance twice both of these calls go into the if-statement and try to retrieve the instance.
Then in here both calls to get RemoteConfig.instance try to complete with the instance, but the second one fails as the first one already completed the Completer.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Both calles to
RemoteConfig.instancecomplete without an errorAdditional context
I'll put together an MVCE