Description
I am having issues with running my SDK implementation on most OS’s including Desktop and mobile devices. The issues range from devices not being allowed (blocked camera, and blocked audio), to the application not even starting.
When I checked site settings I found out that the zoom endpoint was in ‘http’. This is supposed be ‘https’ in my opinion and is the reason for the devices not being allowed for the site/app.
Is there a walk around? Or I’m I missing something?
After troubleshooting for some time, I find that the issue comes from the cookies used by zoom.us. It appears the SameSite attribute has not been set at all in the cookies. This should be the cause of the issue.
Hence, because the SameSite attribute is not set, the browser defaults it to ‘Lax’ and blocks the cookies, and the application cannot start.
These cookies are unrelated to the functionality of the Video SDK; they simply record some preference settings on the Zoom website. Could you please take another look to see if any other reasons are causing HTTP-related issues?