3 Commits

Author	SHA1	Message	Date
bvandeusen	abf91874c3	Show specific error reason on setup screen connection failure ... Instead of a generic "Could not reach server" for all failures, show the actual cause: SSL cert error, timeout, or the raw connection error message. This makes it possible to diagnose setup issues on-device without needing a debugger. Also extend connect timeout from 5s to 10s. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-01 14:48:49 -05:00
bvandeusen	ccaec61de2	Fix setup screen always rejecting valid servers ... Dio throws DioException for 4xx responses by default, so a server returning 401 on /api/auth/status (correct behaviour for an unauthenticated request) was caught and shown as "Could not reach server", preventing the URL from ever being saved. Set validateStatus: (_) => true so any HTTP response (200, 401, 404…) counts as "reachable". Only actual network failures (no response) now trigger the error message. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-03-01 14:38:01 -05:00
bvandeusen	4da36aa31d	Initial commit: Fabled Android app ... Flutter Android client for FabledAssistant with: - Session-cookie auth via persistent cookie jar (Dio + cookie_jar) - OAuth/SSO login via in-app WebView (flutter_inappwebview) - Notes: list, detail (markdown render), create/edit - Tasks: list with status tabs, create/edit with priority - Chat: SSE streaming bubbles, conversation management - Quick Capture FAB for rapid note/task creation - Settings screen (change server URL, logout) - Android home screen widget → opens chat - Riverpod state management, go_router navigation Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-02-28 21:28:53 -05:00