ars/iiEsaywebUIapp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(server): Improve server health checks and authentication flow

Browse Source
This commit is contained in:
cogwheel0
2025-11-26 15:25:02 +05:30
parent 9b69290589
commit 44d1cc99b4
7 changed files with 166 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
lib/core/widgets/error_boundary.dart
View File

@@ -32,10 +32,18 @@ class _ErrorBoundaryState extends ConsumerState<ErrorBoundary> {
void Function(FlutterErrorDetails details)? _previousOnError;
bool _shouldIgnoreError(Object error) {
// Ignore RenderFlex overflow errors (layout issues)
final errorString = error.toString();
return errorString.contains('RenderFlex') ||
errorString.contains('overflow') && errorString.contains('pixels');
// Ignore RenderFlex overflow errors (layout issues)
if (errorString.contains('RenderFlex') ||
errorString.contains('overflow') && errorString.contains('pixels')) {
return true;
}
// Ignore "Build scheduled during frame" errors - these are harmless
// framework warnings from animations during layout
if (errorString.contains('Build scheduled during frame')) {
return true;
}
return false;
}
void _scheduleHandleError(Object error, StackTrace? stack) {
@@ -59,6 +67,10 @@ class _ErrorBoundaryState extends ConsumerState<ErrorBoundary> {
// Set up Flutter error handling for this widget
_previousOnError = FlutterError.onError;
FlutterError.onError = (FlutterErrorDetails details) {
// Check if this is a harmless error we should completely ignore
if (_shouldIgnoreError(details.exception)) {
return; // Don't forward or handle
}
// Forward to any previously registered handler to avoid interfering
_previousOnError?.call(details);
// Defer handling to avoid setState during build