# docs\(mobile\): state the expo-updates startup-error pipeline exactly · pingdotgg/t3code

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

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

Visibility: public

Requested revision: cb480a0f54748c8bf1dc0dd624c5b400b808529e

Requested commit: cb480a0f54748c8bf1dc0dd624c5b400b808529e

Commit: cb480a0f54748c8bf1dc0dd624c5b400b808529e

Tree: 1064e18cb99088f37ed9557b8258bb140d49b02f

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
docs(mobile): state the expo-updates startup-error pipeline exactly

Verified against expo-updates 57.0.19 source: ErrorRecoveryHandler runs
wait-for-remote-update -> launch new update -> relaunch cached older update
-> crash, and CONTENT_APPEARED (Android ReactRootView.onViewAdded, the first
root view render; ExpoUpdatesKit is symmetric) removes the two recovery tasks
at that point. So a render throw that discards the first commit keeps the
whole pipeline available, while any post-first-paint crash never had cached
fallback even before this PR. Comments now say the pipeline, not 'rollback',
and note expo's existing successful-launch-count rule.

```

## Parents

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

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