I see that there have been other reports of this issue in the last few weeks but it remains.
@Hardik said in one of the other threads the issue wasn’t reproducible on their end and this could be because the error is with the server configuration (CORS) and not the app itself.
We tried debugging this across browser, IPs and different ISP, but weren’t able to find this issue. It will be great if you can provide a bit more help here, for us to solve this as early as possible.