using autocrypt setup message to add a 2nd device breaks verified group

[clayt0nk]

• Operating System (Linux/Mac/Windows/iOS/Android): Linux
• Delta Chat Version: 1.3.2
• Expected behavior:

I have two devices (one mobile, one desktop) on the same account, and one verified group. If I invite someone to the verified group with a QR code from the mobile device, this should transparently just work for both of my devices.

• Actual behavior:

My invited friend must actually process two QR code invites, one from my mobile and one from my desktop, before both devices will work.

After my friend accepts the first invite from my mobile, everything looks perfect on my mobile (the source of the invite QR code) but desktop can no longer send to the verified group, in the desktop log I thereafter get this

"DC_EVENT_ERROR Failed to send message: proper enc-key for someone@somedomain.com missing, cannot encrypt"

error in the desktop log every time I try to send to the verified group from desktop.

• Steps to reproduce the problem:

Login with desktop DC
Login with Android DC and "Send Autocrypt Setup Message" to synchronize device keys between Android and desktop
Create new verified group
On my Android, invite friend to verified group with QR code on his desktop DC
Observe everything works great on my Android and friends desktop
On my desktop, observe above encryption error / failure to send any further messages in verified group
On my desktop DC, generate a QR code invite for friend's desktop DC
Observe on my desktop DC, my Android DC, friend's desktop DC: everything now works.

[Jikstra]

Exchanging the private key with autocrypt setup message is sadly not enough to sync verified groups/contacts. You should start on one device with an imported backup of the other device to get the initial peerstate right :/

[clayt0nk]

Yes, what you suggest (imported backup instead of autocrypt setup message on new devices) seems to work so far (stay tuned for further testing) but for me at least it is not straight-forward. My desktop has a permanent VPN connection to my mail server, my Androids do not. So after importing the desktop backup on mobile, I had to scratch my head for some time trying to figure out why it did not "just work". I needed to go into advanced settings after the backup restore to change the IMAP server from the VPN IP to a normal domain name / DNS.

Anyway, what seems obvious to me, is that when your UI contains two functions (in this case, "autocrypt setup message" & "verified groups") where using the former effectively breaks the latter, one still has a bug. Either one of the functions needs to fixed, or one of them needs to be removed. Pushing some random button in the UI should not render other parts unusable.

[Hocuri]

I think adding a second device needs some general rethinking, I'll open a separate issue for this.

[hpk42]

Many of us are well aware that multi-device setups need more work ... as do many other areas btw. Please avoid getting to upset (CAPS letters etc.). It doesn't help. Thanks.

[clayt0nk]

as do many other areas btw

On the subject of bugginess, this new-ish user thinks DC works very well already, aside from the issue reported here

[hpk42]

@clayt0nk good to hear :) The ASM (autocrypt-setup message) falls very short of helping to synchronize DC -- in fact transfering the private key probably better becomes an "advanced option". Maybe we could introduce an "synchronize to another device" option but for now only point to a web page / FAQ and/or tell the user that they need to export/transfer/import. It is an often recurring UX problem and people get caught in a buggy quagmire otherwise.

…

On Sat, Jun 13, 2020 at 18:36 -0700, clayt0nk wrote: > as do many other areas btw On the subject of bugginess, this new-ish user thinks DC works very well already, aside from the issue reported here -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #1597 (comment)

[clayt0nk]

I think userland would definitely appreciate a detailed FAQ on the lay of the land here until the UX settles on a straight-forward process, as the other option is flailing around with time-consuming trial and error

[r10s]

i think we can close this issue, i do not see an actionable item for ASM, which is also meant to maintain compatibility with other non-Delta-MUA.

good new: a better onboarding for multi-device-setup is approaching and discussed at #1731