Mattermost, Inc.

[SOLVED] Mattermost XenMobile Integration

Hello, we are trying to insert Mattermost into Citrix.
Android version works just fine. IOS version crashes in several second after launch (we see launch screen, then address screen for a short period of time, not enough to start typing).
Happens with both builds: self-made according to guide and unsigned v 1.9.2.
Any help is appreciated.

Logs part:
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(CFNetwork)[547] : TCP Conn [5:0x15dcf5790] using empty proxy configuration
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(CFNetwork)[547] : Stream client bypassing proxies on TCP Conn [5:0x15dcf5790]
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(CFNetwork)[547] : TCP Conn 0x15dcf5790 started
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(libnetwork.dylib)[547] : [5 ] start
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(CFNetwork)[547] : TCP Conn 0x15dcf5790 event 3. err: 61
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(libnetwork.dylib)[547] : nw_connection_get_connected_socket 5 Connection has no connected handler
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(CFNetwork)[547] : TCP Conn 0x15dcf5790 complete. fd: -1, err: 61
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(CFNetwork)[547] : TCP Conn 0x15dcf5790 Failed : error 0:61 [61]
Jul 17 10:24:13 iPhone-Dmitrij Mattermost(CFNetwork)[547] : TCP Conn 0x15dcf5790 canceled

Hi @neposo! Thank you for reaching out.

We had other reports on crashing issues on 1.9.2 and 1.9.3 so we included additional fixes in v1.10 and people have reported that the latest version works well. Would you like to try v1.10 to see if it improves the crashing issues?

Yep, we made v 1.10 build ourselves and tested it, but still got the same issue. Would be great if we can get unsigned ipa v 1.10 compiled by the Mattermost team and test it as well.

Hi @neposo, This page might help or let me know if it’s not what you were looking for: https://github.com/mattermost/mattermost-mobile/releases.

Unsigned ipa v 1.10 din’t work as well. However, we figured out that it was MDX Wrapper issue. Signing with enterprise key and putting it into XenMobile solved the issue.