#502 Offline messages are not handled properly with mod_smacks enabled
Reporter
pravi.a
Owner
Nobody
Created
Updated
Stars
★★ (3)
Tags
Priority-Medium
Status-Duplicate
Type-Defect
pravi.a
on
*What steps will reproduce the problem?*
1. Enable OpenPGP in Conversations client on Android
2. Start chatting with a contact
3. Logout from one of the clients
*What is the expected output? What do you see instead?*
The messages send should be accepted as offline messages, but get delivery failed on conversations.
*What version of the product are you using? On what operating system?*
This is running on poddery.com https://xmpp.net/result.php?domain=poddery.com&type=server
Client is Conversations 1.4.3 on Cyanogen Mod 12 (android 5.0)
*Please provide any additional information below.*
This would be very helpful to have asynchronous encrypted messaging (OTR needs a live session)
fayad.fami
on
I can confirm this. Attaching screenshot to this report that shows failed messages.
http://conversations.im/#support says server returns messages if client can’t reconnect in 5 minutes. I think it should be kept as offline messages and delivered when the client reconnects. The server can reply "message stored for later delivery".
*What steps will reproduce the problem?* 1. Enable OpenPGP in Conversations client on Android 2. Start chatting with a contact 3. Logout from one of the clients *What is the expected output? What do you see instead?* The messages send should be accepted as offline messages, but get delivery failed on conversations. *What version of the product are you using? On what operating system?* This is running on poddery.com https://xmpp.net/result.php?domain=poddery.com&type=server Client is Conversations 1.4.3 on Cyanogen Mod 12 (android 5.0) *Please provide any additional information below.* This would be very helpful to have asynchronous encrypted messaging (OTR needs a live session)
I can confirm this. Attaching screenshot to this report that shows failed messages.
Attachmentshttp://conversations.im/#support says server returns messages if client can’t reconnect in 5 minutes. I think it should be kept as offline messages and delivered when the client reconnects. The server can reply "message stored for later delivery".
See #383
Changes