Hey, Andrey. When working with Expo, I always encounter with this kind of issues. Particularly when I'm trying to build the app. The docs always help: Upgrade Docs

Step-by-Step Guide to Upgrade from Expo SDK 52 to 53

Major Differences Between SDK 52 and 53

In SDK 53, the New Architecture is enabled by default for all projects, whereas in SDK 52 it was optional. This is a significant change that impacts compatibility with certain libraries. Other major changes include:

1. SDK 53 includes React Native 0.79 and React 19, which bring breaking changes
2. Node 18 reached End-Of-Life, so Node 20+ is recommended for SDK 53
3. Package.json exports field is now enabled by default in Metro bundler
4. Several deprecated packages: expo-av is replaced by expo-video and expo-audio, expo-background-fetch is replaced by expo-background-task
5. Push notifications and Google Maps are no longer supported in Expo Go (they were already warned about in SDK 52)

Upgrade Process

1. Update Expo CLI and EAS CLI (if you use it)

npm i -g eas-cli

2. Update Expo and Dependencies

Install the new SDK and update dependencies:

npx expo install expo@^53.0.0

# Upgrade all dependencies to match the installed SDK version
npx expo install --fix

If you don't use Continuous Native Generation:

# For iOS
npx pod-install

# Apply changes from the Native project upgrade helper
# Visit https://docs.expo.dev/bare/upgrade/ to see the needed changes

4. Verify Environment Requirements

Make sure you have:

• Node 20 or newer (Node 18 reached EOL)
• Xcode 16.2+ for iOS development (Xcode 16.3 is used by default on EAS Build)

5. Run Expo Doctor to Check for Issues

npx expo-doctor@latest

6. Consider Opting Out of New Architecture if Needed

If you encounter issues with the New Architecture, you can opt out temporarily by adding to your app.json:

{
  "expo": {
    "android": {
      "newArchEnabled": false
    },
    "ios": {
      "newArchEnabled": false
    }
  }
}

7. Test Your App

Test your app thoroughly in development mode first:

npx expo start

Common Errors and Solutions

1. Node Standard Library Imports Error

   Error: "The package at 'node_modules\ws\lib\stream.js' attempted to import the Node standard library module 'stream'"

   This is likely related to the new Metro ES Module resolution in SDK 53. You have several options:

   • Update affected libraries to their latest versions
   • Opt out of package.json exports by adding to your metro.config.js:

     module.exports = {
       resolver: {
         unstable_enablePackageExports: false,
       },
     };
     

2. TurboModuleRegistry Errors

   Error: "TurboModuleRegistry.getEnforcing(...): 'PlatformConstants' could not be found"

   This is related to the New Architecture. Try opting out of the New Architecture temporarily as shown in step 6.

3. Dependencies Resolution Issues

   If you encounter dependency resolution issues, try:

   # Remove node_modules and reinstall
   rm -rf node_modules
   npm install
   
   # If that doesn't work, also delete your lockfile
   rm -rf node_modules package-lock.json # or yarn.lock
   npm install
   
   # Clear Metro cache
   npx expo start -c
   

4. Connection Issues with Expo Go

   If your app works in tunnel mode but not in LAN mode:

   • Check if you're using VirtualBox or VPN (can interfere with IP detection)
   • Try finding your actual IP address and manually entering it

Tips for a Smoother Upgrade

1. Consider a backup of your project before upgrading
2. Check compatibility of third-party libraries with SDK 53 and React Native 0.79
3. Test thoroughly on both Android and iOS after upgrading
4. Run `npx expo-doctor` to identify issues
5. If you encounter a specific error with a third-party library, check their GitHub repository for updates or workarounds

I got fix for all the warnings and errors, but this one i don´t understand what is causing the error:

ERROR Warning: TypeError: Cannot read property 'getState' of undefined

This error is located at:

Call Stack
ScreenContentWrapper ()
RNSScreenStack ()
Layout(./_layout.tsx) ()
RNCSafeAreaProvider ()
App ()
ErrorOverlay ()

I don´t sure it the error is in layout.tsx or in index.tsx, because the terminal and Expo Go are different:

I found the line error by using console.log("1"), console.log("2"), console.log("3")...

The error was in this line...

const navigationState = useRootNavigationState();

Here is the code...

import { useRootNavigationState } from "expo-router";

const navigationState = useRootNavigationState();

React.useEffect(() => {

if (!navigationState?.key || !initialized) return;

}, [segments, navigationState, initialized]);

I found this in the Expo Router Docs ():

Deprecated Use useNavigationContainerRef instead, which returns a React ref.

useRootNavigation()
Returns:
null | NavigationContainerRef<RootParamList>

So I replace by:

import { useNavigationContainerRef } from "expo-router";

const navigationRef = useNavigationContainerRef();

React.useEffect(() => {

if (!navigationRef.isReady() || !initialized) return;

}, [segments, navigationRef, initialized]);