question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

paymentId/address discrepancy in ledger_state file - follow up to 2172

See original GitHub issue

Description

Logging as a follow up to https://github.com/brave/brave-browser/issues/2172#issuecomment-456826171 per discussion with @NejcZdovc

We have some users who are in a state where their paymentId/addresses in ledger_state don’t match (the paymentId in ledger_state is not actually associated with the addresses listed) per #1831. We need to fix users who are in this state.

Background/Context for historical purposes: Logged in issue #1831 you’ll see that there was an issue with paymentId and address mismatch after using Restore functionality. This issue was fixed for users going forward, however, we still need to fix users who are already in this mismatched state. That was logged in #2172 as a follow up issue. However, there was some miscommunication where it was thought that the ledger_state file contained the correct addresses, where unfortunately it did not. The fix for 2172 was to have the UI update to reflect what was in ledger_state, but what is in ledger_state is wrong. We need to take an additional step to update the addresses in ledger_state to be the ones that correspond with the paymentId in ledger_state. After this is done, the fix from 2172 should correctly display the addresses in the UI.

Steps to Reproduce

  1. Install 0.56.6 dmg (this is a Beta version)
  2. Launch with clean profile and enable rewards.
  3. Note backup words.
  4. Note addresses displayed in Add Funds.
  5. Note paymentId, addresses, and CARD_ID from ledger_state.
  6. Use restore functionality to Restore a wallet.
  7. Note backup words (they updated to the words from the restored wallet and are different than step 3).
  8. Note addresses in Add Funds (these are still the same as step 4).
  9. Open ledger_state and note paymentId (this was updated, so it’s different than step 5) addresses and CARD_ID (these are all still the same as step 5). At this point, you now have a paymentId/address discrepancy or mismatch. If you were to put the paymentId from step 9 into this URL: https://ledger.mercury.basicattentiontoken.org/v2/wallet/<paymentId> you can see what addresses should be displayed to compare to what is actually displayed.
  10. Update to 0.59.28 Beta version.
  11. Navigate to Rewards page.

Actual result:

  • Backup words for wallet match step 7 and paymentId matches step 9 (pass)
  • Addresses in Add Funds are still the same as steps 4/8 (fail)
  • Addresses and CARD_ID are still the same as steps 5/9 (fail)

Expected result:

Backup words/paymentId for wallet should be accurate Addresses in Add Funds should be updated to be the ones that correspond with the correct paymentID Addresses and CARD_ID should be updated to be the ones that correspond with the correct paymentID

Reproduces how often:

easily with steps above

Brave version (brave://version info)

Brave 0.59.28 Chromium: 72.0.3626.64 (Official Build) beta(64-bit)
Revision eaa9668e80ce5405e7f1902579558ea725c06ca1-refs/branch-heads/3626@{#708}
OS Mac OS X

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds? yes

Website problems only:

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

Additional Information

cc @brave/legacy_qa

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
NejcZdovccommented, Feb 11, 2019

@LaurenWags will check it out and ping you tomorrow to see what is going on

0reactions
LaurenWagscommented, Feb 19, 2019

Verified passed with

Brave 0.60.28 Chromium: 72.0.3626.96 (Official Build) beta(64-bit)
Revision 84098ee7ef8622a9defc2ef043cd8930b617b10e-refs/branch-heads/3626@{#836}
OS Mac OS X

Verification passed on

Brave 0.60.40 Chromium: 72.0.3626.109 (Official Build) (64-bit)
Revision fae8db7ab9280fa6704a59980263c804f809ebd5-refs/branch-heads/3626@{#857}
OS Windows 7

Used test plan from https://github.com/brave/brave-core/pull/1508

Verification passed on

Brave 0.60.40 Chromium: 72.0.3626.109 (Official Build) (64-bit)
Revision fae8db7ab9280fa6704a59980263c804f809ebd5-refs/branch-heads/3626@{#857}
OS Linux
Read more comments on GitHub >

github_iconTop Results From Across the Web

fix users who already restored wallets but UI displays incorrect ...
paymentId/address discrepancy in ledger_state file - follow up to 2172 #3060. Closed. UI is not reflecting updated backup words for wallet (incorrect backup ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found