A hiring manager asks: "How do you find out there's a memory leak in an app that's already shipped, not one you're developing?" Answer separately for local tools and production signals.
In production you suspect a leak when the MetricKit memory metric climbs with session length or Organizer's memory limit terminations rise in one version, then confirm it locally with the Memory Graph and Leaks.
Performance and debuggingMultiple choiceBasics
For an app already on the App Store, which of these are ways to detect and collect…
#production #crash #metrickit #organizer
Performance and debuggingShort answerBasics
You get an alert that crashes spiked in the version you shipped yesterday. What do you…
#crash #organizer
Performance and debuggingMultiple choiceExpert
Which of these can an app actually receive through MetricKit (MXMetricManager)? Select…
#crash #metrickit
Performance and debuggingShort answerBasics
A user sends you a crash log and it only has hex addresses instead of function names…
#crash