You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using useIsConnected in an application and in the past two weeks have noticed several devices that use this to have failed network calls, but oddly they are pointed at /sorry/index with a 405 error code. We aren't applying a custom endpoint to hit so it should just be hitting the default google.com. Has anyone seen this before or know why this may be happening?
Expected Behavior
I would expect to never hit /sorry/index.
How to reproduce
Not known. Out of > 1000 devices this has only happened a couple dozen times.
Your Environment
software
version
react-native-offline
5.8.0
react-native
0.64.2
node
14.19
npm or yarn
yarn 1.22.18
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
For what it's worth, I get 405 errors when trying to use this package in a web context (localhost:3000), the 405s are coming from failed preflight requests. The actual requests are failing with CORS errors - is there any documentation on how to configure your local development environment for web integration of this package?
Current Behavior
I'm using
useIsConnected
in an application and in the past two weeks have noticed several devices that use this to have failed network calls, but oddly they are pointed at/sorry/index
with a 405 error code. We aren't applying a custom endpoint to hit so it should just be hitting the defaultgoogle.com
. Has anyone seen this before or know why this may be happening?Expected Behavior
I would expect to never hit
/sorry/index
.How to reproduce
Not known. Out of > 1000 devices this has only happened a couple dozen times.
Your Environment
The text was updated successfully, but these errors were encountered: