Inconsistent QR scan behavior - byte order mark fails
I've noticed Selene fails to scan QR codes in the following circumstance. When a byte order mark (BOM) is used and no CashAddr prefix is given.
I came across this when a website provided BCH address without a QR code or CashAddr prefix. Because I wanted to get the address to my mobile/Selene, I used QtQR to encode the address and found Selene is unable to scan when there is no prefix and the BOM is included. It appears Selene recognises the QR because it closes the Scan page but returns to the main screen instead of the confirmation screen.
In QtQR, BOM is the default setting.
X marks unable to scan.
| Prefix | No prefix | |
|---|---|---|
| No BOM | ||
| BOM | X |
Example screenshots:
1. BOM with no prefix (default, fails)
2. BOM with prefix
3. No BOM no prefix
It's pretty easy to work around this problem so this is probably a low priority. Most sites include a QR or prefix.