The DNS resolution failed because I was offline to reproduce the error.
DNS requires the internet to resolve names to IP, hence the error.

To reproduce the error, I intentionally unplugged my wan conn from my router. So I was offline. Other SDKs do similar checks but fail silently. I like using expo, I only wish the offline experience could be better, that's all.

This is what i meant. expo start without the --offline flag, the default behaviour is to reach out to api.expo.dev and fail if it can't. While the Expo Go app will freeze up regularly or just won't work sometimes without an internet connection.

I was referring to devs working with the Expo Go app. Even without that, the --local should be be the default.

2024: Nothing Phone 2A ($350) 👏

I'm excited to see what the best value option is and what features it offers. I'm hoping for more features than last year at the same price, or at least the same features at a lower price. Either way, I'm looking forward to checking it out!

@expo.dev Please 🙏, Let devs work on their projects without and internet connection. Not all devs using @expo.dev can afford to call home to the @expo.dev servers every-time they need to add a button on a page.

@expo.dev Please 🙏, Let devs work on their projects without and internet connection. Not all devs using @expo.dev can afford to call home to the @expo.dev servers every-time they need to add a button on a page.

No more Expo 🙏. Most devs are shocked to realise they can't open or work their apps unless they have an internet connection using Expo. React Native needs an opensource offline first experience like expo.
@swmansion.com #expo #reactnative #react

Saw this coming. when will the public at large starting taking this seriously?