| 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 (1179 days ago) |
| Due | |
| Updated | 07/30/2018 (947 days ago) |
| Assigned | |
| Resolved |
Would it be possible for you to test the attached little patch?
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
New Attachment: mucthread.diff
State ⇒ Accepted
Assigned to Jakob Schröter
Would it be possible for you to test the attached little patch?
State ⇒ Unconfirmed
Queue ⇒ gloox
Summary ⇒ MUC messages with thread id fire off handleMessage instead of handleMUCMessage
Type ⇒ Bug
Priority ⇒ 1. Low
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>