Challenge 3: Which Stack Trace Frame to Start With — Solution Walkthrough

The answer:

The frame from the app's own MainActivity class — not any of the
Android framework frames appearing above it in the stack trace.

Why, per this chapter's own material:

A stack trace is read top to bottom, but per this chapter's own
guidance, the topmost frame that actually belongs to your own app's
code is usually the most useful starting point, rather than the very
first line of the trace. Framework frames represent code inside the
Android platform itself, which you don't control and almost certainly
isn't the actual root cause of a bug in your own app's logic.

Why the app's own frame is the right place to start:

The MainActivity frame represents the closest point in the call chain
that's still under your own control — it's the app's own code that
ultimately triggered whatever framework behavior led to the exception.
Investigating there directly connects the crash back to a specific
line you can actually inspect and fix, rather than starting an
investigation inside framework code you can't modify.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise applies this chapter's own stack-trace-reading guidance
to a realistic trace shape (framework frames above an app frame),
correctly identifying the app's own frame as the practical starting
point rather than simply the first line encountered while reading top
to bottom.