Flagsmith 6.3 should support newer versions of Dio (or pin to a lower Dio version)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- mobile-dev
Research direction
The compile error points to lib/src/core/events/event_processor.dart around line 375, where a switch on e.type over DioExceptionType lacks a case for transformTimeout. Read that switch and the surrounding error handling, then compare against the DioExceptionType enum in dio's dio_exception.dart. Done means the package analyzes cleanly against dio 5.10 and later, either by adding the missing case or a default branch, with the existing event processor behavior unchanged for other types.
Written by the indexing model from the issue text.
Description
Version 5.10 of Dio added a new DioExceptionType type. Since flagsmith switch (e.type) to match cases, it needs to include the new types:
../../../.pub-cache/hosted/pub.dev/flagsmith-6.3.0/lib/src/core/events/event_processor.dart:375:15: Error: The type 'DioExceptionType' is not exhaustively matched by the switch cases since it doesn't match 'DioExceptionType.transformTimeout'.
- 'DioExceptionType' is from 'package:dio/src/dio_exception.dart' ('../../../.pub-cache/hosted/pub.dev/dio-5.11.1/lib/src/dio_exception.dart').
Try adding a default case or cases that match 'DioExceptionType.transformTimeout'.
switch (e.type) {
^
See also: https://github.com/cfug/dio/issues/2547#issuecomment-4841979338
Alternatively, pin dio to < 5.10.0
Alternatively alternatively, provide a default match.
- Dominant language
- Dart
- Stars
- 17
- Forks
- 18
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Flagsmith/flagsmith-flutter-client
-
Dependency DashboardOpen
Difficulty 1/5 Under an hour Newbie friendliness 25/100
Flagsmith/flagsmith-flutter-client#103 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Flagsmith/flagsmith-flutter-client#93 ·
Maintainers usually reply within 1 day
-
Crashlytics reporting a crash when the user lost the internet connectionPossibly taken @Wreos claimed this 296 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
Flagsmith/flagsmith-flutter-client#63 · 1 comment ·
Maintainers usually reply within 1 day
All issues in Flagsmith/flagsmith-flutter-client
Similar issues
-
documentation good first issue help wanted
Difficulty 2/5 Half a day Newbie friendliness 72/100
Is0cre/MonkeyThrive#6 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
15-minutes 5-minutes algorithm any-language beginner-friendly c cpp csharp easy go good first issue hacktoberfest help wanted java javascript kotlin python rust swift typescript
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Huerte/algo-solutions-python#260 ·
Maintainers usually reply within 1 day
-
Android: a receive link with a query opens Receive empty, without the not-a-code messagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
totaldrop-app/totaldrop#516 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
zjs81/meshcore-open#663 ·
Maintainers usually reply within 1 day