-
Notifications
You must be signed in to change notification settings - Fork 984
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
"cannot locate account for address: [wallet address]" error when sending TX #10423
Comments
@ceripower |
Hey @churik! Thanks for checking in. I needed to make the transaction urgently so I deleted the app, reinstalled it and tried again and it worked then. Apologies I can't retrieve a log for you relating to the original issue (or is it still helpful if I send something from the now-functioning app?) |
No, thanks! please send us logs if you have this issue in the future. |
this error is happening here in status-go https://github.com/status-im/status-go/blob/8b61d92d5834215fb06532c527b0bead7b4625d9/account/accounts.go#L159 it can't find KeyFile |
as an assumption problem might be in the checksummed address @gravityblast wdyt ? how do we store and finding keyfiles? |
for example, if we're trying to sign tx with checksummed and not address in the from the field will be any difference do you lowercase address? |
@flexsurfer I don't think it can be related because the address received is somehow sanitized with: so they are always converted to an It's also strange that it happens only now, it would be easy if we can reproduce it. |
Bug Report
Problem
It was appeared while sending TX (from Wallet and 1-1 chat). No steps to reproduce so far for
Expected behavior
No errors when sending TXs
Actual behavior
"cannot locate account for address: [wallet address]" error when sending TX
Notes
For the developer who will be investigating. Is it related to another PR? Tips on where to start?
Reproduction
Additional Information
Logs
TBD...
The text was updated successfully, but these errors were encountered: