You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first problem, clicking the "Start a New Session!" button no longer triggers the modal.
The second problem, for some members, the modal doesn't get triggered at all, regardless of whether they're starting a new session or joining a session that's already in progress.
Steps to Reproduce
Click the "Start a New Session!" or "Join Now!" button in the Slack #co-working-room.
It begins a new Zoom session, bypassing the "Heads up!" modal.
Environment
The first problem:
OS: MacOS Ventura 13.4 (Intel)
Slack: v4.32.122
The second problem:
OS: MacOS Monterey 12.0 (M1)
Slack: v4.31.155
Anything Else?
I originally noticed the first problem with the missing modal upon starting up a new co-working session. This morning while speaking with @alexisjcarr about the issue, I found out that she has never seen this modal. She uses an M1 machine so this may have something to do with it? She's open to you troubleshooting the issue with her, if needed, as am I.
The text was updated successfully, but these errors were encountered:
What Happened?
There's two things happening here:
The first problem, clicking the "Start a New Session!" button no longer triggers the modal.
The second problem, for some members, the modal doesn't get triggered at all, regardless of whether they're starting a new session or joining a session that's already in progress.
Steps to Reproduce
Environment
The first problem:
The second problem:
Anything Else?
I originally noticed the first problem with the missing modal upon starting up a new co-working session. This morning while speaking with @alexisjcarr about the issue, I found out that she has never seen this modal. She uses an M1 machine so this may have something to do with it? She's open to you troubleshooting the issue with her, if needed, as am I.
The text was updated successfully, but these errors were encountered: