Add [Tab Loss] Add info to tab restore logs to see if the app previously crashed #27150
+1
−1
Conversation
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
Cramsden
requested review from
issammani,
FilippoZazzeroni and
mattreaganmozilla
and removed request for
issammani
Client.app: Coverage: 35.47
Generated by 🚫 Danger Swift against 3e72b32 |
mattreaganmozilla
approved these changes
Jun 9, 2025
FilippoZazzeroni
approved these changes
Jun 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
I noticed that Sentry has some information about if the app crashed at last launch. I was hoping by adding this information to the tab restore log we might understand if the reason we are restoring tabs so often is connected to the app crashing or not.
🎥 Demos
Demo
📝 Checklist
@Mergifyio backport release/v120)