Conversation
Enable offline persistence by default for Initialize(url) on WebGL. Move offline replay and syncfs to BacktraceDatabase. Write ahead persist to PlayerPrefs queue and handle rate-limiting correctly.
rick-bt
approved these changes
Jan 30, 2026
Contributor
rick-bt
left a comment
rick-bt
left a comment
There was a problem hiding this comment.
Code walkthrough. Approved.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
WebGL users can lose unsent reports when Backtrace is initialized while offline.
Changes
BacktraceClient.Initialize(url)now enables offline persistence by default on WebGL runtime builds.offline replayand filesystemflushlogic fromBacktraceClientintoBacktraceDatabaseto match SDK architecture and separation of concerns.write-ahead persistenceto thePlayerPrefsbacked fallback queue before sending to prevent data loss when the send callback never executes due tobrowser lifecycle teardown.rate-limiting: Do not delete on-disk database records whenLimitReachedand do not count toward retry attempts (applies to both on-disk DB and fallback queue).FS.syncfscalls on database write/delete and lifecycle hooks via.jslib.Sample Reports
ref: BT-6427