Skip to content

UX: More Details on Why Connection to Node Failed #116

@ChristopherA

Description

@ChristopherA

I’m experiencing a bad day with Gordian & tor today. My Gordian Server mainnet full node is on same network, and I just added it to Kill Switched Gordian Wallet.

I have yet to be able to connect to my own full node, and I there is no way from information available in error to know how to diagnose. I get a “timed out” dialogue than this error on the main pane…

4917D7A5-FC11-4094-AC64-A78D142DD4A4

My UX concern is like some other errors messages lately is it doesn’t say what to do to fix it. It does not say “pull to refresh” or other such message. It gives no diagnosis code or option to see more error details.

In particular as this type of problem happens a lot, and the problem may be ours, or a more general network problem, we need to offer users more details.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions