Krzysztof kuhy Rudnicki feaaf69103 Accept an empty password when parsing a stored Firebase account ... Both the Google one-tap path and the seeded-session path deliberately write `FirebaseAccount(email: ..., password: '')` -- on those devices the refresh token in the keystore is the credential, and there is no password to store. `tryParse` rejected exactly that blob. So a device signed in with Google wrote an account marker it could never read back: every later launch saw "not configured", fell through to the mirror, and left a perfectly good refresh token unused in the keystore beside it. Only widens what parses, so no caller that previously got an account back can regress. Every call site already guards `password.isEmpty` and passes null for it -- meaning "no password on this device" -- which is precisely the case this now lets them see. An empty *email* stays rejected: it carries no identity at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CFSGeWxHPY5rHUGrPqhcmG		2026-08-22 17:19:49 +02:00
..
src	Accept an empty password when parsing a stored Firebase account	2026-08-22 17:19:49 +02:00
crdt_sync_io.dart	Add LogStore local-persistence layer to crdt_sync (v0.2.0)	2026-07-11 22:19:34 +02:00
crdt_sync.dart	crdt_sync_dart: split four library files — package now under the cap	2026-08-22 15:36:03 +02:00