New update available, downloading...

camplify · March 2, 2021, 2:22am

It seems that the details above don’t provide a permanent fix. The key seems to be in changing the resolution.

Using ‘Open in pop-up view’, letting it load in, and then changing back to full-screen view solved the issue each time.

divone · March 8, 2021, 10:47am

When I run into this issue, I fix it by deleting the node_modules folder and running npm install again. Fixed it everytime so far.

snackabilitydev · March 18, 2021, 8:05pm

Thank you! This seems to work for us as well (currently opening up in split-screen as a workaround), I wonder what could be causing this? It seemed to work fine before the expo go update.

amazar · April 22, 2021, 8:53pm

Same issue !!

Expo CLI 4.4.3 environment info:
System:
OS: macOS 11.2.3
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.16.0 - /usr/local/bin/node
npm: 6.14.11 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
IDEs:
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
npmPackages:
expo: ~41.0.1 => 41.0.1
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.1
react-native: https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz => 0.63.2
react-native-web: ~0.13.12 => 0.13.18
npmGlobalPackages:
expo-cli: 4.4.3
Expo Workflow: managed

Please Help !!

notbrent · April 22, 2021, 8:59pm

github.com

expo/fyi/blob/main/manual-debugging.md

# How to narrow down the source of an error: a step by step guide to good old fashioned manual debugging

You’re stuck. You keep getting an error and you have no idea why. Debugging tools have failed you. Error messages are vague and unhelpful. Ideally your development tools would help you out, but right now they’re just not giving you what you need. Google yields no helpful results. You don’t know how to proceed. Should you quit software development? Should you copy and paste the error message into StackOverflow, forums, Twitter, Slack, Discord, and every other resource you can think of? Not yet! First, let’s find exactly what lines of code are the perpetrators of this crime.

## 1. Verify that you can run your app on a previously working commit

First, you should find out if you can get an old version of your code working. Save your current changes to a branch, then check out the last known working commit. Reinstall your dependencies and clear out anything from your git index if it’s dirty (maybe some leftover files from some work you were doing before that you didn’t want to commit, for example).

Ok, does that work? It should, because modern package managers like npm and yarn both include lockfiles and so you should be installing the exact same versions of your dependencies, and git is pretty good at ensuring that your code is the same as you left it when you committed it.

If it does not work, it’s time to debug your system environment or an external service. Did you change versions of any software recently? Did you change the redirect URI on your OAuth provider endpoint? Did you sign in to a different account in your development tool? Your gut reaction will be to say “no” - you’re frustrated and looking for something external to blame, I know this very well because this is often me. Fight that and take a step back and verify anything that seems relevant. Maybe you updated to a new version of Node, npm, or yarn, or maybe you installed a new version of a CLI tool.

You know at this point that the issue is not with the code in your project, but you may still find the “disassemble and reassemble” section below to be useful to trace it further if you’re not sure where to look.

## 2. Narrow down the specific changes that cause your error

If you were able to get a previously working commit running, then you can pat yourself on the back because your project is working again. It’s comforting to know that at the end of the day you can always go back to this state.

But that is often not so helpful, because presumably you had made some changes that you wanted. So we have two options for how to proceed now: incrementally add or remove changes, or disassemble reassemble. Over time and repeated application, you’ll get an intuition for which situations are best suited for a particular approach. Regardless of the strategy, you should always be able to identify the specific changes that cause the error. You may not understand the root cause, but this information is vital for your next research steps and for getting help or reporting a bug if needed.

This file has been truncated. show original

rnexposushil123 · May 12, 2021, 11:34am

How to fix Android SDK manager tool not found | how to install Android SDK Tools (Obsolete) 2020 - YouTube Try this video, it had helped me. You guys could try for this same problem

cyphire · July 15, 2021, 3:07pm

Had a similar problem when working in the app.json and app.config.js files.

No matter what I did there was an error.

Removed the expo app from the device, and reinstalled expo.

Stopped the expo server, restarted it.

Turned out there was a configuration issue which finally showed up (was looking for app.json when I had renamed it, and named it back). Server got confused even when re running it with cache clear (expo start -c).

REMOVED expo from phone, then reinstalled from play store, New update available, downloading went away and it ran perfectly. I’ve seen this before, sometimes you just need to remove expo from the phone and reinstall it.

hosar · July 19, 2021, 7:06pm

Same same error here!
Mac OS Darwin
Expo-cli: 4.8.1
Android Emulator

tnylee · July 27, 2021, 12:28pm

Any updates on this? Looks like a lot of people are experiencing the same problem.

nvbach91 · October 26, 2021, 10:31pm

This happedned to me when upgrading from SDK42 to SDK43, the problem is below.

The solution was to delete the node_modules folder and yarn.lock file and run yarn again

Start afresh and also it is better to log in to you expo account in Expo Go on your device

jest-haste-map: Haste module naming collision: rxjs/ajax
  The following files share their name; please adjust your hasteImpl:
    * <rootDir>\_node_modules\rxjs\ajax\package.json
    * <rootDir>\_node_modules\rxjs\src\ajax\package.json

Failed to construct transformer:  DuplicateError: Duplicated files or mocks. Please check the console for more info
    at setModule (C:\dev\roject\node_modules\jest-haste-map\build\index.js:543:17)
    at workerReply (C:\dev\project\node_modules\jest-haste-map\build\index.js:614:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 36172)
    at C:\dev\project\node_modules\jest-haste-map\build\index.js:426:22 {
  mockPath1: '_node_modules\\rxjs\\ajax\\package.json',
  mockPath2: '_node_modules\\rxjs\\src\\ajax\\package.json'
}
Error: Duplicated files or mocks. Please check the console for more info
    at setModule (C:\dev\project\node_modules\jest-haste-map\build\index.js:543:17)
    at workerReply (C:\dev\project\node_modules\jest-haste-map\build\index.js:614:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 36172)
    at C:\dev\project\node_modules\jest-haste-map\build\index.js:426:22
Error: Duplicated files or mocks. Please check the console for more info
    at setModule (C:\dev\project\node_modules\jest-haste-map\build\index.js:543:17)
    at workerReply (C:\dev\project\node_modules\jest-haste-map\build\index.js:614:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 36172)
    at C:\dev\project\node_modules\jest-haste-map\build\index.js:426:22
Error: Duplicated files or mocks. Please check the console for more info
    at setModule (C:\dev\project\node_modules\jest-haste-map\build\index.js:543:17)
    at workerReply (C:\dev\project\node_modules\jest-haste-map\build\index.js:614:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 36172)
    at C:\dev\project\node_modules\jest-haste-map\build\index.js:426:22
› Stopped server
Done in 193.77s.

jonatanlessa · October 27, 2021, 2:47am

Quando aparecer a mensagem: “New update available, downloading…” fecha o Expo e muda no browser a conexão de LAN para Tunnel. Abre o Expo novamente no celular e vai em Recently opened que provavelmente vai funcionar.

archmind · November 7, 2021, 10:00pm

I have similar problem. When running on hardware devices my app works as intended however when i publish to a release channel it is stuck on the splash screen with “new update available, downloading”. I have attempted the solution “expo upgrade, delete node_modules folder and yarn.lock file, run yarn” which did not fix the issue.

archmind · November 8, 2021, 12:29am

I fixed it finally by rearranging pages in the navigation Container. I don’t know why this fixed the problem but it did. Maybe this will work for someone else.

meshackm · November 8, 2021, 11:00am

How were you’re pages arranged before and how did you re-arrange them ??
I have the same issue

archmind · November 9, 2021, 4:15am

there was no discernable pattern to it. I just had a hunch because i removed the page and suddenly it started working again. so i swapped that page with the one above it and it worked again.

barryloh · November 22, 2021, 6:32am

The team and I were having this problem too when trying to load the published app on Expo Go (both Android and iOS). We tried everything - reinstalling the app, clearing caches, logout/login, restart phone but nothing works. This problem started happening to us when we upgraded to the latest Expo SDK43.

We finally managed to fix it by resolving a library dependency issue with @react-native-picker/picker. Our application had v2 of @react-native-picker/picker, and v2 of native-base installed.

We tried to upgrade the version of native-base but still had an error when trying to run Expo locally.

Error on Android:

Error on iOS:
Sorry, I am not able to upload image as I am still a new user to this forum.
But the error message is similar to Android:
“Uncaught Error: Tried to register two views with the same name RNCPicker”

All the problems went away after we uninstalled @react-native-picker/picker library and use the Picker component from native-base. We could run the app perfectly fine locally, as well as on Expo Go

maurorog · February 8, 2022, 12:29pm

The problem is the presence of Drawer.Navigator.
In my app.tsx I have …

  const Stack = createNativeStackNavigator();
  return (
    <NavigationContainer>
      <Stack.Navigator
        initialRouteName="Home"
        screenOptions={{
          headerShown: false,
          headerTitleAlign: "center",
          headerStyle: {
            backgroundColor: "#0080ff",
          },
        }}
      >
        <Stack.Screen name="InsertData" component={InsertMonthData} />
        <Stack.Screen name="Home" component={Home} />
      </Stack.Navigator>
    </NavigationContainer>
  );

If I add this in my home component, debugging no longer works

  return (
    <Drawer.Navigator>
      <Drawer.Screen
        name="DataManagement"
        options={{ title: "Data" }}
        component={DataManagement}
      />
      <Drawer.Screen
        name="Stats"
        options={{ title: "Statistics" }}
        component={ScreenB}
      />
    </Drawer.Navigator>
  );

If I replace with a simple one

  return (
    <View>
      <Text>Works !!!</Text>
    </View>
  );

the debugger works

gregauger · May 11, 2022, 4:13pm

In my case, I am getting the error as a result of an issue with EAS Update: Expo Go on Android fails when EAS Update enabled · Issue #17461 · expo/expo · GitHub

ljubcoder · July 27, 2023, 5:08pm

I was able to resolve the issue by removing the version property in app.json under expo.

{
  "expo": {
    "version": "1.0.0"
}
}

removing version did the trick for me.

Topic		Replies	Views
expo-update server down? Expo SDK updates	7	511	October 15, 2022
Android release with Splash problem (Upgrade to Expokit 33) (Deprecated) Help: ExpoKit	9	714	August 3, 2019
Upgrade to SDK 40 failed, now SDK 39 giving unseen errors after rollback Expo Development Tools	2	639	March 8, 2021
Expo not bundling the app and not reloading Expo SDK	3	1684	November 26, 2018
Unable to open the expo apk Expo Development Tools updates	7	1863	January 26, 2023

New update available, downloading...

Related Topics