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
{{ message }}
This repository has been archived by the owner on Aug 15, 2023. It is now read-only.
If the skapp url is given in the form https://siasky.net/skylink (e.g. as produced by siasky.net web interface), then skyid.sessionStart() changes window.location.href and the web page is reloaded. After that, skyid.sessionStart() execution stops and no code is executed after that.
However, there is a short delay before the page is reloaded. Within that time, it is possible to see an error message in the console saying: "TypeError: Cannot read property 'focus' of null". Most probably, this is thrown in popupCenter() where newWindow object is undefined. (This is just an observation, which is probably not 100% related to the issue).
When the page reloads, no message is broadcast, and the app has no chance to know what has happened, so the login just fails for no obvious reason.
The second time, from the redirected url, everything works.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If the skapp url is given in the form https://siasky.net/skylink (e.g. as produced by siasky.net web interface), then
skyid.sessionStart()
changeswindow.location.href
and the web page is reloaded. After that,skyid.sessionStart()
execution stops and no code is executed after that.However, there is a short delay before the page is reloaded. Within that time, it is possible to see an error message in the console saying: "TypeError: Cannot read property 'focus' of null". Most probably, this is thrown in
popupCenter()
wherenewWindow
object is undefined. (This is just an observation, which is probably not 100% related to the issue).When the page reloads, no message is broadcast, and the app has no chance to know what has happened, so the login just fails for no obvious reason.
The second time, from the redirected url, everything works.
The text was updated successfully, but these errors were encountered: