Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web3 account is locked if no provider is set #8119

Closed
srirambv opened this issue Feb 7, 2020 · 1 comment
Closed

Web3 account is locked if no provider is set #8119

srirambv opened this issue Feb 7, 2020 · 1 comment
Labels

Comments

@srirambv
Copy link
Contributor

srirambv commented Feb 7, 2020

Description

Web3 account is locked if no provider is set

Steps to Reproduce

  1. Clean profile on 1.6.7 nightly
  2. Create local CW account
  3. Set to Roptsen network and click on deposit
  4. Web3 complains that account is locked
  5. Reload the page, notification shows up to setup

Actual result:

image
image

Expected result:

Web3 provider should be prompted before the script can be injected

Reproduces how often:

Easy

Brave version (brave://version info)

Brave 1.6.7 Chromium: 80.0.3987.87 (Official Build) nightly (64-bit)
Revision 449cb163497b70dbf98d389f54e38e85d4c59b43-refs/branch-heads/3987@{#801}
OS Windows 10 OS Version 1803 (Build 17134.523)

Version/Channel Information:

  • Can you reproduce this issue with the current release? No
  • Can you reproduce this issue with the beta channel? No
  • Can you reproduce this issue with the dev channel? No
  • Can you reproduce this issue with the nightly channel? Yes

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? NA
  • Does the issue resolve itself when disabling Brave Rewards? NA
  • Is the issue reproducible on the latest version of Chrome? NA

Miscellaneous Information:

cc: @bbondy

@bbondy bbondy added the priority/P3 The next thing for us to work on. It'll ride the trains. label Feb 7, 2020
@bbondy
Copy link
Member

bbondy commented Feb 7, 2020

Closing this in favor of this: #8120

@bbondy bbondy closed this as completed Feb 7, 2020
@bbondy bbondy added closed/duplicate Issue has already been reported and removed feature/web3/wallet Integrating Ethereum+ wallet support priority/P3 The next thing for us to work on. It'll ride the trains. regression labels Feb 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants