Skip to content

fix(Unity): Expanded on known limitations when targeting WebGL #15485

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 12, 2025
Merged

fix(Unity): Expanded on known limitations when targeting WebGL #15485

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/platforms/unity/troubleshooting/known-limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,3 +113,8 @@ When targeting WebGL, you have the option of setting the `PlayerSettings.WebGL.e
- Setting it to `WebGLExceptionSupport.None` is not supported by the SDK.
- For the SDK to be able provide stack traces, the support needs to be set to `WebGLExceptionSupport.FullWithStacktrace`.
- The SDK is currently not able to provide line numbers due to the IL2CPP backend not being available.
- **Native crash detection is not available on WebGL.** The SDK cannot determine if the browser or tab crashed, which affects session tracking:
- Sessions with captured exceptions are marked as `Unhandled`
- Sessions where the tab/browser closes without a clean shutdown are marked as `Abnormal`
- The Crash Free Session Rate will show 100% since native `Crashed` status is unavailable
- Monitor both `Unhandled` and `Abnormal` session rates to track stability issues
Loading