mirror of
https://github.com/yattee/yattee.git
synced 2026-10-23 13:12:53 +00:00
ca73b68ad9
Foreground activation started identity resolution, the deletion repair and the CloudKit fetch as three things racing each other. With a tombstone for the selected account already on disk and a sibling login on the same server whose status had not been read back yet, the repair ran against `checking` — which it will not repair onto — and landed on local. It commits, so the status refresh arriving a moment later changed nothing: the selection no longer named an account for a second repair to act on. The steps now run as one sequence in both platform paths, because each one is what makes the next correct: the identity says whose accounts these are, the status refresh says which of them this device can use, the repair reads those statuses, and the fetch goes last so a deletion it delivers repairs against the same refreshed picture.