Problems using the client with own ejabberd server (MAM support)
See original GitHub issueBevor you create a new issue:
- [x] I searched for similar issues and did not find one
- [x] I'm using the latest version available in the [Windows Store](https://www.microsoft.com/store/apps/9NW16X9JB5WV)
I’m submitting a…:
- Question of Support request
I use my own ejabberd server with almost no changes to the standard config. I am new to xmpp and I know I need certain extensions to have certain features, but what I am missing in the UWPX App is the ability to see old chat messages (probably handled by the MAM and Message Carbons extension in ejabberd). With the Conversations App on Android it works very well, also when I am offline for a short time, Conversations will sync my messages afterwards.
Another issue is the sending of a message with the client from my account 1. Currently when I send a message to a different account (account 2) with the UWPX Client on the desktop, I will not receive the message with the UWPX client on my Win 10 Phone. But my Conversations App on my other Android-Phone is showing the message as send from account 1 and in a different client with account 2 I have received this message.
App Version(s): v.0.26.2 (desktop) v.0.22.0 (mobile)
Windows 10 Version Number:
- 1809 (desktop)
- 1803
- 1709
- 1703
- 1607
- 1511
- 1507
- Insider Build (build number: )
- Misc:
Device form factor:
- Desktop
- Mobile
- Xbox
- Surface Hub
Where did you got the APP from?
- Windows Store
- Self-build, using a provided release source
- Self-build, repo cloned at [dd.mm.yyy]
- Misc, got it from…
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Yes, definitely! I’m even thinking of adding MAM support until next month, since I’m currently fixing and extending the chat window. https://twitter.com/UWPX_APP/status/1304416298353471489
Both issues are related to UWPX not having MAM support. Is your phone getting carbon copies of messages, if it is on and the app is running?
If UWPX is not running, then it has to get those messages via MAM, which is not supported currently.