Display toast/alert on web3auth connect errors

Open

#141 opened on Sep 21, 2023 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 45/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: typescript
Domain: authentication

Research direction

Start at src/features/accounts/components/social-login/social-login.tsx around line 101, where the web3auth connection error is logged. Inspect the surrounding social-login error handling and existing user-notification patterns, then show refresh and retry guidance when connection fails. Done means the failure gives the user a toast or alert instead of only a console error.

Written by the indexing model from the issue text.

Description

We're getting the following error on social login when a login fails to connect to web3auth. As of now, there's only a console error message when this happens. We should display a toast or alert to the user when there is a connection error and provide instructions such as refresh your browser, retry, etc.

https://github.com/liftedinit/alberto/blob/3b8894ac14cb3aeb0fd5c3d4ed71ac2996770ab8/src/features/accounts/components/social-login/social-login.tsx#L101

social-login.tsx:101 connectTo error WalletLoginError: Wallet is not connectedNo wallet is connected

connectTo error WalletLoginError: Wallet is not connectedNo wallet is connected
    at Function.value (index.ts:143:12)
    at Function.value (index.ts:155:29)
    at r.<anonymous> (core.ts:175:104)
    at d (regeneratorRuntime.js:72:17)
    at Generator._invoke (regeneratorRuntime.js:55:24)
    at Generator.next (regeneratorRuntime.js:97:21)
    at r (asyncToGenerator.js:3:20)
    at s (asyncToGenerator.js:22:9)
    at asyncToGenerator.js:27:7
    at new Promise (<anonymous>)

Dominant language: TypeScript
Stars: 4
Forks: 7
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Tapping "Use video" more than once submits the verification twice Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

bcgov/bc-wallet-mobile#4761 · 1 comment · Opened Sep 24, 2026
fix(pg-meta): schemas.update and schemas.remove DO blocks fail when a name contains "$$" Open

external-issue to-triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

supabase/supabase#50882 · Opened Sep 24, 2026
Azure Sandboxes: Small and ExtraSmall tiers always fail to deploy (disk request exceeds tier maximum) Open

area-deployment area-integrations triage:bot-seen

Difficulty 2/5 Half a day Newbie friendliness 86/100

microsoft/aspire#20459 · 1 comment · Opened Sep 24, 2026
Mobile builds drop the telemetry and crash-reporting keys, so opting in sends nothing Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

0xMiden/wallet#1118 · Opened Sep 24, 2026
[P3] Handle clipboard failures and announce copy status accessibly Open

refactor

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

nteract/semiotic#1534 · Opened Sep 24, 2026

More TypeScript issues