Reported by a customer that runs their app on several different embedded browsers such as email apps
For example, if an Android embedded browser has settings.setDomStorageEnabled(false), then sessionStorage isn’t available. Sentry checks for this with sessionStorage in window, but it’s possible for that to be true, but window.sessionStorage to be null, resulting in later errors. This would prevent functionality from behaving as normal.
We might need to gate access to sessionStorage and if we can't access this at other spots we need to find a way to gracefully degrade the SDK. If Replay cant' work, we should disable recording, but let the other functionalies of the SDK (e.g: error reporting) continue to function
Reported by a customer that runs their app on several different embedded browsers such as email apps
We might need to gate access to
sessionStorageand if we can't access this at other spots we need to find a way to gracefully degrade the SDK. If Replay cant' work, we should disable recording, but let the other functionalies of the SDK (e.g: error reporting) continue to function