Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Latest Master Branch: Invalid Token - UI does display token modal #5745

Closed
CraigglesO opened this issue Jun 1, 2017 · 4 comments
Closed
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust.

Comments

@CraigglesO
Copy link
Contributor

Blocked connection from http://localhost:8180 using invalid token.
even using --ui-no-validation or --ws-origins all I can't get the parity to work with the UI. No modal to give a valid token showing up.

@5chdn
Copy link
Contributor

5chdn commented Jun 2, 2017

Probably related to #5722 - should we track this in one ticket?

@5chdn 5chdn added F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. labels Jun 2, 2017
@tomusdrw
Copy link
Collaborator

tomusdrw commented Jun 2, 2017

It's fixed in #5710, let's track it as one.

@tomusdrw tomusdrw closed this as completed Jun 2, 2017
@CraigglesO
Copy link
Contributor Author

CraigglesO commented Jun 2, 2017

No, I'm sorry but I think this is a JS issue that has not been resolved even in your PR. I pulled it and I still got:
Connecting to the Parity Node. If this informational message persists, please ensure that your Parity node is running and reachable on the network.
while, obviously it should be asking for a new token to use.

@tomusdrw
Copy link
Collaborator

tomusdrw commented Jun 2, 2017

You need to build with cargo build --release --no-default-features --features ui cause it's indeed JS stuff that I broke and you need to recompile it as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

No branches or pull requests

3 participants