BlockchainCommons / BlockchainCommons/GordianWallet-iOS
UX: More Details on Why Connection to Node Failed
- Dominant language
- Swift
- Stars
- 46
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
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…
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.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing the timed-out node connection error shown in the main pane, then define the diagnostic details and recovery guidance users should see; done means the failure explains likely causes and what action to take.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100