Yet seen before tonight, a user in the main telegram group reported that seedsigner was not able to verify addresses from their BlueWallet native segwit wallet. Seedsigner was instead looking for a match on a legacy address that starts with 1.

After discussing, this was seen by BlueWallet v7.0.7 iOS (build 1736967217 master)

The qr decoded to something like:
"bitcoin:BC1Q..."
and seedsigner was searching for an address starting with 1, as if it had chopped "bitcoin:BC" from the front of the decoded string.

As soon as I lowercased that string and gave another qrcode to the user, seedsigner matched the address quickly.

This feels buggy on BlueWallet's side... because while uppercase can work with bech32 to make a more efficient qrcode, it doesn't work well with "bitcoin:" in lowercase.

Still, I suspect that seedsigner 1) should not be chopping anything off after "bitcoin:", and 2) it might be more tolerant when it can be sure that the entire address appears to be from the bech32 alphabet.

This looks recent at BlueWallet: Expect more issues.
BlueWallet/BlueWallet#7461