# fix\(mobile\): track render failure by flag and exit cold-launch crashes · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/d330f4f1d826881f2c761e485337977f6aea9ea2)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: d330f4f1d826881f2c761e485337977f6aea9ea2

Requested commit: d330f4f1d826881f2c761e485337977f6aea9ea2

Commit: d330f4f1d826881f2c761e485337977f6aea9ea2

Tree: 42f6ed8c11a3723632396e60b53581e3780255af

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(mobile): track render failure by flag and exit cold-launch crashes

Two audit findings on the boundary:
- The thrown value doubled as the failure sentinel, so `throw
  undefined`/`null`/`""` rendered no fallback. Failure now lives in a
  dedicated flag in a pure, testable state model; falsy throws fail the
  boundary.
- A cold-launch crash on the only route had no previous route to pop to and
  Settings lived inside the failed subtree. The screen fallback now offers
  Open settings (outside the boundary, leading to the Diagnostics tab) when
  navigation cannot go back.

```

## Parents

- [bf13cdf74fb61e4736eed2043cc5487e86e9ce64](https://git.cafe/pingdotgg/t3code/commit/bf13cdf74fb61e4736eed2043cc5487e86e9ce64?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/d330f4f1d826881f2c761e485337977f6aea9ea2?format=markdown)