search

cmeng-git / atalk-android

xmpp/jabber client for android
Apache License 2.0
155 stars 56 forks source link

App Crashes when entering already joined groups #210

Closed methuselahin closed 2 months ago

methuselahin commented 5 months ago

I have joined Conversations.im and movim.im group for app related discussions. The app is unable to sync the the history and crahes back to login screen. Just join any group and can i guess replicate the issue back

cmeng-git commented 5 months ago

Are you able to provide the conference room name for the conversations.im which has the problem? I have create an account on conversations.im but do not know which muc to join the see the problem.

methuselahin commented 5 months ago

Why can't you make another xmpp chat group with public discussion? here is the link to the group for your reference Jabber Conversations Group https://search.jabber.network/rooms/1. We can help you clear the apps with bugs in real time. On Mon, 5 Feb 2024 at 12:52, Eng ChongMeng @.***> wrote:

Are you able to provide the conference room name for the conversations.im which has the problem? I have create an account on conversations.im but do not know which muc to join the see the problem.

— Reply to this email directly, view it on GitHub https://github.com/cmeng-git/atalk-android/issues/210#issuecomment-1926366896, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACTWIGSQ7GE33DBSISE3XQTYSCCFBAVCNFSM6AAAAABCXZDAICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRWGM3DMOBZGY . You are receiving this because you authored the thread.Message ID: @.***>

--

[image: tpx]

cmeng-git commented 5 months ago

Why can't you make another xmpp chat group with public discussion? Commonly the community chatroom resides on an XMPP server owned by an organisation with its domain name IP. aTalk does not have a domain nor an XMPP server for community service.

I have joined several of the community chat rooms in your given list, but did not experience crash on joining. I suspect your observed aTalk crashes on joining a chat group, is due to data corruption in aTalk database SQLite storage in one of the received room messages.

If you are still able to reproduce the crash, would appreciate you can send me aTalk debug log; so that I can figure out the root cause and to resolve the Exception.

cmeng-git commented 5 months ago

If you are still facing the problem. Please do the following:

Long press on the conference room that has problem to bring up the context menu. Then select 'Erase this chatRoom history'. Believe this should resolve the issues.

If you still want to keep your current history messages, please send the aTalk debug log for further investigation and possible finding a solution.

methuselahin commented 5 months ago

The app has issues with already joined groups and it doesn't even open group for me. Can you create a xmpp room for discussion about it?

On Sun, 11 Feb 2024, 01:53 Eng ChongMeng, @.***> wrote:

If you are still facing the problem. Please do the following:

Long press on the conference room that has problem to bring up the context menu. Then select 'Erase this chatRoom history'. Believe this should resolve the issues.

If you still want to keep your current history messages, please send the aTalk debug log for further investigation and possible finding a solution.

— Reply to this email directly, view it on GitHub https://github.com/cmeng-git/atalk-android/issues/210#issuecomment-1937112629, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACTWIGVC7JXJ5RPK5DNLZVLYS7JLLAVCNFSM6AAAAABCXZDAICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGEYTENRSHE . You are receiving this because you authored the thread.Message ID: @.***>

cmeng-git commented 5 months ago

Why can't you make another xmpp chat group with public discussion?

Commonly the community chatroom resides on an XMPP server owned by an organisation with its domain name IP. aTalk does not have a domain nor an XMPP server for community service.

Sorry, aTalk does not have a conference room for discussion due to above reason. Also in order to ensure every aTalk issue is tracked to closure, would still prefer using this issues tracker.

The app has issues with already joined groups and it doesn't even open group for me.

I am still not fully understand the full problem you are having. I really need more details info from you.

  1. Are you using below UI to join the group chat.

image

  1. After you have entered the "Chat Room" entity ID, and click "Join" button, what is the error messages being shown.

  2. If aTalk crashes after you clicked "Join" button, please send me the aTalk debug log after you have relaunched aTalk. The debug log should contain the aTalk crash info. Without this aTalk debug log, it is not possible for me to guess or fix the problem.

If you are unable to provide me with the aTalk debug log, please provide me with the exact chatRoom entityId and an user account if required, for the room that you are facing problem with; so I can test it on my side.

I have tested with at least 5 chat rooms from the list you sent. aTalk does not crash on any of the chatroom. Except I see the problem for chat@dino.im, because dino.im muc implementation does not comply with XEP-45.

image

Please note incorrect implementation of any of XMPP protocols, may be the reason for aTalk to crash. Smack library may assert error test and throw exceptions.

cmeng-git commented 2 months ago

Close due to no further update from user. Problem likely to have been fixed in latest aTalk release.