RichL
November 29, 2021, 9:30pm
1
I created a thread last week about the Brave Wallet not letting me move my money out and I was told that fixes were being rolled out, but it is still not working and I am not able to access my money. When is Brave going to fix this and when am I going to get my money back?
Link to previous post below:
I used to have a Gemini account that stored my BAT, however since Brave launched their integrated wallet, I moved it over to that. I am now trying to move it out, but it will not let me confirm the transaction as the Confirm button is greyed out. What am I doing wrong?
chh_68
November 30, 2021, 8:02am
2
brave:master
← brave:f/wallet/issue-19821
opened 06:04AM - 30 Nov 21 UTC
Resolves https://github.com/brave/brave-browser/issues/19821.
## Submitter Ch… ecklist:
- [x] I confirm that no security/privacy review [is needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have [requested](https://github.com/brave/security/issues/new/choose) one
- [x] There is a [ticket](https://github.com/brave/brave-browser/issues) for my issue
- [x] Used Github [auto-closing keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in the PR description above
- [x] Wrote a good [PR/commit description](https://google.github.io/eng-practices/review/developer/cl-descriptions.html)
- [x] Added appropriate labels (`QA/Yes` or `QA/No`; `release-notes/include` or `release-notes/exclude`; `OS/...`) to the associated issue
- [x] Checked the PR locally: `npm run test -- brave_browser_tests`, `npm run test -- brave_unit_tests`, `npm run lint`, `npm run gn_check`, `npm run tslint`
- [x] Ran `git rebase master` (if needed)
## Reviewer Checklist:
- [ ] A security review [is not needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or a link to one is included in the PR description
- [ ] New files have MPL-2.0 license header
- [ ] Adequate test coverage exists to prevent regressions
- [ ] Major classes, functions and non-trivial code blocks are well-commented
- [ ] Changes in component dependencies are properly reflected in `gn`
- [ ] Code follows the [style guide](https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++.md)
- [ ] Test plan is specified in PR before merging
## After-merge Checklist:
- [ ] The associated issue milestone is set to the smallest version that the
changes has landed on
- [ ] All relevant documentation has been updated, for instance:
- [ ] https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
- [ ] https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
- [ ] https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
- [ ] https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
- [ ] https://github.com/brave/brave-browser/wiki/Custom-Headers
- [ ] https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
- [ ] https://github.com/brave/brave-browser/wiki/QA-Guide
- [ ] https://github.com/brave/brave-browser/wiki/P3A
## Demo
|`ETHSend`|`ERC20Transfer`|
-|-
|<video src="https://user-images.githubusercontent.com/3684187/143994001-6aa2c77f-5000-4dfa-a8d1-d6e7fe64971e.mov">|<video src="https://user-images.githubusercontent.com/3684187/143994009-3f786f82-43b4-4e68-80b0-f5c9c168cadc.mov">|
The hotfix (1.32.113) was released, please try again and maybe post a new issue if an issue still exists since this issue has a couple things mixed in already.
(Following statements are according to me)
They said a fix is coming is a new update. An update was released on 26 Nov which does not seem to have solved the issue. According to the guy who posted the github issue, they are trying to solve it and the fix is under review. So, I think you will still need to wait until the issue is finally fixed and is made available in stable release.
system
Closed
December 30, 2021, 8:03am
3
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.