I installed the Blockstack browser on Windows. But I can't sign in with my Blockstack ID

It keeps on saying "SIGNING IN…"
I left it for an hour and still signing in! Is there something wrong with the Windows version?

Hey @walowaiyesh, sorry to hear you’re having trouble!

Our back-end servers were under some heavy loads these past couple days, but we’ve been hard at work getting them fixed. We recently released a new version of the Windows browser. Can you try downloading the latest one (v0.20.1) and trying to sign in again?

Hi,

I have the same login issue on Ubuntu.
The browser console is showing some errors (see below).
There is no long load time. So looks more like a frontend error?

main.js:163710 Uncaught TypeError: Cannot read property ‘__reactInternalInstance$p9itwixv917’ of null
at Object.getClosestInstanceFromNode (main.js:163710)
at findParent (main.js:166133)
at handleTopLevelImpl (main.js:166162)
at ReactDefaultBatchingStrategyTransaction.perform (main.js:170630)
at Object.batchedUpdates (main.js:165855)
at Object.batchedUpdates (main.js:168796)
at dispatchEvent (main.js:166242)
main.js:209034 2017-11-05T02:16:23.223+0800 ERROR window.addWindowListener(‘error’): { isTrusted: [Getter] }
main.js:209034 2017-11-05T02:16:23.223+0800 ERROR window.onerror: Uncaught TypeError: Cannot read property ‘__reactInternalInstance$p9itwixv917’ of null [TypeError: Cannot read property ‘__reactInternalInstance$p9itwixv917’ of null]
TypeError: Cannot read property ‘__reactInternalInstance$p9itwixv917’ of null
at Object.getClosestInstanceFromNode (http://localhost:8888/js/main.js:163710:11)
at findParent (http://localhost:8888/js/main.js:166133:32)
at handleTopLevelImpl (http://localhost:8888/js/main.js:166162:28)
at ReactDefaultBatchingStrategyTransaction.perform (http://localhost:8888/js/main.js:170630:20)
at Object.batchedUpdates (http://localhost:8888/js/main.js:165855:26)
at Object.batchedUpdates (http://localhost:8888/js/main.js:168796:27)
at dispatchEvent (http://localhost:8888/js/main.js:166242:20)
main.js:163710 Uncaught TypeError: Cannot read property ‘__reactInternalInstance$p9itwixv917’ of null
at Object.getClosestInstanceFromNode (main.js:163710)
at findParent (main.js:166133)
at handleTopLevelImpl (main.js:166162)
at ReactDefaultBatchingStrategyTransaction.perform (main.js:170630)
at Object.batchedUpdates (main.js:165855)
at Object.batchedUpdates (main.js:168796)
at dispatchEvent (main.js:166242)

Found a clue as to what might be happening.
The browser console is throwing the error below.
Looks like there is an unrecognizable character

2017-11-05T02:23:29.565+0800 ERROR window.onerror: Uncaught SyntaxError: Unexpected token � in JSON at position 0 [SyntaxError: Unexpected token � in JSON at position 0]
SyntaxError: Unexpected token � in JSON at position 0
at JSON.parse ()
at decodeToken (http://localhost:8888/js/main.js:94248:21)
at AuthModal.componentWillMount (http://localhost:8888/js/main.js:3711:54)
at ReactCompositeComponentWrapper.performInitialMount (http://localhost:8888/js/main.js:161912:14)
at ReactCompositeComponentWrapper.mountComponent (http://localhost:8888/js/main.js:161819:21)
at Object.mountComponent (http://localhost:8888/js/main.js:168036:35)
at ReactCompositeComponentWrapper.performInitialMount (http://localhost:8888/js/main.js:161932:34)
at ReactCompositeComponentWrapper.mountComponent (http://localhost:8888/js/main.js:161819:21)
at Object.mountComponent (http://localhost:8888/js/main.js:168036:35)
at ReactDOMComponent.mountChildren (http://localhost:8888/js/main.js:167440:44)

Yeah, looks like it. These kinds of problems usually indicate that some localStorage state is left over from an earlier release of the Browser. Can you try the following?

  • Make sure you’re on the latest browser release (v0.20.1)
  • Clear localStorage (or open an Incognito window)
  • Enter your backup-phrase when prompted.

i don’t see any option to enter backup-phrase.
What does the UI look like?

btw, I also tried stopping the container.
And now it can’t start.

able to reinstall with my keychain.
However, I still get the same browser error (see below).

BLOCKSTACK_STATE_VERSION is 12

the error seems to be coming from this code in main.js

function consoleAppender (layout, timezoneOffset) {
layout = layout || layouts.colouredLayout;
return function(loggingEvent) {
consoleLog(layout(loggingEvent, timezoneOffset));
};
}

2017-11-05T14:50:09.539+0800 ERROR window.onerror: Uncaught SyntaxError: Unexpected token � in JSON at position 0 [SyntaxError: Unexpected token � in JSON at position 0]
SyntaxError: Unexpected token � in JSON at position 0
at JSON.parse ()
at decodeToken (http://localhost:8888/js/main.js:94248:21)
at AuthModal.componentWillMount (http://localhost:8888/js/main.js:3711:54)
at ReactCompositeComponentWrapper.performInitialMount (http://localhost:8888/js/main.js:161912:14)
at ReactCompositeComponentWrapper.mountComponent (http://localhost:8888/js/main.js:161819:21)
at Object.mountComponent (http://localhost:8888/js/main.js:168036:35)
at ReactCompositeComponentWrapper.performInitialMount (http://localhost:8888/js/main.js:161932:34)
at ReactCompositeComponentWrapper.mountComponent (http://localhost:8888/js/main.js:161819:21)
at Object.mountComponent (http://localhost:8888/js/main.js:168036:35)
at ReactDOMComponent.mountChildren (http://localhost:8888/js/main.js:167440:44)

Hey @skybach,

Apologies for the delay. If you’re still using Ubuntu, I’ve posted a Linux Walkthrough link that takes users through the process end-to-end. It also addresses the problem of the container not starting up again :slight_smile:

The JSON-decoding error you’re seeing is most likely due to an invalid authentication token getting loaded. Just want to confirm that you cleared localStorage from the developer console?

If you’re still having trouble, we now have a Web-hosted version. Details can be found here. Hope this helps!

yes, I tried the walkthrough and also clearing localStorage.
Still getting the same issue.

Think I will wait till issue is resolved.
Don’t feel secure using the “webbed” version.

I downloaded the blockstack-core and blockstack-browser to run on the machine to do further debugging.
Noticed that for some reason, the token is returning a string prepended with 3 slashes.
Hence when the token is split for decoding

at decodeToken (http://localhost:8888/js/main.js:97784:21)

an error occurs.
If I remove the 3 slashes, decoding returns a valid json object.

Why does the login error seem to occur only for Linux?
Was the code base different for different OS or the data returned different for the OSes?

There are some known issues with protocol handlers in Linux. Are you using the docker install or building from source? Also it would be hugely helpful if you could open an issue on Blockstack Browser with that information!

I was using Docker. Guess the launcher script helped to install the protocol handlers.
Then I proceeded with testing the source.
So behaviour was the same.

I just tried modifiying blockstack.desktop protocol handler
from
Exec=bash -c 'xdg-open http://localhost:8888/auth?authRequest=$(echo “%u” | sed s/blockstack://)'
to
Exec=bash -c ‘xdg-open http://localhost:8888/auth?authRequest=$(echo “%u” | sed s^blockstack:///^^)’

Have submitted an issue at
https://github.com/blockstack/blockstack-browser/issues/1118

1 Like