With Chromium Edge lately there has been a CORS issue when connecting to sync.herokuapp.
I think it has to do with the bump of socket io as it introduced "cors: false".
Also the URL set via the options window doesn't work as it's not being used. Not sure why.
So I had to do a workaround to self host but with cors: true connection works as expected.
Hi,
With Chromium Edge lately there has been a CORS issue when connecting to sync.herokuapp. I think it has to do with the bump of socket io as it introduced "cors: false".
Also the URL set via the options window doesn't work as it's not being used. Not sure why. So I had to do a workaround to self host but with cors: true connection works as expected.