chatmail
Trigger transport resync when default transport is changed
With version 2.33.0 transports are synchronized, but when default transport is changed by setting configured_addr, transport is not changed on the other device, so different devices use different transport for sending.
Sending any sync message, e.g. pinning a chat, results in synchronizing the default transport, but otherwise the transport stays the same.
The solution is to send the transports immediately. It is not really necessary to send transports, but does not hurt and may help if previously transport sync was lost.
I just tested this with 2 desktop instances running core 2.34.0 with a shared profile. If I add a relay in instance A I see the added relay in instance B. But if I change the default relay in A it still shows the old default in instance B.
I also tried switching to another profile and back on instance B to make sure it was not just cached in desktop.
I have just tested between my Android and desktop, synchronization of default relay works for me. And we have a test checked by CI.
Could you check that about dialog shows core 2.34.0 in desktop? Maybe need to run pnpm install or you have DELTA_CHAT_RPC_SERVER set?