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

[BUG] Digital Cash Transactions History Wrong Receiver Displayed #1923

Open
1 of 6 tasks
Kaz-ookid opened this issue Jun 12, 2024 · 0 comments
Open
1 of 6 tasks

[BUG] Digital Cash Transactions History Wrong Receiver Displayed #1923

Kaz-ookid opened this issue Jun 12, 2024 · 0 comments
Labels
bug Something isn't working fe2-android

Comments

@Kaz-ookid
Copy link
Contributor

Kaz-ookid commented Jun 12, 2024

Description

When sending coins to another user, and opening the Transaction History (top right corner), we can see the recent send. It displays : To: {$receiver_token_hash}. But this token hash is clearly not the one we sent coins to, and is not even 32 bytes (a PoP Token/Public Key length). This feels wrong and should be investigated.

This only happens for transactions for which we are the sender.

Expected behavior

Display the token of the receiver of the transaction.

How to reproduce

  1. Create a LAO, Join it with another device, create a RollCall, Scan your second device and close the RollCall
  2. Go to Digital Cash
  3. Click on Send and remember the user token
  4. Enter a non-null amount and click on Send
  5. See the Receipt view
  6. Click in the top right corner on the Transaction History icon
  7. See the Transaction History
  8. Click on the recent transaction to deploy the details
  9. See the error (wrong hash of the receiver token)

Version & Environment

This bug was reproduced on:

  • Commit: ...hash... (make sure your working tree is clean and your commit is pushed to the repo)
Front-ends:
  • Fe1-Web (please include browser's names & version)
  • Fe2-Android (please specify if phone or emulation, and Android version)
  • Not applicable
Back-ends:
  • Be1-Go
  • Be2-Scala
  • Not applicable

Impact

Low user experience impact, as it is not a much used feature for now. However, it will be a lot more confusing once we get the username display from #1915.

Possible root cause


This line is responsible of what to display after the To:.
Need to understand where those hashes come from and what they represent, as they can't possibly represent users tokens (less than 32 bytes long)

Screenshots

This is not the token I sent coins to. (the visual bug has been fixed in #1921
image

@Kaz-ookid Kaz-ookid added bug Something isn't working fe2-android labels Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fe2-android
Projects
None yet
Development

No branches or pull requests

1 participant