Connecting to conferences.

[MichaelTiernan]

I am assuming that the error is specific to our server. My proof of that is that my xabber.org id can stay logged into the test conference at xabber.

I have three conference "rooms" that I want to be connected to and the xabber app from my Android won't stay connected. I can establish a connection and send a line. It will then give me a "connection unavailable" message. BUT, subsequent lines /are/ sent to the conference. It just seems to not know how to stay connected.

Attached is a log. I sanitised it a little.
What do I need to tell our end to correct this?
XabberBeta 2.3(473) 2018-03-27 14-50-45 log file.txt

Thanks for everyone's time.

[oxoWrk]

Your server uses out-of-date time-stamp format("CCYYMMDDThh:mm:ss"). Smack crashes when parsing this stamp

[MichaelTiernan]

Okay, I'll ask a loaded question. I know the server on this end is broken and using the wrong format but, shouldn't the Smack software deal with it more elegantly?

[MichaelTiernan]

And, sorry, hit return too fast.

Is there anything I can do to deal with this? I'll ask the server folks to look into an update or whatever but I won't hold my breath.

[andrewnenakhov]

@MichaelTiernan perhaps you can post an issue on Smack issue tracker and have it fixed there.

However, there are major concerns how much efforts 'good' software developers must waste to provide interoperability with software who's developers don't give a damn. Perhaps best way is to use decent server like ejabberd, fixing this once and for all.

[MichaelTiernan]

Not asking the developers to deal with it. Just asking for advice on what to tell the server folks. :(

Like what version of the Smack library is being used in the beta version.

[andrewnenakhov]

Just asking for advice on what to tell the server folks. :(

@MichaelTiernan that depends on what server you are having issues with. Do you have this information?

[andrewnenakhov]

We're obsoleting conferences, in 2019 or in 2020 with a better protocol to replace them.