Linus Rath eebb00238c fix: look for new mail when a push names changes it can't read #34 ...

The native push router and the push task decided separately whether a
push may carry mail, and disagreed. For an account entry that is not
an object, or a map that names no type, the router started the mail
task as possible mail, but the task's guard read the same payload as
"no mail" and returned, so new mail it announced was never looked for.
A push without a kind was judged by its map in the router but taken
for mail by the task.

Both now apply the same rules: anything but a StateChange, a map that
is missing, unreadable or names no type, an unreadable account entry,
or a mail type means the mail task runs. Only a readable StateChange
naming contact, calendar or other non-mail types skips it.

Checked with one table of payloads run against the router's decision
and the task's guard alike.

2026-09-27 10:20:55 +02:00

..

DeviceSyncAccountsTest.kt

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

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

DeviceSyncRunsTest.kt

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

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

ProviderOpsTest.kt

fix: keep every provider write of device sync inside its own account #34

2026-09-27 06:12:08 +02:00

PushRoutingTest.kt

fix: look for new mail when a push names changes it can't read #34

2026-09-27 10:20:55 +02:00

SyncReportsTest.kt

fix: log why a device sync run failed #34

2026-09-27 05:27:13 +02:00