Upgrade to React Native 0.85.3 / Expo SDK 56 (new architecture)

[peachbits]

Summary

Upgrades edge-react-gui from React Native 0.79.2 → 0.85.3 (Expo SDK 53 → 56), moving both platforms to the new architecture and removing the reanimated v3/v4 platform split.

Android was previously pinned to reanimated 3 on the old architecture via a local scripts/r3-hack crutch (iOS already ran reanimated 4 on the new arch). This drops the crutch so the whole app runs reanimated v4 on the new architecture, and brings RN, Expo, and the RN-ecosystem dependencies up to current.

Commits (structured for review)

1. Upgrade to React Native 0.85.3 and Expo SDK 56 — JS/deps/tests: dependency bumps, reanimated-split removal, jest preset + worklets resolver, snapshot updates.
2. Android: build under React Native 0.85 with the new architecture — newArchEnabled, compile/target SDK 35→36, Expo SDK 56 autolinking, MainApplication unwrap.
3. iOS: build and run under React Native 0.85 / Expo SDK 56 / Xcode 26 — Expo autolinking + new-arch Podfile (iOS 16.4), ExpoReactNativeFactory AppDelegate, RCTNewArchEnabled.

Split by area (JS / Android / iOS) so each commit independently passes precommit (the native changes don't affect tsc/tests).

Performance — Android, Flashlight, physical device

Crutch removal + new arch + the RN bump measurably improved Android scroll performance:

During scroll	Baseline (rea3 / old arch / 0.79)	After (rea4 / new arch / 0.85)
Jank (frames <30 fps)	7.3%	2.5%
Worst-case FPS (p10)	33.3	48.1
Peak scroll CPU	326%	201%
RAM mean / peak	456 / 704 MB	662 / 827 MB

Net: jank floor 33 → 48 fps (+44%), jank −66%, peak CPU −38%, total CPU −42% — at a RAM cost (the new-arch tradeoff).

Testing

• tsc --noEmit: clean (0 errors)
• Unit tests: 517 / 517 pass (88 suites)
• iOS: builds under Xcode 26 and verified running on the iOS 26 simulator (boots, new-arch runtime, app navigable)
• Android: release build benchmarked on a physical device (table above)

Notes

• RN-upgrade only — the react-native-zcash SPM migration is a separate PR.
• RCTNewArchEnabled (Info.plist) is what enables the new-arch runtime on iOS.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest@​30.0.0 ⏵ 29.7.0
	@​react-native/​metro-config@​0.79.2 ⏵ 0.85.3	+1		+1	+1
	@​react-native/​typescript-config@​0.79.2 ⏵ 0.85.3			+10	+1
	@​react-native-community/​cli@​18.0.0 ⏵ 20.1.0	+1	+75	+1
	@​react-native/​jest-preset@​0.85.3
	expo@​53.0.20 ⏵ 56.0.12			+23
	react-native-safe-area-context@​5.6.1 ⏵ 5.7.0
	@​types/​react@​19.1.9 ⏵ 19.2.17
	@​babel/​core@​7.28.0 ⏵ 7.29.7		+1	+1
	react-native-gesture-handler@​2.28.0 ⏵ 2.31.2			+1
	react-test-renderer@​19.0.0 ⏵ 19.2.3	+1		+1
	@​react-native-firebase/​app@​20.5.0 ⏵ 25.1.0			+1
	@​react-native-firebase/​messaging@​20.5.0 ⏵ 25.1.0			+1
	@​react-native/​babel-preset@​0.79.5 ⏵ 0.85.3	+1		+1
	@​react-native-picker/​picker@​2.11.2 ⏵ 2.11.4
	react@​19.0.0 ⏵ 19.2.3
	react-native-worklets@​0.6.1 ⏵ 0.8.3	+1		+2
	@​react-native-community/​netinfo@​11.4.1 ⏵ 12.0.1
	react-native-keyboard-controller@​1.19.0 ⏵ 1.21.6			+1	+2
	@​react-native-async-storage/​async-storage@​1.19.4 ⏵ 2.2.0			+16	-1
	react-native-svg@​15.14.0 ⏵ 15.15.4	+1
	react-native-bootsplash@​6.3.8 ⏵ 6.3.12	-10
	react-native-reanimated@​3.19.5 ⏵ 4.3.1	+1		+1
	typescript@​5.0.4 ⏵ 5.8.3	+1		+1
	@​react-native-community/​datetimepicker@​8.4.2 ⏵ 9.1.0				-4
	react-native-vision-camera@​4.7.2 ⏵ 4.7.3				+2
	react-native-webview@​13.15.0 ⏵ 13.16.1			+1	+1
	@​react-native-community/​cli-platform-android@​18.0.0 ⏵ 20.1.0
	@​react-native-community/​cli-platform-ios@​18.0.0 ⏵ 20.1.0
	@​sentry/​react-native@​7.12.0 ⏵ 7.11.0	+1			+1
	react-native@​0.79.2 ⏵ 0.85.3	+12
	react-native-screens@​4.16.0 ⏵ 4.25.2	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @expo/cli is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/expo@56.0.12 → npm/@expo/cli@56.1.16 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@expo/cli@56.1.16. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @react-native/debugger-frontend is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/react-native@0.85.3 → npm/expo@56.0.12 → npm/@react-native/debugger-frontend@0.85.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-native/debugger-frontend@0.85.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @react-native/debugger-frontend is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/react-native@0.85.3 → npm/expo@56.0.12 → npm/@react-native/debugger-frontend@0.85.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-native/debugger-frontend@0.85.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @sentry-internal/feedback is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@sentry/react-native@7.11.0 → npm/@sentry-internal/feedback@10.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@sentry-internal/feedback@10.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @sentry/browser is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@sentry/react-native@7.11.0 → npm/@sentry/browser@10.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@sentry/browser@10.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @sentry/core is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@sentry/react-native@7.11.0 → npm/@sentry/core@10.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@sentry/core@10.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm node-forge is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/expo@56.0.12 → npm/@walletconnect/web3wallet@1.10.1 → npm/node-forge@1.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@1.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm react-native-bootsplash is 75.0% likely obfuscated Confidence: 0.75 Location: Package overview From: package-lock.json → npm/react-native-bootsplash@6.3.12 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-native-bootsplash@6.3.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Low adoption: npm fetch-nodeshim Location: Package overview From: package-lock.json → npm/expo@56.0.12 → npm/fetch-nodeshim@0.4.10 ℹ Read more on: This package | This alert | What are unpopular packages? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Unpopular packages may have less maintenance and contain other problems. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/fetch-nodeshim@0.4.10. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report