Replies: 1 comment 2 replies
-
Here are some relevant logs as well. Flask Socketio is receiving the message, but the handlers are not being used
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We recently upgraded a number of dependencies to our Flask application. During this process, we also adjusted the way we initialize the map in local development.
Flask socketio is still functioning just fine on remote environments, as that is being launched through wsgi.py
But locally, nothing is working. There are no errors, but connection requests from SocketIO are timing out and returning 400 responses. Which made me think this might be a CORS issue. But on local, we are allowing all (*) origins
It seems the cause must be somewhere in the app configuration process. I've tried a number of different approaches, but nothing has worked. Perhaps someone has experienced a similar issue?
Here is how we are now running the dev server.
Note, socket_instance is defined as
Beta Was this translation helpful? Give feedback.
All reactions