Oh, indeed with https it works as expected
It’s just that develop.backendless.com is easier to type than https://develop.backendless.com
So I guess redirecting to https by default would solve it, but anyway shouldn’t it preserve login with http as well?
but anyway shouldn’t it preserve login with http as well?
no, web browser uses different LocalStorages for http and https,
When you login from http:// it redirects to social-login, then you will be redirected to https:// and web browser will put user’s auth token into LocalStorage for https and when you try to open another web page (with http) the received token will not be there and as result you can see Login Screen