Linus Rath 153e85cb80 fix: finish turning sync off when the app goes to the background #34 ...

Turning sync off first uploads what the device changed, then removes
the synced rows. Started from the settings screen, that work yielded
the JS thread with timers between its steps, and React Native pauses
timers while the app is in the background and no headless task runs:
leaving the app stopped it halfway, holding the account's sync lock,
until the app came back. The teardown now waits without timers.

2026-09-27 07:53:37 +02:00

..

__tests__

fix: finish turning sync off when the app goes to the background #34

2026-09-27 07:53:37 +02:00

app

fix: let the user delete or restore held-back deletions from the sync settings #34

2026-09-27 07:19:26 +02:00

calendar

fix: keep syncing a big meeting after it was edited on the phone #34

2026-09-27 07:10:47 +02:00

common

test: add a fake device provider and jmap server for the sync tests #34

2026-09-27 02:53:22 +02:00

contacts

fix: keep the groups of a contact created on the device #34

2026-09-27 07:19:27 +02:00

engine

fix: finish turning sync off when the app goes to the background #34

2026-09-27 07:53:37 +02:00

jmap

fix: sync only the primary account's collections by default #34

2026-09-27 07:53:36 +02:00

android-columns.ts

feat: map calendars and events to android's calendar provider #34

2026-09-27 04:21:30 +02:00

native.ts

feat: give device sync scoped access to the contacts and calendar providers #34

2026-09-27 04:04:00 +02:00

planner.ts

fix: stop reading the read-only flag the contacts provider never returns #34

2026-09-27 05:07:58 +02:00

task.ts

feat: map contacts and groups to android's contacts provider #34

2026-09-27 04:23:22 +02:00

types.ts

feat: give device sync scoped access to the contacts and calendar providers #34

2026-09-27 04:04:00 +02:00

wire.ts

test: add a fake device provider and jmap server for the sync tests #34

2026-09-27 02:53:22 +02:00