does this error go away after some time or does it persist across app restarts and refreshes? Any other functionality impacted, like notifications?
Did you already try to switch networks (wifi → gsm, gsm → wifi) in order to verify that the problem is not related to a specific connection?
Does your Mattermost domain have an IPv6 record and is it reachable via IPv6 properly?
Thanks, this sounds like a problem with the websockets which also indicates the error your seeing, so your mobile client is not able to establish a solid websocket connection to the server. The websocket is used for streaming events and notifying the mobile app about a new post f.ex.
Trying to find out how to further debug that and will update you once I know.
Also, can you please verify the build number of your app? Click on your profile picture on the bottom right, then on Settings and then on “About ”. It should be build 452.
Also, if it really is 452, can you please click on the “Report a problem” link at the bottom of the Settings screen and send yourself the logs and attach the relevant parts here? Not sure if they contain sensitive information, you might want to DM them to me or strip the relevant parts out of it first before posting them publicly.
Got the same issue: App showing “The server is not reachable” and no notification on incoming messages.
Could it be an incompatibility with the new Android app and our server which is still on the previous version ?
2023/01/23 17:35:19.121 INFO Launch app in Home screen
2023/01/23 17:35:19.200 INFO Running "Home
2023/01/23 17:35:21.195 INFO websocket connecting to wss://xxxxxxxxx.com:443/api/v4/websocket
2023/01/23 17:35:22.279 WARN Handling Javascript error websocket error false
2023/01/23 17:35:22.281 ERROR websocket error wss://xxxxxxxxx.com:443/api/v4/websocket
2023/01/23 17:35:22.283 WARN Handling Javascript error WEBSOCKET ERROR EVENT false
2023/01/23 17:35:22.290 ERROR WEBSOCKET ERROR EVENT {
"message": {
"error": "Forbidden"
},
"url": "wss:\/\/xxxxxxxxx.com:443\/api\/v4\/websocket"
}
On my computer, in the browser, the web socket call works fine. wss://xxxxxxxxx.com/api/v4/websocket?connection_id=&sequence_number=0 Status Code: 101 Switching Protocols