Some users may encounter problems when they start screen sharing and this might be because of browser preferences or OS preferences. Here are some common issues with screen sharing in Remo:

Screen sharing is blocked in Safari
Screen sharing is blocked in Firefox
Can't Screen share using macOS Catalina
Computer crashed after turning on Screen sharing on Windows 10

Below are the solutions to prevent these errors:

Screen sharing is blocked in Safari

Click on ‘Safari’ and click ‘Settings for this website:’.

Check that the Screen Sharing field is not set on Deny. Set it on Ask or Allow. Set it on ‘Allow’ if you don’t want to be reminded each time you turn on Screen Sharing.

Refresh your browser. The next time you try to screen share, Safari will display a window asking you to allow screen sharing.

Screen sharing is blocked in Firefox

Click on the 'Permissions' icon next to your URL bar.

Under permission, make sure that ‘Share the screen' is not blocked.

Once you allow permissions, please refresh your browser. You should be able to share your screen afterwards.

Screen sharing using macOS Catalina

Due to increased security and permissions safeguards with macOS 10.14 Mojave and 10.15 Catalina, you may need to adjust your Security & Privacy settings to enable screen sharing of your desktop and other applications on your computer. Check how to fix screen sharing on macOS Catalina here.

Computer crashed after turning on Screen sharing on Windows 10

On Windows 10, Chrome freezes when screen sharing a high-resolution display. This issue is caused by a bug in Chrome. The issue may go away if the 'hardware acceleration settings' in Chrome is disabled. To disable this:

Go to 'Settings' in your browser.

Type "Hardware Acceleration" on the search box.

Click on the toggle button next to "Use Hardware Acceleration when available". Make sure that the button is grayed out.

Note: If this solution doesn't work, switch to Firefox.

The patch was scheduled to land in late April in Chrome 82 by Google themselves, however this has been delayed due to the Coronavirus. Unfortunately, there's no ETA as of now , the patch will most likely land in Chrome 82.
Was this article helpful?
Thank you!