IssueTracker

Thanks for your feedback. The members of the Android team responsible for managing and documenting permissions are looking into this issue.

Any time table on when this is going to be verified ? If this is truly bug in Android 8 then it is quite substantial.

According to this commit (not sure if it has entered the official Oreo rom) https://android.googlesource.com/platform/frameworks/opt/telephony/+/987378c0704f6000e8f99a36dd032c99f926b81a/src/java/android/telephony/SmsManager.java
(method: sendTextMessage, line 263) there is a call to getSubscriptionId(), which is protected with READ_PHONE_STATE_PERMISSION, then if the app does not have this permission checked/granted, calling this method will cause the SecurityException and the app will crash.

I'm quite sure it is out there. Replicated it on two pixel phones with Oreo.

This issue was reproduced at LG Nexus 5X with Android 8. After providing READ_PHONE_STATE_PERMISSION sendTextMessage() crushes ended. Also this issue reproduced in Android Oreo 8 emulator with same exception. We urgently deploy application update with this workaround, because the number of users with Ores is growing day by day.

Unfortunately we don't have the option to ask extra permission. Considering that this is not a small bug it is taking a long time for google team to investigate and respond. Perhaps there are some other channels we can use?

I have put this ticket in "documentation issues", perhaps these tickets are given a lot lower priority and we won't se any progress for quite some time.

Requiring extra permissions is confusing to users if nothing else. Personally, think this should be reverted to using a single permission rather than being documented.

Just to throw a curve ball here, I can replicate the crash on an LG Nexus 5X running Android 8 - BUT - only with certain contacts?

I have found a number of contacts that I can successfully call sendTextMessage() WITHOUT having to have request READ_PHONE_STATE from the user.

Which makes no sense given the suggestion that it is a global problem from comment #4

To confirm, I have triple checked - successful calls to sendTextMessage() (and confirmed delivery) immediately followed by using another contact and it will crash.

So will this just be ignored ? Should I repost in another channel (not related to documentation)

Silence from Google around this issue is indeed terrifying.

So i just tested this on (virtual) devices running 8.0.0 (OSR1.170720.005) and 8.1.0 (OPM1.171004.001).

Well, 8.1.0 no longer crashes while sending sms without READ_PHONE_STATE permission, so i guess problem is fixed there, but still remains in 8.0.0. Which is kinda painful considering we would most likely have to put checks for this specific version in code and handle the permission correctly. Or is there some patch fixing this in 8.0.0 that I don't know about?

Somebody please test this to confirm/deny my statement.

I love the complete silence from googles android team about this issue.
This bug forced me to redo some of logic in my app, as it seemed that there would be no fix for this in near future.

I am checking ContextCompat.checkSelfPermission(this, Manifest.permission.SEND_SMS) == PackageManager.PERMISSION_GRANTED
and i am still getting the error

java.lang.SecurityException:
  at android.os.Parcel.readException (Parcel.java:1942)
  at android.os.Parcel.readException (Parcel.java:1888)
  at com.android.internal.telephony.ISms$Stub$Proxy.sendTextForSubscriber (ISms.java:789)
  at android.telephony.SmsManager.sendTextMessageInternal (SmsManager.java:329)
  at android.telephony.SmsManager.sendTextMessage (SmsManager.java:312)

See the title of this bug for an explanation

Hi,

Anybody got an update on this issue?

I love that its been 2 months since reporting this issue. And still complete silence from google. I would like to know who has been assigned this issue, this is below any industry standards.

still getting more and more crashes have over 100,000 users

So half a year later and silence! It looks like this is assigned to someone.
Is there any other channel we can go thru?

So close to a full year, still having this bug... May it be because Oreos are vegan, and hence Google guys don't wanna "kill the bug"?

some solution to this bug still continues to occur in version 8.0

Fatal Exception: java.lang.SecurityException
       at android.os.Parcel.createException(Parcel.java:1950)
       at android.os.Parcel.readException(Parcel.java:1918)
       at android.os.Parcel.readException(Parcel.java:1868)
       at com.android.internal.telephony.ISms$Stub$Proxy.sendTextForSubscriber(ISms.java:871)
       at android.telephony.SmsManager.sendTextMessageInternal(SmsManager.java:358)
       at android.telephony.SmsManager.sendTextMessage(SmsManager.java:323)
       at com.otri.sosmap.MapsActivity.b(MapsActivity.java:23)
       at com.otri.sosmap.MapsActivity.access$600(MapsActivity.java)
       at com.otri.sosmap.MapsActivity.n(MapsActivity.java:193)
       at com.otri.sosmap.MapsActivity.access$600(MapsActivity.java)
       at com.otri.sosmap.MapsActivity$PhoneCallListener$1.run(MapsActivity.java:4)
       at android.os.Handler.handleCallback(Handler.java:873)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:193)
       at android.app.ActivityThread.main(ActivityThread.java:6863)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

I have given SEND_SMS and READ_PHONE_STATE both permissions.

Device
Brand: OnePlus
Model: ONEPLUS A3003

Operating System Version: 9

Crash Date: 23 Nov 2019, 23:10:00

صور

صور14

Thank you for your feedback.  We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here https://goo.gl/TbMiIO and reference this bug for context.