Fragment binding after destroy
An AI wrote this Android Fragment to load a profile and update a TextView. It works in normal use, but testers who rotate the device or back out quickly during the load see occasional crashes with `IllegalStateException` / `NullPointerException`, and you suspect the binding. What's the bug and how would you catch it?
Implement
simulate_fragment_updates(event_lines: list[str], use_view_scope: bool) → list[str]Examples
in
[["create","start:a","complete:a"],false]out["updated:a"]in
[["create","start:a","destroy","complete:a"],false]out["crash:a"]in
[["create","start:a","destroy","complete:a"],true]out["cancelled:a"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 18 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.