Every React Native team upgrades eventually, and the question before it is always the same: what is going to break in our code? The release notes list the changes, but they don't tell you which of them touch your app.

So we ran that question over 947 open-source React Native and Expo apps from GitHub, with NativeKeel 's new upgrade command. It reads each project's code and dependencies, matches them against the breaking changes between its version and the newest one (React Native 0.88 / Expo SDK 58), and returns a verdict with file and line.

The result

Verdict Apps Share

Already on the newest line 36 4%

Ready: no breaking change found in their code 226 24%

Several versions behind, nothing found in the newest steps 338 36%

Not ready: at least one upgrade blocker 347 37%

For 345 of those 347 apps (36% of all), the blocker is in code they wrote themselves, before counting native build issues.

What breaks most

Breaking change Apps

StyleSheet.absoluteFillObject removed (React Native 0.85)…