Can't initiate OMEMO with Conversations

[woj-tek]

(From Conversations MUC)

Describe the bug

[2019-12-03 21:11:57] Wojtek: Stork can't initiate OMEMO, luckly C can [2019-12-03 21:13:32] Wojtek: not the same user, just the same avatar

Screenshots

In https://github.com/tigase/stork/issues/2#issuecomment-561606708

Smartphone (please complete the following information):

• Device: Xiaomi
• OS: MIUI11 Android 10
• Version: 3.0.23.p
• Accounts servers: ejabberd HEAD

[licaon-kter]

Xiaomi MIUI11 Android 10 3.0.23.p ejabberd HEAD

[joergister]

This Problem does still exist as of today on the iOS client, but I wasn't quite able to figure out why it sometimes occurs. I don't know if it still is on the android client, since I don't have a test device.

[licaon-kter]

It's better in 3.0.25

[woj-tek]

@licaon-kter "better" as in fixed completely or with still occasional hiccups?

[licaon-kter]

Worked as I tested... This needs more that one measly "better" from one user :))

[woj-tek]

Exactly, ideally with more details/data :-)

I just checked a couple of things (slightly older report related to OMEMO/PEP) and that issue is also gone.

[joergister]

it may be on android, but is sure is still in place on iOS

[woj-tek]

Please provide more details: from which client you try to initiate it? What version? What server/account?

Please note that this issue/project relates to StorkIM (Android client). SiskinIM related issue should be reported here: github.com/tigase/siskin-im/

[joergister]

I will, but I haven't quite figured out all the details as of now (when does the message appear for example, because it doesn't always and stuff like that) and didn't want to give useless bug report. I will then open an issue for siskin.