feat: fix expo example

[florrdv]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR focuses on updating dependencies, enhancing configuration files, and making adjustments to the project structure for a React Native application.

Detailed summary

• Updated react-native-config, @react-native-community/cli, and added @react-navigation/elements.
• Enhanced metro.config.js to handle .js/.jsx extensions in TypeScript files.
• Modified package.json dependencies, including updates to expo, react-native, and react-native-screens.
• Updated Podfile.lock to reflect new versions for various pods.
• Adjusted project.pbxproj to include new files and update existing ones.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
aa-sdk-ui-demo	Ready	Preview	Comment	Sep 6, 2025 5:13am

[graphite-app]

How to use the Graphite Merge Queue

Add the label graphite-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[github-actions]

🌿 Documentation Preview

Name	Status	Preview	Updated (UTC)
Alchemy Docs	✅ Ready	🔗 Visit Preview	Sep 6, 2025, 5:10 AM

[graphite-app]

There's a potential race condition in the authentication flow. Currently, setAwaitingOtp(true) is executed immediately after initiating the async authenticate() call, without waiting for its completion. If the authentication request fails, the UI will still transition to the OTP input screen even though no OTP was actually sent.

Consider moving the state update inside a success callback or adding error handling to reset the state:

onPress={() => {
  signer
    .authenticate({
      phone,
      type: "sms",
    })
    .then(() => {
      setAwaitingOtp(true);
    })
    .catch((error) => {
      console.error(error);
      // Optionally show an error message to the user
    });
}}

This ensures the UI state accurately reflects the authentication process status.

Suggested change

	onPress={() => {
	signer
	.authenticate({
	phone,
	type: "sms",
	})
	.catch(console.error);
	setAwaitingOtp(true);
	}}
	onPress={() => {
	signer
	.authenticate({
	phone,
	type: "sms",
	})
	.then(() => {
	setAwaitingOtp(true);
	})
	.catch((error) => {
	console.error(error);
	// Optionally show an error message to the user
	});
	}}

Spotted by Diamond



Is this helpful? React 👍 or 👎 to let us know.