chore(deps): bump expo from 55.0.15 to 57.0.10

[dependabot]

Bumps expo from 55.0.15 to 57.0.10.

Changelog

Sourced from expo's changelog.

Changelog

Unpublished

🛠 Breaking changes

• Raise minimum Node.js version to ^22.13.0 (#47202 by @​kitten)

🎉 New features

🐛 Bug fixes

• [iOS] Fix expo/fetch streaming race between URLSession delegate callbacks and startStreaming() that could deliver an empty body on a 200 response, drop chunks, or leave the body stream open. (#47796 by @​idoyana)
• Fix expo/fetch body-stream teardown races: aborting via an AbortSignal now rejects the in-flight read with an AbortError instead of hanging forever, and late native events no longer throw The stream is not in a state that permits enqueue/close from outside any consumer try/catch. (#47573 by @​idoyana)
• [iOS] Fix expo/fetch Response.text() and .arrayBuffer() never settling when the request fails (network drop, abort()) after the response was already delivered. (#48230 by @​zoontek)
• Fix iOS build against React Native 0.87+ by dropping the legacy architecture (bridge) RCTRootViewFactoryConfiguration setup. (#46641 by @​zoontek)
• Adopted the UIKit scene-based life cycle on iOS so apps built with the iOS 27 SDK launch correctly. (#46733 by @​alanjhughes)
• [iOS] Mark ExpoAppSceneDelegate as unavailable in extensions. (#46799 by @​jakex7)
• [iOS] Fix Linking.getInitialURL() returning null and deep links being dropped when a URL cold-starts an app on the UIKit scene life cycle. (#47628 by @​tsapeta)
• [iOS] Mark ExpoAppSceneDelegate as unavailable in iOSApplicationExtension for widgets. (#47894 by @​jakex7)
• [iOS] Add ExpoBundleConfiguration to derive RCTBundleConfiguration from the normalized bundle URL instead of default shared settings singleton (#48010 by @​kitten)
• [iOS] Resolve the dev server port from the RCTMetroPort Info.plist key at runtime so bare projects without expo-dev-client connect to their own Metro instance instead of defaulting to 8081. (#48098 by @​alanjhughes)
• Fix async imports (import(...)) via asyncRequireModule not a thenable instead of a full promise shape (#48550 by @​kitten)

💡 Others

• [Android] ExpoReactHostFactory now passes host handlers' DevSupportManagerFactory to ReactHostImpl. (#47637 by @​alanjhughes)
• [macOS] Fix build by guarding the bundleConfiguration override, which requires react-native 0.84+. (#48494 by @​intergalacticspacehighway)
• Restore RCTHostRuntimeDelegate conformance for react-native-macos (#46420 by @​gabrieldonadel)
• Add explicit react-native/Libraries/Core/InitializeCore import to native runtime entrypoint (#46344 by @​kitten)
• [Internal] Update logbox imports (#46640 by @​kitten)
• Re-export more expo-modules-core APIs (#45987 by @​Wenszel)
• Update URL and URLSearchParams implementation to support IDNA/TR-46 and improve performance. Spec-adherence has increased and few gaps should now be noticeable compared to browsers (#47813 by @​kitten)
• [Internal] Add getBundleOrigin, exposed as expo/internal/bundle-origin (#48275 by @​kitten)
• [Internal] Derive getDevServer from the bundle URL internally and expose getBundleUrl helper (#48278 by @​kitten)

57.0.9 - 2026-07-29

This version does not introduce any user-facing changes.

57.0.8 - 2026-07-22

🐛 Bug fixes

• [Android] Fixed expo-fetch race condition causing out-of-order delivery of initial chunks (#42161 by @​matthieugicquel)

57.0.7 - 2026-07-17

🐛 Bug fixes

... (truncated)

Commits

• See full diff in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
accounts-site	Ready	Preview	Aug 11, 2026 4:04pm

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	incur@​0.4.26
	expo@​57.0.10
	wagmi@​3.7.6
	@​types/​node@​26.2.0
	@​cloudflare/​vite-plugin@​1.51.1
	@​tanstack/​react-query@​5.101.4
	@​vitejs/​plugin-react@​6.0.5

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 @react-native/debugger-frontend is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/expo-web-browser@55.0.14 → npm/expo-secure-store@55.0.13 → npm/expo@57.0.10 → npm/@react-native/debugger-frontend@0.86.2 ℹ 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.86.2. 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: pnpm-lock.yaml → npm/expo-web-browser@55.0.14 → npm/expo-secure-store@55.0.13 → npm/expo@57.0.10 → npm/@react-native/debugger-frontend@0.86.2 ℹ 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.86.2. 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 yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@react-native-async-storage/async-storage@3.0.2 → npm/react-native-mmkv@4.3.1 → npm/expo-web-browser@55.0.14 → npm/expo-secure-store@55.0.13 → npm/@privy-io/react-auth@3.25.0 → npm/react-native-nitro-modules@0.35.9 → npm/wagmi@3.7.0 → npm/expo@57.0.10 → npm/yargs@17.7.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/yargs@17.7.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.

View full report

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/tempoxyz/accounts@739

commit: 3b1ec67