bug: iPhone Keplr browser may connect unexpected Terra wallet address after switching chain connect order #5

Open
opened 2026-03-01 14:54:08 +00:00 by PlasticDigits · 3 comments
PlasticDigits commented 2026-03-01 14:54:08 +00:00 (Migrated from gitlab.com)

Frontend Bug Report

Issue Title

  • bug: iPhone Keplr browser may connect unexpected Terra wallet address after switching chain connect order

Environment

  • Device Type: Mobile (iOS)
  • Device Model: iPhone (exact model TBD)
  • OS Version: iOS (exact version TBD)
  • Browser Version: Keplr in-app browser (version TBD)
  • Wallet Used: Keplr
  • Network / Chain: BNB Chain + Terra Classic Mainnet
  • Page: Transfer (wallet connect flow)

Steps to Reproduce

  1. Open the bridge in the Keplr browser on iPhone.
  2. Connect BNB Chain wallet first.
  3. Then select/connect Terra Classic (LUNC) wallet.
  4. Observe the connected Terra address shown by the app.
  5. Compare with the intended/expected Terra wallet address in Keplr.

Expected Behavior

  • Terra connection should always use the selected/intended Terra account.
  • Changing chain connect order should not cause address mix-up.
  • BNB and Terra sessions should remain independently correct and stable.

Actual Behavior

  • When BNB is connected first, connecting LUNC can attach an unexpected/random Terra address.
  • Connected Terra address shown in the app may not match the expected user wallet.
  • Behavior appears related to Keplr active wallet/account context when switching chains.

Severity

  • High (incorrect wallet binding risk can cause user confusion and potential transfer mistakes)

Evidence (screenshots / recordings)

  • Attached screenshot shows unexpected Terra address after chain connect order switch.
  • Optional: add short video reproducing BNB-first then LUNC connect flow.

Console Errors (if available)

# Not captured yet (Keplr iOS in-app browser)

Transaction Hash (if applicable)

  • N/A (connection-stage issue)

Source

  • Found during manual QA testing
  • Reported by a user

Auto-uploaded Evidence

## Frontend Bug Report ### Issue Title - bug: iPhone Keplr browser may connect unexpected Terra wallet address after switching chain connect order ### Environment - Device Type: Mobile (iOS) - Device Model: iPhone (exact model TBD) - OS Version: iOS (exact version TBD) - Browser Version: Keplr in-app browser (version TBD) - Wallet Used: Keplr - Network / Chain: BNB Chain + Terra Classic Mainnet - Page: Transfer (wallet connect flow) ### Steps to Reproduce 1. Open the bridge in the Keplr browser on iPhone. 2. Connect BNB Chain wallet first. 3. Then select/connect Terra Classic (LUNC) wallet. 4. Observe the connected Terra address shown by the app. 5. Compare with the intended/expected Terra wallet address in Keplr. ### Expected Behavior - Terra connection should always use the selected/intended Terra account. - Changing chain connect order should not cause address mix-up. - BNB and Terra sessions should remain independently correct and stable. ### Actual Behavior - When BNB is connected first, connecting LUNC can attach an unexpected/random Terra address. - Connected Terra address shown in the app may not match the expected user wallet. - Behavior appears related to Keplr active wallet/account context when switching chains. ### Severity - High (incorrect wallet binding risk can cause user confusion and potential transfer mistakes) ### Evidence (screenshots / recordings) - Attached screenshot shows unexpected Terra address after chain connect order switch. - Optional: add short video reproducing BNB-first then LUNC connect flow. ### Console Errors (if available) ```shell # Not captured yet (Keplr iOS in-app browser) ``` ### Transaction Hash (if applicable) - N/A (connection-stage issue) ### Source - [x] Found during manual QA testing - [ ] Reported by a user ### Auto-uploaded Evidence - [photo_2026-03-01_23-49-28-e0f2977f-df15-4e56-be1f-4ca68ebaceb3.png](https://raw.githubusercontent.com/PlasticDigits/cl8y-qa-evidence/main/2026-03-01/1772376824-photo_2026-03-01_23-49-28-e0f2977f-df15-4e56-be1f-4ca68ebaceb3.png) - ![photo_2026-03-01_23-49-28-e0f2977f-df15-4e56-be1f-4ca68ebaceb3.png](https://raw.githubusercontent.com/PlasticDigits/cl8y-qa-evidence/main/2026-03-01/1772376824-photo_2026-03-01_23-49-28-e0f2977f-df15-4e56-be1f-4ca68ebaceb3.png)
PlasticDigits commented 2026-03-11 06:10:56 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
PlasticDigits commented 2026-03-11 06:10:57 +00:00 (Migrated from gitlab.com)

assigned to @Brouie

assigned to @Brouie
Brouie commented 2026-04-23 03:47:52 +00:00 (Migrated from gitlab.com)

mentioned in issue #116

mentioned in issue #116
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#5
No description provided.