SecurityException: Requires READ_PHONE_STATE

[jbaginski]

Required Information

• Mode (Mock/Sandbox/Live): Live
• PayPal Android SDK Version: 2.14.2
• Android Version and Device (Motorola Droid Razr Maxx with Android 4.4.2, Samsung S7 with Android 6.0, etc...): Samsung devices (SM-A5000, SM-N900916, SM-A700YD14) and Meizu MX4
• PayPal-Debug-ID(s) (from any logs): n/a

Issue Description

we have some crash reports from multiple Samsung devices running Lollipop (5.0, 5.0.2, 5.1)

Fatal Exception: java.lang.SecurityException: Requires READ_PHONE_STATE: Neither user 10323 nor current process has android.permission.READ_PHONE_STATE.
       at android.os.Parcel.readException(Parcel.java:1540)
       at android.os.Parcel.readException(Parcel.java:1493)
       at com.android.internal.telephony.ITelephony$Stub$Proxy.getCellLocation(ITelephony.java:2644)
       at android.telephony.TelephonyManager.getCellLocation(TelephonyManager.java:735)
       at com.paypal.android.sdk.at.l(Unknown Source)
       at com.paypal.android.sdk.at.c(Unknown Source)
       at com.paypal.android.sdk.fr.b(Unknown Source)
       at com.paypal.android.sdk.cs.run(Unknown Source)

it may be related to #205

[sankarbhavanib]

@jbaginski I am looking into this issue will update you soon

[braebot]

We've found the issue and will submit a new release as soon as we can. Thanks for raising the issue to us!

[jbaginski]

great news! do you have any ETA for the next release?

[braebot]

We'll get a release out next week.

[WongWeiLoon]

Can I know when we would get the new release because we are urgent to push out our Android update. Thanks in advance. 👍

[garfieldmypet]

Hi, @braebot ,

Can I know if the bug had already been fixed, because we are facing the same issue as well. Is the new release out yet and where can we download the Android MPL new release?

[garfieldmypet]

@sankarbhavanib , do we have any update on this issue as we are still facing the same problem in Android Marshmallow and above.

I am hoping that either @braebot or @sankarbhavanib can at least reply to this issue as our app cannot be deployed without a fix and there seems to be no workaround provided as well.

[braebot]

Fixed in 2.14.5.

[jbaginski]

thanks :)