Persist LastRunInfo and populate app.isLaunching for JVM errors #1165
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.
Goal
Persists the
LastRunInfo
so that previous launch information can be retrieved by the user. This also sets the value ofapp.isLaunching
on JVM events.The implementation of this behaviour for NDK errors will be done in a separate changeset to ease review.
Changeset
LaunchCrashTracker
, which tracks the state of whether the application is currently launching or notLastRunInfoStore
, which loads and saves theLastRunInfo
object from disk in the key-value formatLastRunInfo
to the defaults onClient
initializationLastRunInfo
whenever an unhandled exception occurred so that the next launch allows the user to check that the app crashedTesting
Added unit tests for new classes. Updated JVM events to assert that the
app.isLaunching
field is set to the correct default.E2E tests for the NDK and when
markLaunchCompleted()
are called will be added in a separate PR.