Do not always write startup crash marker #3409
Merged
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.
馃摐 Description
CurrentDateProvider
uses uptime millis, therefore we were always writing the crash marker file and always blocking SDK init. This is a regression from when we introduced app start spans馃挕 Motivation and Context
Found out this accidentally while testing
馃挌 How did you test it?
Manually + automated
馃摑 Checklist
sendDefaultPII
is enabled.馃敭 Next steps