5.2.20
10/23/2019

[#272] MUC messages with thread id fire off handleMessage instead of handleMUCMessage
Summary MUC messages with thread id fire off handleMessage instead of handleMUCMessage
Queue gloox
Queue Version SVN
Type Bug
State Accepted
Priority 1. Low
Owners js (at) camaya (dot) net
Requester jazzvoid (at) gmail (dot) com
Created 12/10/2017 (682 days ago)
Due
Updated 07/30/2018 (450 days ago)
Assigned
Resolved

History
07/30/2018 07:15:37 PM jazzvoid (at) gmail (dot) com Comment #3 Reply to this comment
Thanks for the report. Are you still on this?
Would it be possible for you to test the attached little patch?
Hello, it took some time for the issue to resurface since clients 
using threads in mucs seem to be rare, but apparently Xabber does that

I've tried the attached patch and it does fix the issue
06/12/2018 10:14:02 AM Jakob Schröter Comment #2
New Attachment: mucthread.diff Download
State ⇒ Accepted
Assigned to Jakob Schröter
Reply to this comment
Thanks for the report. Are you still on this?
Would it be possible for you to test the attached little patch?
12/10/2017 04:40:15 PM jazzvoid (at) gmail (dot) com Comment #1
State ⇒ Unconfirmed
Queue ⇒ gloox
Summary ⇒ MUC messages with thread id fire off handleMessage instead of handleMUCMessage
Type ⇒ Bug
Priority ⇒ 1. Low
Reply to this comment
Gloox 1.0.20

For some reason MUC messages that have a thread ID fire off 
handleMessage callbacks instead of handleMUCMessage. Xabber Dev 
Android 2.0.1 sends messages like these.

Stanza that causes handleMessage:

<message id="r2Y0b-1078" to="foo@example.com/bar" type="groupchat" 
from="example@conference.jabber.ru/baz1" xml:lang="en">
<body>text</body>
<thread>0hW5O7OB5voe</thread>
</message>

Stanza that causes handleMUCMessage (as expected):

<message id="ab2da" to="foo@example.com/bar" type="groupchat" 
from="example@conference.jabber.ru/baz2" xml:lang="ru">
<body>text2</body>
</message>