This is some issue with Xabber when using with the latest Openfire version Can’t send second message using Openfire 4.0 server · Issue #618 · redsolution/xabber-android · GitHub
There were security and performance updates since Openfire 3.10.3 (which is reported as last working fine with Xabber). This is most probably some Xabber bug.
Yaxim works fine on Android with Openfire, but it hasn’t been updated for a long time and doesn’t support group chats. Everyone seems to be glad using Conversations client for Android. But it is a paid one (although there is a way to compile it yourself free of charge).
What OS, Windows? If you have it installed in Program files and run it with a launcher, then you have to run it with “Run as admin” for it to be able to save changes (UAC). You can also try adding some other user as admin (which you know the password of).
As i said, you can add some other user (which you know password for) as admin. Login with that user, change password for ‘admin’ user. Then login with admin and remove administrator rights from that first user.
I don’t have any problem with capital letter my resource name is Android still i can get each and every message.
When i was trying to send muc message i got this type of error so at that time i had some research and found that my servicediscovery manager run after my connection has been established so try to execute service discovey manager before you establish connection. Hope you got solution .