[firebase_remote_config] RemoteConfig.instance Future already completed

[IchordeDionysos]

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:

1. Install and configure Remote Config
2. Get RemoteConfig.instance twice in parallel
3. See that the second call will fail with Bad state: Future already completed

Expected behavior
Both calles to RemoteConfig.instance complete without an error

Additional context

I'll put together an MVCE

[IchordeDionysos]

Here is the MCVE: https://gist.github.com/IchordeDionysos/849d1ec5ec409487f1f2640c9c806e9f
If you run it in Debug mode you'll stop at the Future already complete error.

Of course, this example seems a bit useless, but consider the second RemoteConfig.instance being called somewhere else in the source code independent from the first call.

[mayurdhurpate]

Facing the same issue Unhandled Exception: Bad state: Future already completed if running:
final RemoteConfig remoteConfig = await RemoteConfig.instance; multiple times in parent-child widgets at the same time. Any workarounds?

[stepankuzmin]

Facing the same issue Unhandled Exception: Bad state: Future already completed if running:
final RemoteConfig remoteConfig = await RemoteConfig.instance; multiple times in parent-child widgets at the same time. Any workarounds?

Same issue here ☹️

[Praveen-Pandiyan]

this problem occurs only when i am using MVC architecture.

[michaldev]

I have the same problem.

[albertpurnama]

I'm experiencing the same problem!

[Salakar]

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.

[IchordeDionysos]

Ah yes, forgot to close this issue.

This is definitely fixed with the new version!