Extremely unstable work, some messages are not delivered, false status online. #622

Open
opened 2 weeks ago by Bread · 3 comments
Bread commented 2 weeks ago

Extremely unstable work, some messages are not delivered, false status online.

General information

  • Version: 3.0.8-playstore
  • Android Version: Android 9 (stock)
  • Server name: thesecure.biz, deshalbfrei.org
  • Server software: -
  • Installed server modules: -
  • Pix-Art Messenger source: PlayStore

Steps to reproduce

  1. Install and login 1 jabber account last version https://psi-plus.com/ in Windows 10.
  2. Install and login 2 jabber account blabber.im 3.0.8.
  3. We check the connection, make sure that the connection is and messages come in both directions.
  4. Restart the smartphone. And start sending several messages from PSI + to Blabber.im.

Expected result

What is the expected output?

  1. What, after restarting the smartphone, the blabber.im will start automatically.
  2. What, when you turn off / restart the smartphone in PSI +, the contact status will be changed to offline.
  3. That messages sent to the reloading smartphone will reach it after rebooting.

Actual result

What do you see instead?

  1. BLABBER.IM does not start automatically after rebooting.
  2. PSI + continues to think that contact online, although the smartphone is already turned off.
  3. Messages sent during the reboot just disappear, as if they were not written.

Debug output

Please post the output of adb logcat. The log should begin with the start of blabber.im and include all the
steps it takes to reproduce the problem.

Linux: adb -d logcat -v time | grep -i blabber.im > logcat.txt
Windows: adb -d logcat -v time | FINDSTR blabber.im > logcat.txt

Message PSI + after a while

Service unavailable.
The server or recipient does not currently provide the requested service.
User session not found

Extremely unstable work, some messages are not delivered, false status online. #### General information * **Version:** 3.0.8-playstore * **Android Version:** Android 9 (stock) * **Server name:** thesecure.biz, deshalbfrei.org * **Server software:** - * **Installed server modules:** - * **Pix-Art Messenger source:** PlayStore #### Steps to reproduce 1. Install and login 1 jabber account last version https://psi-plus.com/ in Windows 10. 2. Install and login 2 jabber account blabber.im 3.0.8. 3. We check the connection, make sure that the connection is and messages come in both directions. 4. Restart the smartphone. And start sending several messages from PSI + to Blabber.im. #### Expected result What is the expected output? 1. What, after restarting the smartphone, the blabber.im will start automatically. 2. What, when you turn off / restart the smartphone in PSI +, the contact status will be changed to offline. 3. That messages sent to the reloading smartphone will reach it after rebooting. #### Actual result What do you see instead? 1. BLABBER.IM does not start automatically after rebooting. 2. PSI + continues to think that contact online, although the smartphone is already turned off. 3. Messages sent during the reboot just disappear, as if they were not written. #### Debug output Please post the output of adb logcat. The log should begin with the start of blabber.im and include all the steps it takes to reproduce the problem. ```` Linux: adb -d logcat -v time | grep -i blabber.im > logcat.txt Windows: adb -d logcat -v time | FINDSTR blabber.im > logcat.txt ```` Message PSI + after a while Service unavailable. The server or recipient does not currently provide the requested service. User session not found ------

Hi,

your main problem is that your server does not support mam.

Please contact the admin and ask for mam support.
If it's your server please load the module

mod_mam

and enable it for mucs too.
(have a look here for help: https://compliance.conversations.im/server/thesecure.biz/ )
This sould solve your second and third issue.

Your first issue should be solved by waiting a moment. Blabber.im should be started after reboot automatically.

Hi, your main problem is that your server does not support mam. Please contact the admin and ask for mam support. If it's your server please load the module ``` mod_mam ``` and enable it for mucs too. (have a look here for help: [https://compliance.conversations.im/server/thesecure.biz/](https://compliance.conversations.im/server/thesecure.biz/) ) This sould solve your second and third issue. Your first issue should be solved by waiting a moment. Blabber.im should be started after reboot automatically.
Poster

Hi! Well, I checked by registering both accounts on deshalbfrei.org on which there is MAM support. The third problem is solved, thanks! The second no, most likely the case in incorrect references of the status when the smartphone is turned off, you should check it, because the status does not change on offline even after 30 minutes (perhaps never), the one who is misleading the interlocutor who thinks that I am online.

The translation of the smartphone in the airport acts exactly as well as shutdown, the status of the interlocutor is constantly online.

Hi! Well, I checked by registering both accounts on deshalbfrei.org on which there is MAM support. The third problem is solved, thanks! The second no, most likely the case in incorrect references of the status when the smartphone is turned off, you should check it, because the status does not change on offline even after 30 minutes (perhaps never), the one who is misleading the interlocutor who thinks that I am online. The translation of the smartphone in the airport acts exactly as well as shutdown, the status of the interlocutor is constantly online.
Owner

The second issue depends on the session timeout which can be configured by the server admin. If the timeout is very long you will be shown online for a long time too and vice versa. The only possibility is to manually disable the account in blabber.im. This will terminate the open session.
In a way of flight mode (cut off the connection) blabber can't terminate the session correctly and is shown as online until session times out. With the session tineout it's possible to resume an open session after a network outage. This is an important feature for mobile devices.

The second issue depends on the session timeout which can be configured by the server admin. If the timeout is very long you will be shown online for a long time too and vice versa. The only possibility is to manually disable the account in blabber.im. This will terminate the open session. In a way of flight mode (cut off the connection) blabber can't terminate the session correctly and is shown as online until session times out. With the session tineout it's possible to resume an open session after a network outage. This is an important feature for mobile devices.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.