Wallet connect on new wallet freshly installed does not work #207

Closed
opened 2026-05-28 11:59:23 +00:00 by totdking · 10 comments
totdking commented 2026-05-28 11:59:23 +00:00 (Migrated from gitlab.com)
No description provided.
totdking commented 2026-05-28 12:22:26 +00:00 (Migrated from gitlab.com)

mentioned in issue #147

mentioned in issue #147
totdking commented 2026-05-28 12:26:51 +00:00 (Migrated from gitlab.com)

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

  1. Install a new instance of the Station wallet extension
  2. Open the application
  3. Click Connect Wallet in the header
  4. Attempt to connect the station wallet after installation
  5. Observe the error message displayed

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:

Screen Recording 2026-05-28 at 13.17.53.mov


Environment Details

Field Value
OS macOS (Apple M1 Pro, 14-inch)
Browser Google Chrome (desktop)
Network localterra (local Docker)
Frontend VITE_NETWORK=local npm run dev

Wallet / Device Details

  • Wallet: Station wallet (newly installed)
  • Connection Method: Direct wallet connection

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

### 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 1. Install a new instance of the Station wallet extension 2. Open the application 3. Click **Connect Wallet** in the header 4. Attempt to connect the station wallet after installation 5. Observe the error message displayed --- ### 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: ![Screen Recording 2026-05-28 at 13.17.53.mov](/uploads/fee41cbdd4e0ccba558b5c381df4a054/Screen_Recording_2026-05-28_at_13.17.53.mov) --- ### Environment Details | Field | Value | |-------|-------| | OS | macOS (Apple M1 Pro, 14-inch) | | Browser | Google Chrome (desktop) | | Network | `localterra` (local Docker) | | Frontend | `VITE_NETWORK=local npm run dev` | --- ### Wallet / Device Details - **Wallet:** Station wallet (newly installed) - **Connection Method:** Direct wallet connection --- ### 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
PlasticDigits commented 2026-05-28 12:34:36 +00:00 (Migrated from gitlab.com)

@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.

@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.
PlasticDigits commented 2026-05-28 12:46:54 +00:00 (Migrated from gitlab.com)

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

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
totdking commented 2026-05-28 12:49:54 +00:00 (Migrated from gitlab.com)

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

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
PlasticDigits commented 2026-05-28 12:50:28 +00:00 (Migrated from gitlab.com)

No, I am investigating the issue. It is a commonly used wallet and must be supported.

No, I am investigating the issue. It is a commonly used wallet and must be supported.
PlasticDigits commented 2026-05-28 14:19:07 +00:00 (Migrated from gitlab.com)

mentioned in commit dba254805b

mentioned in commit dba254805b2657f38c9a794780612549c03dd247
PlasticDigits (Migrated from gitlab.com) closed this issue 2026-05-29 02:46:26 +00:00
PlasticDigits commented 2026-05-29 02:46:27 +00:00 (Migrated from gitlab.com)

Resolved. Terastation wallet does not properly switch chains, so a notice to the user to switch was added.

Resolved. Terastation wallet does not properly switch chains, so a notice to the user to switch was added.
PlasticDigits commented 2026-05-29 02:49:38 +00:00 (Migrated from gitlab.com)

mentioned in issue #208

mentioned in issue #208
Brouie commented 2026-06-10 06:07:07 +00:00 (Migrated from gitlab.com)

mentioned in issue #337

mentioned in issue #337
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-dex-terraclassic#207
No description provided.