I installed Sentry on my production application and noticed a deprecation error filling up all my logs.
ReportingObserver [deprecation]: SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.
Thank you for reaching out about this—to clarify, did you add Sentry logging to Zoom API requests, or something else? If you’re seeing warnings for CORS, please note that our APIs must be called from your backend—we don’t support calling our APIs from a frontend service.
Let me know if there are any additional details you can share so that I can better understand how you’re leveraging our APIs in relation to the errors you’ve shared here.
Sentry logging is added to the whole application as default, so it logs out errors across the platform completely. No zoom API calls are made from the frontend, the only zoom calls that are made are by Zoom SDK.
I have done more testing with the cross-origin isolation enabled, it seems to works fine on Chrome Canary 92 and the current stable version, my question is now as described in the documentation here https://web.dev/cross-origin-isolation-guide/ under the caution section there will be some issues if we have popups for some third-party authentication.
I added the meta tags for the origin trials but however, the gallery view seems still shown as disabled from the chrome 92 canary that I used for testing. does it need to be on the document header instead?