In my Expo app, I handled cases where the user loses connection. They will get an alert and components will change. It was working in Expo experience but in my standalone app it is not working.
I switched off my network connection and was hit with an error page:
There was a problem loading this experience.
Error: The Internet connection appears to be offline.
Error Code: CLIENT_LOADING_ERROR
Status Code: -1009
Are we not able to have offline features in our apps or maybe I am doing something wrong?
Hey @mc10 - your assumption is right, your app should have no trouble from the expo side running offline. Could you post your app.json and a little more information about the steps that are taking you to this error? (e.g. are you getting this on the first run after installing, or have you successfully launched the app before with internet? Are you testing on a device or simulator?)
Hi, thanks for the response! My app.json looks something like this:
"description": "App description",
I had opened and run the app a few times already. I am running on an iPad device with Wifi capabilities only. The app is currently being deployed through TestFlight. The steps I am following are like so:
- I open my app from the iOS homescreen
- I get to the initial screen which opens WebBrowser for SSO
- I pass through authentication and get in to the app
- I swipe up and open iOS 11 Control Center and disable Wifi
- I go back to the app
- I hit the error page
One interesting thing is that I am also detecting connection loss on the initial page before the WebBrowser is launched and it will tell them a network connection is required to sign in. This switch is working here when I turn off the Wifi but switching anywhere else inside the app is not.
Hmm, this sounds like it could be a bug. Could you confirm that you are using the latest version of
exp (currently 49.2.2)? If not, try updating that and building again. But if you are, could you provide a minimally reproducible test case and post an issue to https://github.com/expo/expo/issues ?
Sorry for the inconvenience! Hopefully we can get this resolved soon.
After further testing, I believe it may actually just be a bug on my side. Will definitely know after the next build but I think that’s the case. Thanks for your time!
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.