darken 04c23ecf63 fix(ble): Prefer case-context pod when merging split BLE broadcasts ...

When both pods broadcast independently (one in case, one on desk), the pod inside the case carries authoritative case state via hasCaseContext bits. Previously, whichever address was processed last would overwrite the other, causing case state to flip-flop between OPEN and NOT_IN_CASE every scan cycle.

Two-layer fix: BlePodMonitor.processWithCache() now prefers the pod with case context when two scan results map to the same identity in one batch. ApplePodsFactory.getLatestCaseLidState() no longer treats NOT_IN_CASE as authoritative when recent history contains a broadcast with case context.

2026-04-14 11:28:41 +02:00

..

proguard

refactor: Replace Moshi with kotlinx.serialization

2026-03-09 20:29:19 +00:00

src

fix(ble): Prefer case-context pod when merging split BLE broadcasts

2026-04-14 11:28:41 +02:00

.gitignore

Refactoring

2022-09-14 18:00:18 +02:00

build.gradle.kts

refactor: Replace Moshi with kotlinx.serialization

2026-03-09 20:29:19 +00:00

proguard-rules-debug.pro

Refactoring

2022-09-14 18:00:18 +02:00