Google’s SMS retriever API is working fine without the <#> prefix. Why?

Question

according to the Google’s SMS retriever API, the SMS message should start with the <#> prefix, but it's working well for me without it (on multiple phones and system versions). Has anyone ever encountered that and knows why it's possible?

https://android.jlelse.eu/googles-sms-retriever-api-6540eb3c8e9c

What API are you using exatly? Show us some code. – m02ph3u5 Jul 16 '19 at 11:53 — m02ph3u5, Jul 16 '19 at 11:53
Are you using SMS retreiver API or SMS UserConsent API – Lakhwinder Singh Jul 16 '19 at 12:23 — Lakhwinder Singh, Jul 16 '19 at 12:23
@LakhwinderSingh SMS retreiver API. – wlodku Jul 16 '19 at 12:35 — wlodku, Jul 16 '19 at 12:35

score 2 · Answer 1 · answered Dec 24 '19 at 07:14

2

Google has removed the prefix from their API documentation. But I don't know when it was changed.

Here is their latest example of the message content. (https://developers.google.com/identity/sms-retriever/verify#1_construct_a_verification_message)

Your ExampleApp code is: 123ABC78


FA+9qCX9VSu

answered Dec 24 '19 at 07:14

soy

143
1
9

It would've been nice for them to tell exactly when the prefix requisite was removed. – andreszs May 14 '22 at 14:24

Google’s SMS retriever API is working fine without the <#> prefix. Why?

1 Answers1