Wallet connect on new wallet freshly installed does not work #207
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic#207
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
mentioned in issue #147
Issue Summary
Attempting to directly connect a newly installed Station wallet fails. The UI displays the error message: "Failed to connect Station: No wallets connected". This prevents users from using the Station Wallet
Reproduction Steps
Expected Behavior
The application should successfully initiate a successful connected session with the Station wallet, or provide a clear, actionable error message if the wallet needs prior configuration (e.g., creating a wallet profile or unlocking it first).
Actual Behavior
The connection fails immediately with the error:
Failed to connect Station: No wallets connected. The user cannot proceed with authentication via this method.Screen record:
Environment Details
localterra(local Docker)VITE_NETWORK=local npm run devWallet / Device Details
Severity / Impact
Blocker ~"blocker:launch" . Users relying on newly installed Station wallets encounter a hard block when trying to connect. This impacts onboarding for new users or those migrating to a new machine/browser profile.
This prevents me from completely verifying issue https://gitlab.com/PlasticDigits/cl8y-dex-terraclassic/-/work_items/147
cc: @PlasticDigits
@totdking Make sure you create a project id with reown and add to the env before walletconnect testing workflows. Walletconnect does not work without a projectid.
Note on clarification: This is NOT related to walletconnect. This is about connecting the injected terrastation wallet. Note that station wallet has recently been updated, which may be causing old connection hooks/components to no longer work, requrieing exensive research to update and test
The issue of station wallet being updated introduced a myriad of bugs into the application. This is a station wallet problem, if ignoring this for now is okay, We can mark https://gitlab.com/PlasticDigits/cl8y-dex-terraclassic/-/work_items/147 as closed
No, I am investigating the issue. It is a commonly used wallet and must be supported.
mentioned in commit
dba254805bResolved. Terastation wallet does not properly switch chains, so a notice to the user to switch was added.
mentioned in issue #208
mentioned in issue #337