Open ZarenOFF opened 2 months ago
We are facing the same issue, and we haven't identified a consistent pattern to reproduce it.
[2024-08-22 14:54:08.443] [debug] [App.Initialize] UserActivityMonitor.on(status) { userIsActive: true, idleTime: 37, isSystemEvent: false }
[2024-08-22 14:54:32.850] [debug] [ViewManager] handleSetCurrentViewBounds { x: 2560, y: 0, width: 1920, height: 1040 }
[2024-08-22 14:54:32.851] [debug] [ModalManager] handleResizeModal {
bounds: { x: 2560, y: 0, width: 1920, height: 1040 },
modalQueueLength: 0
}
[2024-08-22 14:54:32.867] [debug] [MainWindow] saving window state {
x: 2552,
y: -8,
width: 1936,
height: 1056,
maximized: true,
fullscreen: false
}
[2024-08-22 14:55:08.928] [debug] [App.Initialize] UserActivityMonitor.on(status) { userIsActive: true, idleTime: 0, isSystemEvent: false }
[2024-08-22 14:55:10.466] [debug] [App.Intercom] handleMentionNotification {
channelId: 'usgrqphcbjyojfxh1uank974xh',
teamId: '',
url: '/main/channels/3x56k5pkitr5ze99ay5njdtp8c__4tt3fy81b3fjjdpgh5s3fz68py',
silent: false,
soundName: 'Bing'
}
[2024-08-22 14:55:10.466] [debug] [Notifications] displayMention {
channelId: 'usgrqphcbjyojfxh1uank974xh',
teamId: '',
url: '/main/channels/3x56k5pkitr5ze99ay5njdtp8c__4tt3fy81b3fjjdpgh5s3fz68py',
silent: false,
soundName: 'Bing'
}
[2024-08-22 14:55:10.467] [debug] [Notifications] should not notify for this view 4
[2024-08-22 14:55:10.572] [debug] [App.Intercom] handleMentionNotification {
channelId: 'usgrqphcbjyojfxh1uank974xh',
teamId: '',
url: '/main/channels/3x56k5pkitr5ze99ay5njdtp8c__4tt3fy81b3fjjdpgh5s3fz68py',
silent: false,
soundName: 'Bing'
}
[2024-08-22 14:55:10.573] [debug] [Notifications] displayMention {
channelId: 'usgrqphcbjyojfxh1uank974xh',
teamId: '',
url: '/main/channels/3x56k5pkitr5ze99ay5njdtp8c__4tt3fy81b3fjjdpgh5s3fz68py',
silent: false,
soundName: 'Bing'
}
[2024-08-22 14:55:10.574] [debug] [PermissionsManager] doPermissionRequest notifications { requestingUrl: 'https://mattermost.tps.net/', isMainFrame: false }
[2024-08-22 14:55:10.591] [debug] [Notifications] displayMention.show MAIN b85b16e2-aa6a-4394-871b-04b9ca6e4766
[2024-08-22 14:55:10.591] [debug] [Notifications] close :usgrqphcbjyojfxh1uank974xh
[2024-08-22 14:55:12.499] [debug] [Notifications] notification click MAIN b85b16e2-aa6a-4394-871b-04b9ca6e4766
[2024-08-22 14:55:12.501] [debug] [ViewManager] handleBrowserHistoryPush 3 /main/channels/3x56k5pkitr5ze99ay5njdtp8c__4tt3fy81b3fjjdpgh5s3fz68py
[2024-08-22 14:55:12.501] [debug] [ServerManager] [0fd5a740-a2f3-48b...] getOrderedTabsForServer
[2024-08-22 14:55:12.684] [debug] [ViewManager] [8f510ce4-77c6-4fe...] [MAIN] [TAB_MESSAGING] showById 8f510ce4-77c6-4fee-90b2-fbfddcd71298
[2024-08-22 14:55:12.694] [debug] [WebContentsEventM...] [8f510ce4-77c6-4fe...] [MAIN] [TAB_MESSAGING] did-start-navigation https://mattermost.tps.net/main/channels/3x56k5pkitr5ze99ay5njdtp8c__4tt3fy81b3fjjdpgh5s3fz68py
[2024-08-22 14:55:12.706] [debug] [WebContentsEventM...] [8f510ce4-77c6-4fe...] [MAIN] [TAB_MESSAGING] did-start-navigation https://mattermost.tps.net/main/messages/@testas
[2024-08-22 14:55:12.713] [debug] [ViewManager] handleSetCurrentViewBounds { x: 2560, y: 0, width: 1920, height: 1040 }
[2024-08-22 14:55:12.714] [debug] [ModalManager] handleResizeModal {
bounds: { x: 2560, y: 0, width: 1920, height: 1040 },
modalQueueLength: 0
}
[2024-08-22 14:55:12.715] [debug] [ViewManager] focusCurrentView
[2024-08-22 14:55:17.207] [debug] [ViewManager] handleSetCurrentViewBounds { x: 2560, y: 0, width: 1920, height: 1040 }
[2024-08-22 14:55:17.208] [debug] [ModalManager] handleResizeModal {
bounds: { x: 2560, y: 0, width: 1920, height: 1040 },
modalQueueLength: 0
}
[2024-08-22 14:55:17.211] [debug] [MainWindow] saving window state {
x: 2552,
y: -8,
width: 1936,
height: 1056,
maximized: true,
fullscreen: false
}
I've seen this before - but have never been able to reproduce. Can someone take a video for me just so I can see exactly what the steps look like?
https://github.com/user-attachments/assets/425ce364-e4b8-4afe-af56-35f13d51e508
Here is the video with the error. It was very difficult to reproduce. Sorry for the blur, I cannot disclose confidential data.
@ZarenOFF Thanks for the video! No worries about the blur, so it looks like we're seeing a mention badge in the Desktop App at the top, but as said the view literally isn't navigating.
One more request - can you turn on Debug logging in the Settings modal, reproduce one more time and send me the logs? (you may want to sanitize those before sending as well)
@devinbinnie Here is the full log with debug enabled. The issue occurred when the message arrived at 15:34:51. Also, the log in the first message is also a log with this problem and debug enabled. main.log
Thanks @ZarenOFF. I'll have to investigate and get back to you.
@ZarenOFF I spent some time trying to reproduce this but unfortunately got nowhere. I have a couple theories as to what might be going on, but unfortunately nothing I can act on since I can't get reproduce the issue.
My leading theory is: The tab has gone to sleep (which is why we see websocket reconnecting messages) and is not waking up correctly until some kind of user interaction happens, which is why it's not navigating until you click somewhere. It's probably happening intermittently due to some race condition between methods that unminimize/unhide the app and navigate to the correct channel.
I think there might be a way to force that to happen, but I've been unsuccessful doing so so far. I'll hopefully be able to spend more time on it eventually, but right now I don't have the time to focus on it.
Thanks for all the feedback :) Created a JIRA ticket so we don't lose track of this: https://mattermost.atlassian.net/browse/MM-60305
@devinbinnie I would also like to add that we are using HAProxy as a reverse proxy for Mattermost, which might be important. Today, we slightly adjusted the HAProxy configuration based on this article, and we will see if it has any effect. In any case, thank you for your help.
Checks before filing an issue
Mattermost Desktop Version
5.9.0
Operating System
Windows 10 x64 22H2
Mattermost Server Version
9.11
Steps to reproduce
Expected behavior
When opening the app from a notification, the UI should immediately navigate to the chat with the new message and display it without requiring an additional click.
Observed behavior
The app opens but remains in its previous state, and the new message and chat are not visible until the user clicks somewhere in the app window.
Log Output
Additional Information
It's important to note that this issue is intermittent and difficult to reproduce consistently. I haven't been able to identify a specific pattern or set of conditions that consistently lead to this behavior.