Krzysztof kuhy Rudnicki db3d8f827f Let a host explain an absent Google button instead of hiding it ... lyricanki's Linux desktop cannot use google_sign_in (no Linux implementation) and its loopback replacement is dark until a Desktop OAuth client exists. Hiding the button there makes the screen silently offer less on one platform, which reads as a bug. googleUnavailableReason renders a *disabled* button plus the reason. That is not the "control that can never succeed" trap: the trap is a live-looking button that reports a fake cancellation, and a null onPressed cannot be tapped at all. Null stays the default, so every existing host is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CFSGeWxHPY5rHUGrPqhcmG		2026-08-22 19:03:24 +02:00
..
backup_slot_test.dart	Add sync_settings_ui: shared Firebase-only sync settings screen	2026-08-12 23:10:17 +02:00
firebase_sync_controller_test.dart	Add sync_settings_ui: shared Firebase-only sync settings screen	2026-08-12 23:10:17 +02:00
sync_settings_screen_backup_test.dart	dart: split ten oversized test files by group	2026-08-22 14:54:35 +02:00
sync_settings_screen_google_test.dart	Let a host explain an absent Google button instead of hiding it	2026-08-22 19:03:24 +02:00
sync_settings_screen_test.dart	dart: split ten oversized test files by group	2026-08-22 14:54:35 +02:00