Skip to content

docs(unity): PostExceptionsInEditor defaults to false in 5.0.0 - #332

Draft
bobbyg603 wants to merge 1 commit into
masterfrom
docs/post-exceptions-in-editor-default
Draft

docs(unity): PostExceptionsInEditor defaults to false in 5.0.0#332
bobbyg603 wants to merge 1 commit into
masterfrom
docs/post-exceptions-in-editor-default

Conversation

@bobbyg603

Copy link
Copy Markdown
Member

Note

Hold until bugsplat-unity 5.0.0 ships. Documents the new default from BugSplat-Git/bugsplat-unity#202 (fixes BugSplat-Git/bugsplat-unity#153); merging before the release would describe behavior the published package doesn't have yet.

What

PostExceptionsInEditor defaults to false in bugsplat-unity 5.0.0, so play mode exceptions no longer upload to the shipping database unless the developer opts in.

Two edits to the Unity page, both mirroring the wording added to the bugsplat-unity README in #202:

  • Configuration section: adds a sentence stating the default and how to opt in (checkbox on the options asset, or bugsplat.PostExceptionsInEditor = true in code) while verifying an integration.
  • Options table: the PostExceptionsInEditor row now states the default and why.

The getting-started sample flow ("click Play" → report appears) is unaffected — the imported sample's BugSplatOptions asset explicitly enables the setting.

🤖 Generated with Claude Code

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

F5: PostExceptionsInEditor defaults to true and pollutes production databases

2 participants