Janez T 01fbb7de6c
fix: Profile duplication on device connect ...
DeviceKey resolver was falling back to deviceId when publicKey wasn't
yet available during early connection. This created two different keys
(id:xxx then pk:yyy) for the same device, causing a new profile to be
created each time.
Now returns null until publicKey is available, so profile sync waits
for the stable identifier.
2026-03-18 14:45:55 +01:00
2026-03-17 14:43:47 +01:00
2026-03-16 11:25:51 +01:00
2026-03-16 11:25:51 +01:00
2026-03-09 19:23:35 +01:00
2026-03-15 20:14:01 +01:00
2026-03-12 14:39:44 +01:00
2026-03-17 09:44:38 +01:00
2026-03-08 14:26:05 +01:00
2026-03-16 11:25:51 +01:00
2026-02-28 10:11:33 +01:00
2026-03-02 09:42:14 +01:00
2026-03-16 11:25:51 +01:00
2026-03-13 10:16:04 +01:00
2026-03-08 20:46:09 +01:00
2026-03-16 11:25:51 +01:00
2026-03-17 11:08:56 +01:00
2026-03-16 11:25:51 +01:00
2026-03-16 22:16:36 +01:00
2026-03-08 20:22:10 +01:00
2026-03-16 11:25:51 +01:00
2026-03-16 11:25:51 +01:00
2026-03-08 14:26:05 +01:00
2026-03-04 19:11:16 +01:00
2026-03-15 09:13:32 +01:00
2026-03-09 19:59:29 +01:00
2026-03-12 20:54:04 +01:00
2026-03-18 14:45:55 +01:00
2026-03-18 14:29:33 +01:00
2026-03-16 11:25:51 +01:00
2026-03-18 14:29:33 +01:00
2026-03-18 14:29:33 +01:00
2026-03-17 09:44:38 +01:00
2026-03-17 09:44:38 +01:00
2026-02-28 10:11:33 +01:00
2026-02-28 10:11:33 +01:00
2026-03-05 08:05:55 +01:00
2026-02-28 10:11:33 +01:00
2026-03-16 11:25:51 +01:00
2026-03-12 20:12:25 +01:00
2026-03-12 20:12:25 +01:00
2026-03-04 19:19:40 +01:00
2026-03-11 21:16:08 +01:00
2026-03-12 20:12:25 +01:00
2026-02-28 10:11:33 +01:00
2026-02-28 10:11:33 +01:00
01fbb7de6c