“Can’t reproduce” is the most expensive phrase in mobile development. Every team has lost days chasing a bug where the screenshot lacked the logs, the logs lacked the network request and nobody remembers which build it happened on.

In this roundtable, we’ll explore how mobile teams reconstruct the context around a bug from signals scattered across an application. What information should we capture when something goes wrong? How can we correlate UI state, logs and network activity into a consistent snapshot? How do we do this without affecting performance? And where is the line between useful diagnostic data and user privacy?

We’ll share approaches, tools, production lessons and failures, with the goal of leaving with practical ideas for making the next “can’t reproduce” bug easier to diagnose.