Expo Go 57: Login Requirement for Development Mode

What Changed

Expo Go has introduced a significant update in its latest version, Expo Go 57, which now requires users to be logged in to both the Expo CLI and the Expo Go app to run projects in development mode. This change is currently applicable to the iOS version of Expo Go and is expected to extend to the Android version in the future. The update aims to streamline the development process by ensuring that users are authenticated across both platforms, thus providing a more secure and integrated experience.

When using npx expo start and scanning a QR code with your camera app, you will need to ensure that you are logged in on both the terminal and the Expo Go app. If not, you will encounter prompts guiding you to log in. For the terminal, you can execute npx expo login and follow the link to log in via your web browser. For the Expo Go app, navigate to the home screen, tap the avatar icon in the upper right corner, and enter your Expo credentials.

This login requirement does not apply to simulator versions or development builds, offering some flexibility for developers who prefer these environments for testing. However, for those using physical devices, this change represents a new layer of authentication that must be managed.

For more details, refer to the official Expo changelog: Expo Go 57 Changelog.

Who is Affected

The new login requirement affects several roles within the development workflow:

• Developers: Those working on Expo projects will need to adjust their workflows to include the login step when using physical devices. This change impacts the initial setup and ongoing development cycles.
• CI/CD Pipelines: Continuous Integration and Continuous Deployment (CI/CD) systems that rely on Expo Go for testing will need to incorporate authentication steps to ensure seamless operation.
• Mobile Teams: Teams developing mobile applications using Expo will need to ensure that all members have access to the necessary credentials and understand the new login process.

Marketplace Impact

For a multi-app marketplace like Good Food Pro, which includes customer, driver, and restaurant apps built with Expo, this update has several implications:

• Development Workflow: Teams will need to incorporate the login step into their development workflows. This means ensuring that all developers have access to Expo accounts and understand the login process. This is crucial for maintaining productivity and avoiding disruptions during development.
• Testing and QA: The requirement to log in on physical devices means that testing processes may need adjustment. QA teams will need to ensure that devices are properly authenticated before testing begins, particularly when testing features like live courier tracking and real-time updates via Socket.IO.
• Security Considerations: With the introduction of login requirements, security becomes a more prominent consideration. Teams must manage credentials securely, possibly integrating with existing identity management systems to streamline authentication across the development environment.
• Documentation and Training: Updating internal documentation and providing training on the new process will be essential. This ensures that new developers can onboard smoothly and that existing team members are aware of the changes.

For more insights into building and managing white-label delivery apps, explore our EAS Build blog.

Action Checklist

1. Update Expo CLI: Ensure all developers are using the latest version of Expo CLI to support the new login requirements.
2. Account Setup: Verify that all team members have active Expo accounts and understand how to log in both via the CLI and the Expo Go app.
3. CI/CD Integration: Update CI/CD pipelines to handle Expo login, ensuring automated processes can authenticate as needed.
4. Device Management: Implement a process for managing device logins, especially for shared testing devices in QA environments.
5. Security Practices: Review and enhance security practices around credential management to protect against unauthorized access.
6. Documentation and Training: Update internal documentation and provide training sessions to familiarize the team with the new requirements.

When to Ignore

There are scenarios where this update may not significantly impact your workflow:

• Simulator Use: If your development and testing primarily occur on simulators, you can continue without interruption as the login requirement does not apply.
• Development Builds: If you rely on development builds rather than Expo Go for testing, this update will not affect your current processes.
• Non-Expo Projects: If your projects do not utilize Expo Go, this change will not impact your workflow.

For those interested in exploring more about our multi-app marketplace solutions, visit our Good Food Pro page for more information.

For a deeper dive into managing courier tracking and real-time updates, check out our Socket.IO blog.

If you're interested in seeing how these changes can be implemented in a real-world scenario, consider scheduling a demo with us at Good Food Pro.