Connect wallet does not fire for most of the available wallets #215
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega#215
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue Summary
The connect wallet in any other view than desktop view gives 5 wallet options to connect :
Rainbow,base,metamask,safepalandwallet connect. Out of these only Base actually fires up to connect and even when it does , it gives a loading page with this logskeys.coinbase.com refused to connect.Reproduction Steps
Not reproducible as when the page was refreshed , it started functioning as expected.
Environment Details
runningWallet / Device Details
@Brouie Some users also reporting this bug, but some are not. Very challenging to debug. See if you can replicate.
@totdking Please provide any errors you have from console or ux for more info to debug this issue
mentioned in issue #219
mentioned in issue #220
Walked the repro on production with the overnight fixes landed. All wallets in the modal now fire their extension popups cleanly when clicked.
Tested wallets that all PASS:
Likely resolved by the wallet/RPC connectivity work shipped in #221 (commit
8f69b7b) and the surrounding stack changes from #216. The original totdking report mentioned only Base firing and keys.coinbase.com refused-to-connect — both consistent with the EIP-6963 / window.ethereum race condition that the shipped useRpcConnectivity changes addressed.Cross-references to today's related work:
Bottom line: not reproducible post-fix. Suggest closing this as resolved by the architecture work this week, or leaving open until totdking confirms on his side.