Apologies if I’ve missed it, currently on my phone, but I can‘t find a reason why this would break if I add the sender to one of my contacts?
For example, one bank I use sends messages from “HSBCUKTOKAC”. So I see something less suspicious, I’ve added that to the banks contact details (and don’t get me started on the other weird and stupid things they do).
https://web.dev/web-otp/
“If the sender's phone number is included in the receiver's contact list, this API will not be triggered due to the design of the underlying SMS User Consent API.”
https://developers.google.com/identity/sms-retriever/user-consent/request#2_start_listening_for_incoming_messages
“The message was sent by a phone number that's not in the user's contacts.“
https://github.com/WICG/WebOTP/blob/master/FAQ.md
No mention?
Apologies if I’ve missed it, currently on my phone, but I can‘t find a reason why this would break if I add the sender to one of my contacts?
For example, one bank I use sends messages from “HSBCUKTOKAC”. So I see something less suspicious, I’ve added that to the banks contact details (and don’t get me started on the other weird and stupid things they do).
https://web.dev/web-otp/
“If the sender's phone number is included in the receiver's contact list, this API will not be triggered due to the design of the underlying SMS User Consent API.”
https://developers.google.com/identity/sms-retriever/user-consent/request#2_start_listening_for_incoming_messages
“The message was sent by a phone number that's not in the user's contacts.“
https://github.com/WICG/WebOTP/blob/master/FAQ.md
No mention?