bug: Leap wallet connection does nothing — no popup or error #56

Closed
opened 2026-03-13 03:37:16 +00:00 by Brouie · 7 comments
Brouie commented 2026-03-13 03:37:16 +00:00 (Migrated from gitlab.com)

Description

Clicking Leap in the wallet connection modal produces a click sound but no wallet popup, no signing prompt, and no error message. The UI stays on the modal without any response.

Expected

Leap extension should prompt for connection approval, or show an error if connection fails.

Steps to Reproduce

  1. Install Leap extension
  2. Open bridge.cl8y.com
  3. Click Connect Wallet → Select Leap
  4. Nothing happens — no popup, no error

Environment

  • Browser: Chrome (latest)
  • Leap: installed and active
  • Bridge: v0.1.59+
## Description Clicking Leap in the wallet connection modal produces a click sound but no wallet popup, no signing prompt, and no error message. The UI stays on the modal without any response. ## Expected Leap extension should prompt for connection approval, or show an error if connection fails. ## Steps to Reproduce 1. Install Leap extension 2. Open bridge.cl8y.com 3. Click Connect Wallet → Select Leap 4. Nothing happens — no popup, no error ## Environment - Browser: Chrome (latest) - Leap: installed and active - Bridge: v0.1.59+
Brouie commented 2026-03-13 04:17:47 +00:00 (Migrated from gitlab.com)

mentioned in issue #55

mentioned in issue #55
PlasticDigits commented 2026-03-13 06:57:28 +00:00 (Migrated from gitlab.com)

mentioned in commit abbb827f1a

mentioned in commit abbb827f1a9b8b7bfa0746dae093dbd2720d1906
PlasticDigits commented 2026-03-13 06:57:40 +00:00 (Migrated from gitlab.com)

Fix pushed on branch fix/issue-56-leap-wallet-connection (commit abbb827).

Root causes identified:

  1. Silent error swallowing — TerraWalletModal.handleConnect had an empty catch block. The wallet store had no error state, so connection failures were completely hidden from the user.
  2. No experimentalSuggestChain — Wallets that don't have Terra Classic (columbus-5) built-in would reject the enable() call silently. No chain suggestion was made before connecting.
  3. Missing wallet-specific error messages — Only Keplr and Station had "not installed" messages; Leap and Cosmostation fell through to a generic error.

Changes:

  • Added connectionError state to wallet store + red error banner in TerraWalletModal with dismiss button
  • Added suggestChain.ts — calls experimentalSuggestChain on Keplr/Leap/Cosmostation before enable() to register Terra Classic chain info
  • Added Leap and Cosmostation "not installed" error messages + "no chain info" catch
  • Expanded window.leap/window.keplr type definitions to match actual extension APIs

@Brouie — requesting QA review. To test: install Leap extension, open bridge, click Connect Wallet → Leap. Should now either prompt for connection or show an error message in the modal.

Fix pushed on branch `fix/issue-56-leap-wallet-connection` (commit abbb827). **Root causes identified:** 1. **Silent error swallowing** — `TerraWalletModal.handleConnect` had an empty catch block. The wallet store had no error state, so connection failures were completely hidden from the user. 2. **No `experimentalSuggestChain`** — Wallets that don't have Terra Classic (columbus-5) built-in would reject the `enable()` call silently. No chain suggestion was made before connecting. 3. **Missing wallet-specific error messages** — Only Keplr and Station had "not installed" messages; Leap and Cosmostation fell through to a generic error. **Changes:** - Added `connectionError` state to wallet store + red error banner in TerraWalletModal with dismiss button - Added `suggestChain.ts` — calls `experimentalSuggestChain` on Keplr/Leap/Cosmostation before `enable()` to register Terra Classic chain info - Added Leap and Cosmostation "not installed" error messages + "no chain info" catch - Expanded `window.leap`/`window.keplr` type definitions to match actual extension APIs @Brouie — requesting QA review. To test: install Leap extension, open bridge, click Connect Wallet → Leap. Should now either prompt for connection or show an error message in the modal.
Brouie commented 2026-03-13 11:46:38 +00:00 (Migrated from gitlab.com)

Code changes look good. Can you merge and deploy so I can verify the fix live on bridge.cl8y.com? Need to test Leap connection behavior + error messages in the actual UI.

Code changes look good. Can you merge and deploy so I can verify the fix live on bridge.cl8y.com? Need to test Leap connection behavior + error messages in the actual UI.
PlasticDigits commented 2026-03-13 12:47:33 +00:00 (Migrated from gitlab.com)

Now live in v0.1.59+

Now live in v0.1.59+
Brouie (Migrated from gitlab.com) closed this issue 2026-03-14 00:38:44 +00:00
Brouie commented 2026-03-14 00:38:46 +00:00 (Migrated from gitlab.com)

Verified fixed on deployed build (b28e30d). Leap wallet now prompts for connection approval. experimentalSuggestChain registers Terra Classic chain info before connecting. Error messages display correctly in modal.

Verified fixed on deployed build (b28e30d). Leap wallet now prompts for connection approval. experimentalSuggestChain registers Terra Classic chain info before connecting. Error messages display correctly in modal.
Brouie commented 2026-03-16 01:36:47 +00:00 (Migrated from gitlab.com)

mentioned in issue #57

mentioned in issue #57
Sign in to join this conversation.
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#56
No description provided.