Actually, I’ve just applied the 7.10 server update. So going to let that run for a bit.
And mobile app 2.3 was released, got that updated too.
I have the same issues, affecting the android app, 2023/04/17 14:15:29.401 INFO Running "Onboarding
2023/04/17 14:15:31.419 INFO Running "Server
2023/04/17 14:15:52.329 INFO Running "Login
2023/04/17 14:15:53.997 INFO Running "SSO
2023/04/17 14:16:23.629 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/04/17 14:16:28.388 WARN Handling Javascript error fetchSessions false
2023/04/17 14:16:28.388 ERROR fetchSessions {
“jsEngine”: “hermes”,
“status_code”: 401,
“server_error_id”: “api.context.session_expired.app_error”,
“url”: “/api/v4/users/me/sessions”,
“message”: “Invalid or expired session, please login again.”
}
2023/04/17 14:16:31.631 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/04/17 14:16:35.811 INFO Running "SSO
2023/04/17 14:16:40.279 INFO websocket connecting to wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0
2023/04/17 14:16:40.527 INFO websocket connected to wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0
2023/04/17 14:16:40.530 INFO wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0 got connection id bc6e3zdtetrfppx488a8magb3o
2023/04/17 14:16:41.032 INFO websocket closed wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0
2023/04/17 14:16:41.042 INFO Running "Home
2023/04/17 14:16:41.313 INFO Running "SelectTeam
2023/04/17 14:16:44.282 INFO websocket re-established connection to wss://mattermost.smhi.se/api/v4/websocket?connection_id=bc6e3zdtetrfppx488a8magb3o&sequence_number=1
2023/04/17 14:16:54.296 DEBUG error joining a team: {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/teams/yipm58u9ubbmdensne6sbimzne”,
“message”: “Received invalid response from the server.”
We sign in with gitlab and get a api error respons when being redirected from gitlab to Mattermost. This issue only effects android, ios and web and desktop is fine
Hi @MattermostSMHI and welcome to the Mattermost forums!
Just to verify, what mobile version are you on right now on the problematic devices?
We are on 2.3 on android. Really need some help with this. I have verified that the problem is the same with 2.1 and 2.2.
The problem with our environment is that you get stuck in a loop after logging in with gitlab sso. You get an error page, invalid respons /api/v4/users/me. but sometimes you can get out of the loop and gets logged in but get lots of errors.
This is me trying the 2.1 app and logging in until it exits the loop.
2023/04/19 09:46:08.209 INFO Running "Onboarding
2023/04/19 09:46:11.378 INFO Running "Server
2023/04/19 09:46:26.820 INFO Running "SSO
2023/04/19 09:46:59.846 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:05.797 WARN Handling Javascript error fetchSessions false
2023/04/19 09:47:05.800 ERROR fetchSessions {
“jsEngine”: “hermes”,
“status_code”: 401,
“server_error_id”: “api.context.session_expired.app_error”,
“url”: “/api/v4/users/me/sessions”,
“message”: “Invalid or expired session, please login again.”
}
2023/04/19 09:47:07.728 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:13.994 INFO Running "SSO
2023/04/19 09:47:15.195 WARN Handling Javascript error fetchSessions false
2023/04/19 09:47:15.196 ERROR fetchSessions {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me/sessions”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:17.673 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:19.337 WARN Handling Javascript error fetchSessions false
2023/04/19 09:47:19.338 ERROR fetchSessions {
“jsEngine”: “hermes”,
“status_code”: 401,
“server_error_id”: “api.context.session_expired.app_error”,
“url”: “/api/v4/users/me/sessions”,
“message”: “Invalid or expired session, please login again.”
}
2023/04/19 09:47:21.109 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:24.818 INFO Running "SSO
2023/04/19 09:47:25.984 WARN Handling Javascript error fetchSessions false
2023/04/19 09:47:25.985 ERROR fetchSessions {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me/sessions”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:29.276 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:33.843 WARN Handling Javascript error fetchSessions false
2023/04/19 09:47:33.846 ERROR fetchSessions {
“jsEngine”: “hermes”,
“status_code”: 401,
“server_error_id”: “api.context.session_expired.app_error”,
“url”: “/api/v4/users/me/sessions”,
“message”: “Invalid or expired session, please login again.”
}
2023/04/19 09:47:38.238 INFO websocket connecting to wss://mattermost.smhi.se/api/v4/websocket
2023/04/19 09:47:38.251 INFO Running "Home
2023/04/19 09:47:38.616 INFO websocket connected to wss://mattermost.smhi.se/api/v4/websocket
2023/04/19 09:47:38.620 WARN Handling Javascript error fetchProfilesInChannel false
2023/04/19 09:47:38.620 ERROR fetchProfilesInChannel {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users?in_channel=t4tkqfqbupb7dd6zk33hom3rjo”,
“message”: “Received invalid response from the server.”
}
2023/04/19 09:47:40.909 WARN Handling Javascript error FetchPostsForChannel false
2023/04/19 09:47:40.911 ERROR FetchPostsForChannel {
“jsEngine”: “hermes”,
“status_code”: 403,
“server_error_id”: “api.user.view_archived_channels.get_posts_for_channel.app_error”,
“url”: “/api/v4/channels/bytciunboff1xryydit3xa4ute/posts?page=0&per_page=60&collapsedThreads=false&collapsedThreadsExtended=false”,
“message”: “Cannot retrieve posts for an archived channel”
}
2023/04/19 09:47:45.542 INFO Running "Settings
2023/04/19 09:47:46.913 WARN Handling Javascript error fetchSessions false
2023/04/19 09:47:46.913 ERROR fetchSessions {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“url”: “/api/v4/users/me/sessions”,
“message”: “Received invalid response from the server.”
}
I’ve verified that there is no change in mattermost 7.10 for our problem
Hey again,
in the meantime, mobile client 2.4 has been released and if the problem is still reproducible with it, would you be open to download the latest beta app and try to reproduce it there? The beta version has much better logging and should help the developers troubleshoot the issue if it’s still there in the beta.
I’ already on the beta but havent gotten a new 2.5b release yet. But i’m also pretty sure that our problem lies in the fact that we run gitlab sso login and piggyback onto keycloak.
From what I’ve been told, the current beta release is still flagged with version 2.4. We’re talking about build 271+ (depending on the time you’re reading this).
If you have this version running, can you please try to generate a log bundle and attach/link it here?
2023/06/01 16:51:00.216 INFO Running "Onboarding
2023/06/01 16:51:02.083 INFO Running "Server
2023/06/01 16:51:21.615 INFO Running "Login
2023/06/01 16:51:22.918 INFO Running "SSO
2023/06/01 16:51:28.485 DEBUG error on ssoLogin Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/01 16:51:28.490 WARN Failed to set store from local data {
“jsEngine”: “hermes”,
“intl”: {
“defaultMessage”: “Received invalid response from the server.”,
“id”: “mobile.request.invalid_response”
},
“details”: {
“jsEngine”: “hermes”,
“code”: “EUNSPECIFIED”,
“message”: “unexpected end of stream on https://mattermost.smhi.se/…”,
“userInfo”: null,
“nativeStackAndroid”: [
{
“lineNumber”: 202,
“file”: “Http1ExchangeCodec.kt”,
“methodName”: “readResponseHeaders”,
“class”: “okhttp3.internal.http1.Http1ExchangeCodec”
},
{
“lineNumber”: 106,
“file”: “Exchange.kt”,
“methodName”: “readResponseHeaders”,
“class”: “okhttp3.internal.connection.Exchange”
},
{
“lineNumber”: 79,
“file”: “CallServerInterceptor.kt”,
“methodName”: “intercept”,
“class”: “okhttp3.internal.http.CallServerInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 34,
“file”: “ConnectInterceptor.kt”,
“methodName”: “intercept”,
“class”: “okhttp3.internal.connection.ConnectInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 95,
“file”: “CacheInterceptor.kt”,
“methodName”: “intercept”,
“class”: “okhttp3.internal.cache.CacheInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 83,
“file”: “BridgeInterceptor.kt”,
“methodName”: “intercept”,
“class”: “okhttp3.internal.http.BridgeInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 76,
“file”: “RetryAndFollowUpInterceptor.kt”,
“methodName”: “intercept”,
“class”: “okhttp3.internal.http.RetryAndFollowUpInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 20,
“file”: “BearerTokenInterceptor.kt”,
“methodName”: “intercept”,
“class”: “com.mattermost.networkclient.interceptors.BearerTokenInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 26,
“file”: “TimeoutInterceptor.kt”,
“methodName”: “intercept”,
“class”: “com.mattermost.networkclient.interceptors.TimeoutInterceptor”
},
{
“lineNumber”: 16,
“file”: “RuntimeInterceptor.kt”,
“methodName”: “intercept”,
“class”: “com.mattermost.networkclient.interceptors.RuntimeInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 29,
“file”: “RetryInterceptor.kt”,
“methodName”: “intercept”,
“class”: “com.mattermost.networkclient.interfaces.RetryInterceptor$DefaultImpls”
},
{
“lineNumber”: 6,
“file”: “ExponentialRetryInterceptor.kt”,
“methodName”: “intercept”,
“class”: “com.mattermost.networkclient.interceptors.ExponentialRetryInterceptor”
},
{
“lineNumber”: 16,
“file”: “RuntimeInterceptor.kt”,
“methodName”: “intercept”,
“class”: “com.mattermost.networkclient.interceptors.RuntimeInterceptor”
},
{
“lineNumber”: 109,
“file”: “RealInterceptorChain.kt”,
“methodName”: “proceed”,
“class”: “okhttp3.internal.http.RealInterceptorChain”
},
{
“lineNumber”: 201,
“file”: “RealCall.kt”,
“methodName”: “getResponseWithInterceptorChain$okhttp”,
“class”: “okhttp3.internal.connection.RealCall”
},
{
“lineNumber”: 517,
“file”: “RealCall.kt”,
“methodName”: “run”,
“class”: “okhttp3.internal.connection.RealCall$AsyncCall”
},
{
“lineNumber”: 1137,
“file”: “ThreadPoolExecutor.java”,
“methodName”: “runWorker”,
“class”: “java.util.concurrent.ThreadPoolExecutor”
},
{
“lineNumber”: 637,
“file”: “ThreadPoolExecutor.java”,
“methodName”: “run”,
“class”: “java.util.concurrent.ThreadPoolExecutor$Worker”
},
{
“lineNumber”: 1012,
“file”: “Thread.java”,
“methodName”: “run”,
“class”: “java.lang.Thread”
}
]
},
“url”: “/api/v4/users/me”,
“message”: “Received invalid response from the server.”
}
2023/06/01 16:51:41.352 DEBUG error on fetchSessions Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/02 09:44:19.453 INFO websocket connecting to wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0
2023/06/02 09:44:19.468 INFO Launch app in Select Teams screen
2023/06/02 09:44:19.474 DEBUG error on verifyPushProxy Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/02 09:44:19.522 INFO Running "SelectTeam
2023/06/02 09:44:19.672 INFO websocket connected to wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0
2023/06/02 09:44:19.673 INFO wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0 got connection id inpdqw6p4ifh3pjwa51ysxfkya
2023/06/02 09:44:20.739 INFO WEBSOCKET RECONNECT MODELS BATCHING TOOK 62ms
2023/06/02 09:44:20.777 INFO Running "Home
2023/06/02 09:44:21.119 DEBUG re-fetching self
2023/06/02 09:44:21.143 DEBUG error on fetchMe Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/02 09:44:21.144 DEBUG error on fetchProfilesInChannel Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/02 09:44:21.145 DEBUG error on fetchProfilesInChannel Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/02 09:44:32.820 INFO Running "BottomSheet
2023/06/02 09:44:33.748 DEBUG error on fetchSessions Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/02 09:44:41.192 DEBUG error on fetchSessions Received invalid response from the server.; unexpected end of stream on https://mattermost.smhi.se/…
2023/06/02 14:40:53.119 INFO websocket connecting to wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0
2023/06/02 14:40:53.135 INFO Launch app in Home screen
2023/06/02 14:40:53.211 INFO Running "Home
2023/06/02 14:40:53.619 DEBUG re-fetching self
2023/06/02 14:40:53.661 INFO websocket connected to wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0
2023/06/02 14:40:53.662 INFO wss://mattermost.smhi.se/api/v4/websocket?connection_id=&sequence_number=0 got connection id tkctnc4d9jn89mjy7q5h3na5ry
2023/06/02 14:40:53.774 DEBUG missing currentUserId
2023/06/02 14:40:53.847 DEBUG re-fetching self
2023/06/02 14:40:54.606 INFO WEBSOCKET RECONNECT MODELS BATCHING TOOK 315ms
2023/06/02 14:40:54.676 DEBUG error on fetchGroupsForMember api endpoint requires a license; Unknown error
2023/06/02 14:40:57.209 DEBUG error on fetchPosts Cannot retrieve posts for an archived channel; Unknown error
2023/06/02 14:40:57.210 DEBUG error on fetchPostsForChannel Cannot retrieve posts for an archived channel; Unknown error
2023/06/02 14:40:57.212 DEBUG error on fetchPosts Cannot retrieve posts for an archived channel; Unknown error
2023/06/02 14:40:57.212 DEBUG error on fetchPostsForChannel Cannot retrieve posts for an archived channel; Unknown error
2023/06/02 14:40:57.213 DEBUG error on fetchPosts Cannot retrieve posts for an archived channel; Unknown error
2023/06/02 14:40:57.214 DEBUG error on fetchPostsForChannel Cannot retrieve posts for an archived channel; Unknown error
2023/06/02 14:40:57.215 DEBUG error on fetchPosts Cannot retrieve posts for an archived channel; Unknown error
We think the issue has to do with the fact that the login wants the users to have a name axxxxx which is supplied through the openid specified scope prefered username. But mattermost can’t retrive that and istead makes up its own username derived from mailadress. I think that is the ssologin error