Reydan46
commented
3 weeks 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
}
devinbinnie
ZarenOFF
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.