You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2024. It is now read-only.
In 1.52.x we moved some of the Ledger code on the core side to use mojo, which surfaced an issue with the current legacy wallet migration code and possible threading problems
Steps to Reproduce
On 1.51 and lower: Enable rewards, then go to Rewards Debug settings and tap on "Create Legacy Wallet"
Update to 1.52
Launch and observe crash
Reproduces how often: Easily
Brave Version: 1.52
The text was updated successfully, but these errors were encountered:
The Ledger code in brave-core behaves like a singleton as it uses a global pointer to log, so we can't have more than 1 created. Creating a legacy wallet to do migrations was now crashing because ledger changes in 1.52 to use mojo now expose threading errors.
The Ledger code in brave-core behaves like a singleton as it uses a global pointer to log, so we can't have more than 1 created. Creating a legacy wallet to do migrations was now crashing because ledger changes in 1.52 to use mojo now expose threading errors.
…ve/brave-ios#7465)
The Ledger code in brave-core behaves like a singleton as it uses a global pointer to log, so we can't have more than 1 created. Creating a legacy wallet to do migrations was now crashing because ledger changes in 1.52 to use mojo now expose threading errors.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description:
In 1.52.x we moved some of the Ledger code on the core side to use mojo, which surfaced an issue with the current legacy wallet migration code and possible threading problems
Steps to Reproduce
Reproduces how often: Easily
Brave Version: 1.52
The text was updated successfully, but these errors were encountered: