Thanks to Gary Passero, we've identified the issue and have pushed out a fix: https://support.pop.com/changelog/pop-v809-important-bug-fix-for-screen-sharing

If you have any issues after the update, please post a new bug report. Thank you for your patience and your help!

J Sherwani (Pop Team) Thanks for thinking about this so quickly. I'll try to do as you asked to assist the diagnostics.

Is this easy to reproduce? If so, it would be incredibly helpful if whoever is able to reproduce this to find a time to reproduce it with us live via https://calendly.com/j-pop/debug-session

Alternatively, if it isn't easy to reproduce, the moment this happens, could you stop the call, click the angry face to leave feedback for that call, and reference this ticket in your response, telling us that it just happened? Knowing the time will help us dig through our logs to identify what may have caused the issue.

Also, could you keep the Pop "Activity Monitor" view open around this time? My guess is that bandwidth estimation is incorrectly estimating that you have very low bandwidth, which chokes the screen share stream, and so seeing what the screen share host's Pop thinks its available bandwidth is would be very helpful.

I've seen this multiple times on MacOS over the last few days as well. Had to switch to Zoom

This is happening on pretty much every call I get on.

This isn't just on Windows. I had it happen recently on macOS.

I can confirm I've also seen this happen on MacOS. J Sherwani (Pop Team), can you verify?

I can confirm we're seeing this in v8.0.1, and it's leaves us dead in the water.

It causes a great amount of confusion: seeing the mouse movement makes me think I'm seeing his screen, but he's not making the change I requested... so I ask it again... but really, he's making it. So now he's confused why I just repeated myself. This pattern continues for a while until we figure out that I can't see what he's done, b/c the screen stopped updating.

Pop is unusable for screen sharing applications (like pair programming) until this is fixed.

We've switched back to Slack (temporarily) until then.