Repository navigation
Improve API error handling and user recovery - #376
Merged
Merged
Conversation
jakobkoerber
marked this pull request as ready for review
November 7, 2026 21:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Several API-to-UI paths lose the original failure, discard its source stack, leave dependent streams loading, or report a mutation as complete before its request finishes. Some cards also replace real failures with a generic Error, and the custom gRPC cache bridge can leave rejected calls unresolved.
Why this is useful for all students
Users see localized, actionable error messages while the original exception and source stack remain available for diagnosis. Shared Campus collection views and floating snackbars retain the same error metadata and recovery policy. Recoverable reads offer Retry, invalid TUMonline tokens retain Login, and ambiguous submissions advise checking the outcome before submitting again. Large-text explanations wrap and scroll.
Unverified TUMonline error strings retain the generic fallback. EFA-specific error envelopes still require verified fixtures. Read-only production probes returned HTTP 404 for News and movies; correcting client error handling does not repair that service/deployment issue.
Release target
Target version: 5.4.1 (
5.4.1+1is already set in pubspec). The latest published release is v5.4.0. This is a compatibility-preserving bug-fix release; no release tag or store publication is created by this PR.Refresh 12 compatible direct/transitive packages, including SQLite 3.9.1, Flutter Riverpod 3.5.0, and GoRouter 18.1.3. Retain the current Flutter/Dart baseline and dependency overrides. Packages requiring incompatible constraint changes remain outside this patch release. A fresh SQLite 3.9.1 macOS native download passes its checksum verification locally.
Screenshot
No screenshots attached. Widget tests exercise every card error path, recovery actions, empty states, large text, short layouts, and calendar submission failures.
Validation
flutter test --no-pub: 380 tests passed in the main checkout after merging current main.flutter analyze --no-pub: no issues found.git diff --check: passed.The audit remains excluded. The resolved merge preserves current main’s Campus UI, floating snackbars, login announcements, and location-permission onboarding. No live authenticated or mutation API calls were used for validation.