Expo Go on iOS now requires matching sign-ins in Expo CLI and the app for development testing. UAE teams should update onboarding, but Android and development builds are not affected yet.
UAE agencies and mobile teams using Expo should update their developer onboarding and iPhone testing checklist now. The change is real, but it is narrower than the headline suggests: the latest Expo Go release for iOS requires developers to sign in to both Expo CLI and the Expo Go app when running projects in development mode. Android and simulator workflows are not affected by this requirement yet. (expo.dev)
Do not rebuild your app or change production architecture because of this announcement. Add the sign-in steps to your team process, test them on an iPhone, and wait before making wider changes.
Expo’s official changelog, dated 3 September 2026, says the Apple App Store version of Expo Go now supports projects running on Expo SDK 57. To run an app in development mode, the developer must be signed in to Expo CLI in the terminal and to Expo Go on the iOS device. Both sides must use the same Expo account. (expo.dev)
If either side is not signed in, a developer may see a login message after running `npx expo start` and scanning the QR code. Expo Go identifies whether the missing login is in the terminal, the app, or both.
A QR code is no longer enough for every iOS Expo Go test session.
The terminal login uses `npx expo login`, which opens a link for signing in through a web browser. The iOS app login is available from the Home tab by tapping the avatar icon in the upper-right corner and entering the Expo account details. Once both sessions use the same account, the developer can scan the QR code again or open the development server from the Home tab. (expo.dev)
For a UAE agency, this changes the first-day setup for employees, contractors and clients who test pre-release builds on iPhones. A new developer who only installs the command-line tools and Expo Go may now stop at the login screen rather than reaching the project.
Update the onboarding document with these checks:
The requirement currently applies only to the latest Expo Go version for iOS. Expo says it will extend the requirement to Android in the future, but the announcement does not give a date. It also says the requirement does not apply to simulator versions. Login is not required for development builds. (expo.dev)
That distinction matters. Teams that test through an iOS simulator, use Android Expo Go, or use development builds do not need to redesign those workflows because of this specific change. Expo also recommends signing in to an Android account because doing so can surface running development servers and allow published projects to load, but that is separate from the new iOS requirement.
The main impact is operational, not commercial. Project managers should add account access and device readiness to the definition of “ready for testing”. Agencies should decide who owns the Expo account used for a client project, how access is handed over, and what happens when a contractor leaves.
Do not put shared passwords in an onboarding document. Instead, use the account access method approved by your organisation and make sure developers can complete the sign-in step before a scheduled review. This is a sensible control for any team that shares devices or works across Dubai, Abu Dhabi and remote locations, but it is a process recommendation rather than a new Expo rule.
If your team is starting a new app or reviewing its testing stack, our websites and mobile apps service is the relevant place to assess the wider delivery setup. This Expo announcement alone is not a reason to move away from Expo.
Yes, but only with a small process update. Add the two-login check, run a clean iPhone test, and record which account the project uses. Do not rush into changing platforms, buying new tools or converting existing projects solely because of this notice.
The honest answer for a wider technical migration is not yet. Android support is not covered by the current requirement, simulators are excluded, development builds are excluded, and Expo has not announced the Android rollout date on the page reviewed here. Revisit the process when Expo publishes further details or when your own team sees a repeated testing failure.
The header image should use the official Expo Go login-error screenshot shown in the changelog, cropped as a clear card rather than used as generic stock imagery. Place the headline over the card in a readable panel. The source is Expo’s own SDK 57 login announcement, which identifies the image as “login errors from Expo Go”.
Add the matching-account check to your onboarding notes and test it on the iPhone models your team actually uses. If you also need help reviewing an Expo-based app delivery workflow, talk to us with the current testing setup; a simpler checklist may be all you need.
Book a free consultation and get a clear roadmap — from company formation to a fully automated digital operation.