fix: Potential app launch hang caused by the SDK #6181
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
Remove unused crash report fields binary_cpu_type and binary_cpu_subtype so we can also remove the call to _dyld_get_image_header, which lead to app launch hangs for a customer. Still, these
fields might be useful and we can readd them with GH-6180.
💡 Motivation and Context
Quick fix for #6180
💚 How did you test it?
binary_cpu_subtype
andbinary_cpu_type
, so we test that if previous reports contain this info, we handle it correctly.📝 Checklist
You have to check all boxes before merging:
sendDefaultPII
is enabled.