-
Notifications
You must be signed in to change notification settings - Fork 985
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
qr testing mode, fixed qr pure address and EIP681 issues #10280
Conversation
Pull Request Checklist
|
(js/parseInt chain-id) | ||
(ethereum/chain-keyword->chain-id :mainnet))} | ||
arguments))))))))))) | ||
(if (ethereum/address? s) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only this one small change in this function, added address condition for pure addreses
Jenkins BuildsClick to see older builds (10)
|
99% of end-end tests have passed
Failed tests (1)Click to expand
Passed tests (96)Click to expand |
I just tested the QR code and it's using just the chat key, not the full URL including Are we sure we want to do it that way? With that the QR code is useless for anyone that doesn't have Status installed, and if it was a full URL it would be usable for anyone. |
Could you also take a look at #10306 as part of this? Might affect address scanner. |
this PR is only for status wallet qr scanner. Chat scanner and mailserver scanner are separate so should be done in separate PRs |
That makes sense, but does the wallet scanner handle whitespace/newlines fine? |
Good question :) i need to take a look |
ISSUE 1: In case of error (i.e. wrong network id in the link) empty bottom sheet is openedLink: ethereum:0x4470BB87d77b963A013DB939BE332f927f2b992e@5/transfer?address=0xd21DB0e43048AcB94f428eD61dC244c82f1ff2a8&uint256=1e-5 ISSUE 2: Sometimes after scanning QR-codes from Recipient -> Scan QR app is freezing with opened bottom sheetLink: ethereum:0x4470BB87d77b963A013DB939BE332f927f2b992e@5/transfer?address=0xd21DB0e43048AcB94f428eD61dC244c82f1ff2a8&uint256=1e-5 Steps to reproduce are scan link from Wallet -> QR code and then from Wallet -> Send Transaction -> Choose recipient -> Scan QR code and repeat until get unresponsive app (in my case 3-4 times) Full logcat with 2 freezing: UPD: it does not depend on the place of scanning (Wallet -> QR or Send Transaction -> Recipient -> Scan QR) or link itself - can be reproduced with any link when scanning QR several times. Sometimes it is reproducible from the 1 time. Testing is in progress. |
ISSUE 3:
|
Thank you for making possibility for e2e to scan QR! |
|
95b779a
to
f69b54c
Compare
also fixes #9872 |
882ddac
to
f2b6ee3
Compare
Tested on IOS13 and Android 10:
All mentioned issues are resolved, only ENS name for tokens is not resolved (will be added separately). AWESOME 👍 |
Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
f2b6ee3
to
45dae49
Compare
fixes #10107
fixes #10093
fixes #9183
fixes #8150
fixes #9580
fixes #9872
removed chain usage for tokens
For local and e2e builds, qr scan testing mode implemented, so now we can add e2e for qr codes
Tested with this generator https://brunobar79.github.io/eip681-link-generator/#
FOR QA: all tokens related functionality should be tested, also QR codes , especially value