Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[1] ApiInstance, Crypto API Error #304

Closed
wmbutler opened this issue Aug 21, 2017 · 2 comments
Closed

[1] ApiInstance, Crypto API Error #304

wmbutler opened this issue Aug 21, 2017 · 2 comments
Assignees
@svk31
Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design
Milestone
170914

Comments

@wmbutler
Copy link
Contributor

I'm seeing this in my Chrome Browser console log when I load: https://bitshares.org/wallet. It happens when the wallet first loads prior to login.

screen shot 2017-08-21 at 4 32 23 pm
@wmbutler wmbutler added the [3] Bug Classification indicating the existing implementation does not match the intention of the design label Aug 21, 2017
@wmbutler wmbutler added this to the 170914 milestone Aug 21, 2017
@svk31
Copy link
Contributor

svk31 commented Aug 23, 2017

I think this is from an API server that is incorrectly configured, wss://bitshares.crypto.fans/ws

@wmbutler
Copy link
Contributor Author

I think we should either remove misconfigured servers or throw a more meaningful message, like:

  • wss://bitshares.crypto.fans/ws is inaccessible or misconfigured

@svk31 svk31 self-assigned this Aug 28, 2017
svk31 added a commit to bitshares/bitsharesjs-ws that referenced this issue Aug 31, 2017
@svk31
Don't catch the crypto API error, bitshares/bitshares-ui#304
cdb3ea0
svk31 added a commit that referenced this issue Aug 31, 2017
@svk31
Update bitsharesjs, #346, fix #304
5230a80
@svk31 svk31 closed this as completed in e5a376d Aug 31, 2017
@svk31 svk31 mentioned this issue Aug 31, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svk31 svk31

Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design
Projects
None yet
Milestone
170914
Development

No branches or pull requests
2 participants
@wmbutler @svk31