Begin the SMS with two consecutive zero-width space characters (U+200B) doesn't work about android-credentials HOT 9 CLOSED

@gabrieldelmas thanks for reporting this. Can you explain why you want to start the SMS with those characters? It would help me understand the issue better.

from android-credentials.

Thanks for taking the time to answer me. Basically, I don't want to start the SMS with "<#>" just because the SMS looks better without. The documentation seems let the choice between "<#>" or two consecutive zero-width space characters (U+200B) to begin the SMS.
https://developers.google.com/identity/sms-retriever/verify

from android-credentials.

@gabrieldelmas gotcha, I actually hadn't read that bit of the documentation before! Can you paste here the Java code you use to generate the SMS with the unicode characters?

from android-credentials.

No worries. Sure, here it is :
String body = "\u200b\u200b" + " " + message + "\n\n" + getAndroidAppHash();

If I replace "\u200b\u200b" by "<#>" everything works well.

from android-credentials.

@gabrieldelmas I've filed this with some backend engineers, will let you know what they have to say.

from android-credentials.

@samtstern Thanks

from android-credentials.

@gabrieldelmas apparently we've seen other reports like this. We suspect it's a carrier issue, some do not properly deliver the messages with the unicode prefix.

For max reliability I'd stick with the visible prefix. We're going to see what we can do to fix it or improve the docs.

from android-credentials.

@samtstern Could make sens. Fortunately, this issue happened on my phone otherwise it would have been harder to figure out from one of our feedback's user. I will stick with the visible prefix. Thanks.

from android-credentials.

Closing this for now as there's nothing we can do in this repo, but will come back if we have any more news.

from android-credentials.