Repository navigation
Help !!! Unable to solve it tried whatever is available in google "The development server returned response error code 500 #931
Description
Describe the bug
error: TypeError: dependencies is not iterable
at Graph._resolveDependencies (C:\Users\saahm\OneDrive\Desktop\varcast-app-master\node_modules@react-native-community\cli-plugin-metro\node_modules\metro\src\DeltaBundler\Graph.js:452:23)
at Graph._processModule (C:\Users\saahm\OneDrive\Desktop\varcast-app-master\node_modules@react-native-community\cli-plugin-metro\node_modules\metro\src\DeltaBundler\Graph.js:267:38)
at async Graph._addDependency (C:\Users\saahm\OneDrive\Desktop\varcast-app-master\node_modules@react-native-community\cli-plugin-metro\node_modules\metro\src\DeltaBundler\Graph.js:378:20)
at async Promise.all (index 33)
at async Graph._processModule (C:\Users\saahm\OneDrive\Desktop\varcast-app-master\node_modules@react-native-community\cli-plugin-metro\node_modules\metro\src\DeltaBundler\Graph.js:328:5)
at async Graph._addDependency (C:\Users\saahm\OneDrive\Desktop\varcast-app-master\node_modules@react-native-community\cli-plugin-metro\node_modules\metro\src\DeltaBundler\Graph.js:378:20)
at async Promise.all (index 3)
at async Graph._processModule (C:\Users\saahm\OneDrive\Desktop\varcast-app-master\node_modules@react-native-community\cli-plugin-metro\node_modules\metro\src\DeltaBundler\Graph.js:328:5)
at async Graph._traverseDependenciesForSingleFile (C:\Users\saahm\OneDrive\Desktop\varcast-app-master\node_modules@react-native-community\cli-plugin-metro\node_modules\metro\src\DeltaBundler\Graph.js:255:5)
at async Promise.all (index 0)
Add any other context about the problem here.
Activity
AyJayHam commentedon May 6, 2024
Same error here, running on a Win 11 machine. Works just fine on my Win 10 machine.
natejhowe commentedon May 22, 2024
Did you ever figure this out? I've been banging my head against the wall attempting to debug this error.
natejhowe commentedon May 22, 2024
@Sana720 Delete your Temp folder located here C:\Users{user}\AppData\Local\Temp. Then try again. Fixed it for me.
ivstiv commentedon Jun 5, 2024
Had the same issue today, my Windows bluescreened so that must have corrupted some of my cache. After wiping the Temp folder that @natejhowe mentioned the problem went away!
Manlikevee commentedon Jun 16, 2024
npx expo install --fix fixed it for me
kerimovok commentedon Jul 23, 2024
It helped me too, thx!
Aaqibraza098 commentedon Aug 20, 2024
This one helped . Thanks
mugabe00 commentedon Aug 28, 2024
this one helped me . thanks
shaheer741 commentedon Sep 8, 2024
solved for me
mikeisadev commentedon Sep 16, 2024
I had the same problem and I fixed it right now.
Instead of going into the "Temp" folder inside AppData/Local deleting the interested temp and cache files, you can do the following steps:
npm cache clean --forceto clear the global npm cachenpx expo start --clearto restart the development server and to clear the transformation javascript/typescript/jsx/tsx files starting freshThese commands helped me to solve the problem. Yes, you can go and clear cache files and temp files inside your PC folders inside "AppData/Local/Temp", but this approach will save you time with a direct CLI command.
I want to add more:
If you need to establish a tunnel connection to see your react native app through expo go on your smartphone do this:
npm cache clean --forcenpx expo start --clearnpx expo start --tunnelto restart the server in a tunnelOr you can combine the two last commands
npx expo start --clearandnpx expo start --tunnelintonpx expo start --clear --tunnelafter doingnpm cache clean --force. Butnpx expo start --clear --tunnelgave me errors, so do the step by step procedure dividing the two commands.Hope it helps.
Vinaykpro commentedon Oct 15, 2024
Cool so deleting the temp folder is the only working way for me these cache clean commands didn't fix my problem...
AslamNS commentedon May 13, 2025
this worked for me
Shahtaymur commentedon May 25, 2025
It helped me too, thx!
leostark221 commentedon Jun 17, 2025
Worked for me as well. Thanks it was a different issue but somewhat similar