Bug P2
Status Update
No update yet.
Comments
ta...@gmail.com
It looks like you are raising an issue as an Android user, rather than an Android Open Source Developer.
For user support, please see the
For Pixel phone support, please see the
Support for other devices is provided by the device manufacturers or by the carriers selling those devices,
na...@gmail.com
Comment has been deleted.
ma...@gmail.com
Is Issue Resolved?
pa...@gmail.com
Our app is crashing too. Simple try catch resolves the crash, but still SMS retriever stopped working on some devices with Android 13
sa...@eleve.co.in
Getting the same issue, any updated?
hw...@gmail.com
Getting the same issue here.
The deveice is Samsung GalaxyZ Fold4
The deveice is Samsung GalaxyZ Fold4
al...@gmail.com
Noted this issue as well on Samsung A03s when I updated to android 13.
ra...@gmail.com
Same issue on One Plus with Android 13
gi...@gmail.com
Same issue on all Android 13 devices
vf...@justeattakeaway.com
Same issue on Samsung A72 with Android 13 devices
ev...@poppy.be
Same issue on OnePlus 8T Android 13 (KB2003_11_F.62)
fi...@bnpparibas.pl
same
al...@gmail.com
Same here on Mi9 lite Android 13
mi...@gmail.com
I'm getting this error when trying to start SMS retriever, also on android 13, but I only notice this error on devices with Google Play Services 23.09.14 or higher.
Any PlayServices below that seems to work fine even on Android 13.
Any PlayServices below that seems to work fine even on Android 13.
ma...@gmail.com
Same issue on OnePlus 9
pt...@gmail.com
same here
ha...@gmail.com
same issue on zenfone 9
ra...@gmail.com
Please fix this, our apps are impacted due to this as well.
co...@gmail.com
We are also facing same issue. Oppo, One Plus with Android13 devices mostly.
na...@udhaar.co
Please provide fix for this issue.
po...@gmail.com
Am facing the same challenge,Kindly resolve the issue
in...@gmail.com
same issue
de...@gmail.com
I hope they resolve this fast
pr...@gmail.com
We are also facing the same issue. unable to auto read the OTP. We are using the auto read functionality of the SmsRetriever getting the exception as "Device doesn't support the messaging feature" in the startSmsRetriever => addOnFailureListener
si...@gmail.com
Facing the same issue, should we upgrade the API Level to 33 and authorize push notifications in AndroidManifest? The SmsRetriever is encountering an exception that says "Device doesn't support the messaging feature" when starting the startSmsRetriever process.
br...@gmail.com
Facing the same issue on our app, on android 13
is...@shadowfax.in
#26 we have target sdk as 33 & notif perm but still facing the same issue
is...@shadowfax.in
Similar issue which is assigned:
pr...@gmail.com
Even i am facing the issue in my oppo reno 8 5g
ra...@gmail.com
Here is a temp work around solution
al...@gmail.com
The above work around worked for me.
Thank you very much.
Thank you very much.
wi...@bnpparibas.pl
We are facing same issue on many devices.
Here is some list of devices:
CPH2197 - oppo
SM-A137F - samsung a13
RMX3241 -realme
CPH2195 - oppo
CPH2363 - oppo
SM-A528B - galaxy 52s
CPH2211 - oppo
RMX3472 - realm 9pro
M2012K11AG - xiaomi
SM-A325F - samsung galaxy a32
RMX3370 - realm GT Neo 2
We have like 100 crashes already by this problem and list of devices is much longer. All problems on Android 13
This problem should be fixed by Google. Above work around isn't something what we can accept and just tell to our customers as a standard fix..
Here is some list of devices:
CPH2197 - oppo
SM-A137F - samsung a13
RMX3241 -realme
CPH2195 - oppo
CPH2363 - oppo
SM-A528B - galaxy 52s
CPH2211 - oppo
RMX3472 - realm 9pro
M2012K11AG - xiaomi
SM-A325F - samsung galaxy a32
RMX3370 - realm GT Neo 2
We have like 100 crashes already by this problem and list of devices is much longer. All problems on Android 13
This problem should be fixed by Google. Above work around isn't something what we can accept and just tell to our customers as a standard fix..
va...@acintyo.com
I am also observing this issue in my app.
je...@x-guard.nl
Provided workaround does work (#31), confirming it is an bug with Google Play Services
uz...@gmail.com
Dear Google Kindly fix the sms otp is not working on google android 13 many banking apps not work due to OTP sms recieving but application not recognised the code due to messaging feature is not supported
as...@ergos.in
Even i am facing the issue in my oppo device in andoid 13.
is...@gmail.com
Solution Found.Don't listen for success or failure of task
Step1:
IntentFilter intentFilter = new IntentFilter(SmsRetriever.SMS_RETRIEVED_ACTION);
context.registerReceiver(smsVerificationReceiver, intentFilter);
Step 2:
SmsRetriever.getClient(context).startSmsUserConsent(null);
Note: Don't listen for success or failure of task.Just write above code and send sms you will get consent screen.
Step1:
IntentFilter intentFilter = new IntentFilter(SmsRetriever.SMS_RETRIEVED_ACTION);
context.registerReceiver(smsVerificationReceiver, intentFilter);
Step 2:
SmsRetriever.getClient(context).startSmsUserConsent(null);
Note: Don't listen for success or failure of task.Just write above code and send sms you will get consent screen.
vl...@gmail.com
this is not a solution, this is a possible workaround.
according to the reports it is clear that the problem is in the work on the 13th android, and not in the result listener
according to the reports it is clear that the problem is in the work on the 13th android, and not in the result listener
ka...@gmail.com
The solution doesn't address the concern since it means rearchitecting how already existing applications run affecting many users.
A permanent solution is for Google to resolve the issue ASAP.
A permanent solution is for Google to resolve the issue ASAP.
bh...@gmail.com
bh...@gmail.com
gk...@gmail.com
Ask chatgpt to translate below code for the solution
IntentFilter intentFilter = new IntentFilter(SmsRetriever.SMS_RETRIEVED_ACTION);
context.registerReceiver(smsVerificationReceiver, intentFilter);
Step 2:
SmsRetriever.getClient(context).startSmsUserConsent(null);
Note: Don't listen for success or failure of task.Just write above code and send sms you will get consent screen.
IntentFilter intentFilter = new IntentFilter(SmsRetriever.SMS_RETRIEVED_ACTION);
context.registerReceiver(smsVerificationReceiver, intentFilter);
Step 2:
SmsRetriever.getClient(context).startSmsUserConsent(null);
Note: Don't listen for success or failure of task.Just write above code and send sms you will get consent screen.
[Deleted User] <[Deleted User]>
Hello, I'm using sms retriever api and above work around isn't working for me i have made changes in SmsHelper.java file, mostly samsung and onePlus devices not working please give us proper guide to fix this issue. Thanks in-advance. My app is built on react native ("^0.64.2") and i'm using npm package react-native-sms-retriever ("^1.1.1").
gs...@gmail.com
Still an issue in 2025
Description
We are using the auto read functionality of the SmsRetriever that is creating this crash even on the older versions of the apps that are in the market currently.
This crash has started to spike now so request you to let us know the solution for this.
Similar issue was reported by someone as well but there is no solution provided for that.
Below is is the crash log. and the bug report is sent to the android-bugreport@google.com
Fatal Exception: com.google.android.gms.common.api.ApiException: 17: Device doesn't support the messaging feature
at com.google.android.gms.common.api.internal.TaskUtil.setResultOrApiException(TaskUtil.java:4)
at com.google.android.gms.common.api.internal.TaskUtil.setResultOrApiException(TaskUtil.java:1)
at com.google.android.gms.internal.auth-api-phone.zzz.zzb(zzz.java:1)
at com.google.android.gms.internal.auth-api-phone.zzi.zza(zzi.java:2)
at com.google.android.gms.internal.auth-api-phone.zzb.onTransact(zzb.java:3)
at android.os.Binder.execTransactInternal(Binder.java:1321)
at android.os.Binder.execTransact(Binder.java:1280)