Reviews of a secondhand marketplace app keep saying "it gets slow and then closes." How do you connect crash logs with performance traces to decide which problem to fix first?
Symbolicate the crash logs to read the exception type and the crashed thread's stack, then join hang time and memory peak data on common axes, same app version, same screen, same device class, same session, to check whether they form one user flow like "memory climbs on the chat list until it hits the limit and the app dies," and fix first whatever hits the largest share of users at the highest rate.
Performance and debuggingShort answerBasics
A user sends you a crash log and it only has hex addresses instead of function names…
#crash #symbolication
Performance and debuggingShort answerBasics
You get an alert that crashes spiked in the version you shipped yesterday. What do you…
#crash
Performance and debuggingMultiple choiceBasics
A crash report shows EXC_BREAKPOINT (SIGTRAP). In a Swift app, which of these situations…
#crash
Performance and debuggingMultiple choiceExpert
Which of these can an app actually receive through MetricKit (MXMetricManager)? Select…
#crash