SMS Retriever API auto fetch issue

**Issue by [AtifAbbAsi19](https://github.com/AtifAbbAsi19)**
_Monday Mar 18, 2019 at 11:37 GMT_
_Originally opened as https://github.com/googlesamples/android-credentials/issues/36_

----

[SMS Verification with SMS Retriever API auto fetch issue](https://stackoverflow.com/questions/55216363/sms-verification-with-sms-retriever-api-auto-fetch-issue)

I'm trying to use Google's SMS Retriever API for Automatic SMS Verification, but there is an issue in it. previously , I was reading sender number using getOriginatingAddress() and if it's valid sender number then read OTP otherwise it should not read msg. As , forwarded OTP is disturbing user's privacy.

I have the following scenario.

My app is auto-fetching forwarded OTP messages.

User A installs app on his mobile and enters User B mobile number.
User B receives OTP and forwards it to User A.
App reads OTP on User A mobile and goes to home screen.
is there any way around to get sender number?

No repository file or test is identified. Start by reviewing the SMS Retriever API behavior and the use of getOriginatingAddress() described in the issue, then determine whether forwarded OTP messages can be distinguished from messages sent by the intended sender. Done would require a documented, reproducible resolution for the reported privacy concern.

Written by the indexing model from the issue text.