FeaturedThread timeline
Why a bug only happens sometimes, and how to reproduce it
A bug that fires on maybe one tap in eight is usually a race whose timing you can't control locally. Here is how to force it and record the run that broke.
Workflow
Connect
By team
Learn
Resources
Every page here starts from a symptom, explains the real causes, and shows the one piece of runtime evidence that pins it down.
10 use cases7 topics
10 use cases
FeaturedThread timeline
A bug that fires on maybe one tap in eight is usually a race whose timing you can't control locally. Here is how to force it and record the run that broke.
Screen capture
A crash or blank screen on a fresh install that never recurs comes from empty first-run state that vanishes the instant you relaunch and the app writes it.
Crash report
App crashes on launch only on iOS 18 usually come from a stricter runtime check or a changed system value. A missing dyld symbol rarely explains that.
Rendered layout
Your UI fits a 6.7-inch simulator but clips on the iPhone SE, the shortest modern iPhone at 667 points. Why short screens break the layout, and how to see it.
Network waterfall
API calls pass in TestFlight but 404, stall on TLS, or fail in the App Store build. The cause is a runtime environment difference the request record exposes.
Screen capture
An update that breaks for only some users is new code meeting old persisted on-device state; reproduce it by upgrading over the old build, not installing fresh.
Screen capture
Your iOS app forgets the session and screen after the user switches away and returns, because iOS terminated the suspended process and nothing restored it.
Network waterfall
A spinner that never resolves means the request never returned, the response was dropped, or the loading flag never cleared; a runtime record tells you which.
Memory curve
Memory climbs every time you open a screen and never falls back, then iOS jetsams the app with no crash log. The curve shape tells you which leak it is.
FPS trace
A long list scrolls clean for a screen, then snags: main-thread work during cell reuse (decode, layout, formatting) blows the frame budget. Read the FPS trace.
Choose a supported model and OS pair, run the flow, and read the full record of what happened.