fix(settings): read the build number from expo-application

The row said '1.0.0 (dev)' on a build stamped 2026081502.

Constants.nativeBuildVersion is deprecated in SDK 57 and returns nothing — not an
error, not a throw, just undefined, so the fallback fired and the screen reported the
opposite of the truth with complete confidence. A deprecation that quietly returns
undefined is the worst kind: everything looks like it is working.

expo-application is the documented replacement and reads the value from the bundle at
runtime, which is the number OAS stamps before signing.

Also removes the last use of expo-constants here, and with it the '1.0.0' half — the
marketing string that has never changed and cannot tell two builds apart.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-15 00:21:12 +01:00
co-authored by Claude Opus 5
parent e7e2d8c6b7
commit e3024a7818
3 changed files with 14 additions and 2 deletions
+1
View File
@@ -18,6 +18,7 @@
"@expo/vector-icons": "15.1.1",
"@react-native-async-storage/async-storage": "2.2.0",
"expo": "57.0.8",
"expo-application": "^57.0.2",
"expo-clipboard": "57.0.1",
"expo-constants": "57.0.7",
"expo-dev-client": "57.0.9",