code/cl8y-bridge-monorepo

Fork 0

bug: Station wallet connection fails — No wallets connected #57

New issue

Closed

opened 2026-03-16 01:36:46 +00:00 by Brouie · 3 comments

Brouie commented

2026-03-16 01:36:46 +00:00

(Migrated from gitlab.com)

Description

Clicking Station in the wallet connection modal fails with 'Failed to connect Station: No wallets connected'. The extension is installed and active.

Error

Wallet connection failed: Error: Failed to connect Station: No wallets connected

Expected

Station extension should prompt for connection or show a clear error about chain support.

Steps to Reproduce

Install Station extension
Open bridge.cl8y.com
Click Connect Wallet → Station
Error: No wallets connected

Notes

Dev flagged Station as important ('terrastation is popular'). May need experimentalSuggestChain similar to the Leap fix in #56.

Environment

Browser: Chrome (latest)
Station: installed and active
Bridge: b28e30d

## Description Clicking Station in the wallet connection modal fails with 'Failed to connect Station: No wallets connected'. The extension is installed and active. ## Error `Wallet connection failed: Error: Failed to connect Station: No wallets connected` ## Expected Station extension should prompt for connection or show a clear error about chain support. ## Steps to Reproduce 1. Install Station extension 2. Open bridge.cl8y.com 3. Click Connect Wallet → Station 4. Error: No wallets connected ## Notes Dev flagged Station as important ('terrastation is popular'). May need experimentalSuggestChain similar to the Leap fix in #56. ## Environment - Browser: Chrome (latest) - Station: installed and active - Bridge: b28e30d

Brouie commented

2026-03-16 04:18:37 +00:00

(Migrated from gitlab.com)

mentioned in issue #58

PlasticDigits commented

2026-03-16 07:30:48 +00:00

(Migrated from gitlab.com)

Fix deployed. Station now gets experimentalSuggestChain called before connecting, same approach as the Leap fix in #56. This teaches the extension about columbus-5 so getKey no longer fails silently.

@Brouie can you verify with Station extension installed? Connect should now either succeed or show a clear chain-support error instead of the generic 'No wallets connected' message.

Fix deployed. Station now gets `experimentalSuggestChain` called before connecting, same approach as the Leap fix in #56. This teaches the extension about columbus-5 so `getKey` no longer fails silently. @Brouie can you verify with Station extension installed? Connect should now either succeed or show a clear chain-support error instead of the generic 'No wallets connected' message.

Brouie (Migrated from gitlab.com) closed this issue

2026-03-17 02:54:28 +00:00

Brouie commented

2026-03-17 02:54:30 +00:00

(Migrated from gitlab.com)

Verified fixed on 55b1989. Station connects successfully after switching to Terra Classic (columbus-5) network. Error message now properly indicates chain mismatch when on wrong network.

Verified fixed on 55b1989. Station connects successfully after switching to Terra Classic (columbus-5) network. Error message now properly indicates chain mismatch when on wrong network.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

code/cl8y-bridge-monorepo#57

No description provided.

Rows
Columns