Xabber Android not detecting XEP with Prosody 0.10

[mightyBroccoli]

I am using Xabber / Xabber Beta on my phone and both are not using the mod muc which is active on my server. When I am using gajim on win/arch mam works perfectly. Also PEP is not detected correctly. In the serverinfo section XEP-163 Personal Eventing Procotoll and XEP-313 MAM is not detected even though both are installed and working on my server.

[casperklein]

I noticed that as well, that PEP is not detected in the serverinfo.

=> Xabber 2.0.2(360) with Prosody 0.9.12

[hartois]

I also confirm this bug with Prosody 0.10 and Xabber 2.1(405)

[Quallenauge]

I hacked the file mod_mam/mod_mam.lua of prosody 0.10 branch: and add the following lines at the top of it local xmlns_mam0 = "urn:xmpp:mam:0"; local xmlns_mam1 = "urn:xmpp:mam:1"; local xmlns_mam = "urn:xmpp:mam:2";

removed the feature hook ~~module:hook("account-disco-info", function(event) (event.reply or event.stanza):tag("feature", {var=xmlns_mam}):up(); (event.reply or event.stanza):tag("feature", {var=xmlns_st_id}):up(); end);~~

and added the new syntax: module:add_feature(xmlns_mam0); module:add_feature(xmlns_mam1); module:add_feature(xmlns_mam); module:add_feature(xmlns_st_id);

[hartois]

It does not help. I have "Support for chat history server store is not determined yet" message in history settings.

[back2live]

can confirm after the mod from quallenauge xabber will find the mod_mem Feature.

[Zash]

Per https://xmpp.org/extensions/xep-0313.html#support MAM is advertised on the account JID, not on the server.

[singpolyma]

Is this the same problem as #745 ? I also happily use MAM with other clients, but with Xabber it says my prosody server has no MAM...