Skip to content
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

Bad state: Future already completed on client.getFeatureFlags call #36

Closed
momrak opened this issue Jun 17, 2022 · 2 comments
Closed

Bad state: Future already completed on client.getFeatureFlags call #36

momrak opened this issue Jun 17, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@momrak
Copy link

momrak commented Jun 17, 2022

This line seems to cause an error at our side. (see attached image)
await _client.getFeatureFlags(user: Identity(identifier: id), reload: true);
When I remove the line there is no error. Is this something you have seen before, or have any idea what it could be?

This is how we init the client

    try {
      await _client.initialize();
      await _client.updateTraits(value: traits);
      await _client.getFeatureFlags(user: Identity(identifier: id), reload: true);
      _ready = true;
    } catch (e, s) {
      _logger.warn('failed to init feature flag client', stacktrace: s, payload: {'error': e});
    }

image

@dabeeeenster dabeeeenster added the bug Something isn't working label Jun 17, 2022
@dabeeeenster
Copy link
Collaborator

Thanks @momrak - we're looking into this

@jackforesightmobile
Copy link
Collaborator

Hi @momrak, I've investigated this and I don't think the issue is on our end. It seems to be an issue with the Dio package that we have as a dependency.

cfug/dio#1480
cfug/dio#1497

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants