You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys, I just tried to see if the new dio v4.0.6 resolved the issue mentioned in your documentation https://docs.flagsmith.com/clients/flutter#known-issues
"If using the package Dio, you may encounter an error saying Bad state: Future already completed. There is a bug in the Dio package, introduced in 4.0.5 (and as of writing this on 12/09/2022, is unresolved). To resolve, you'll need to pin your Dio version in pubspec.yaml to 4.0.4 or earlier."
Unfortunately this is not the case.
I'll attach my test results as screenshots.
I reproduced it easily, by just locking the dio version in the sdk itself & in the example application.
Then start it for web - see if the error occurs.
Here you can see the result with different version - 4.0.4, 4.0.5, 4.0.6
Web state with dio 4.0.4
Web state with dio 4.0.5
Web state with upgrading dio to 4.0.6
The text was updated successfully, but these errors were encountered:
jdde
added a commit
to jdde/flagsmith-flutter-client
that referenced
this issue
Nov 30, 2022
* - locked dio version, to make sure flagsmith is compatible to dio
- see #45
* - re-executed "flutter pub get" to not use the non-working version 4.0.6 in the example - the example throws errors.
Hi guys, I just tried to see if the new dio v4.0.6 resolved the issue mentioned in your documentation https://docs.flagsmith.com/clients/flutter#known-issues
"If using the package Dio, you may encounter an error saying Bad state: Future already completed. There is a bug in the Dio package, introduced in 4.0.5 (and as of writing this on 12/09/2022, is unresolved). To resolve, you'll need to pin your Dio version in pubspec.yaml to 4.0.4 or earlier."
Unfortunately this is not the case.
I'll attach my test results as screenshots.
I reproduced it easily, by just locking the dio version in the sdk itself & in the example application.
Then start it for web - see if the error occurs.
Here you can see the result with different version - 4.0.4, 4.0.5, 4.0.6
Web state with dio 4.0.4
![dio_4_0_4](https://user-images.githubusercontent.com/10098106/204753166-8b37fd7c-78c4-4f29-9d2b-993fcd17ca7e.png)
Web state with dio 4.0.5
![dio_4_0_5](https://user-images.githubusercontent.com/10098106/204753197-561c9e6b-37ea-4464-b00c-ca0c62ecd353.png)
Web state with upgrading dio to 4.0.6
![dio_4_0_6](https://user-images.githubusercontent.com/10098106/204753222-0d437ff6-abb6-4a6f-8e97-32932e02b7b9.png)
The text was updated successfully, but these errors were encountered: