java.lang.SecurityException

Neither user 10012 nor current process has android.permission.ACCESS_COARSE_LOCATION.

Samebug tips5

Android SDK 23 introduced a new way to handle permissions, so as a temporary workaround you can set it to build for SDK below 23. As a permanent solution you have to ask user during runtime for permissions with checkSelfPermission() or requestPermissions()

You need to request READ_PHONE_STATE permissions before using of this method.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web1256

  • Neither user 10012 nor current process has android.permission.ACCESS_COARSE_LOCATION.
  • via Android Enthusiasts by p.dario
    , 1 year ago
    Neither user 10012 nor current process has android.permission.ACCESS_COARSE_LOCATION.
  • Neither user 10012 nor current process has android.permission.ACCESS_COARSE_LOCATION.
  • Stack trace

    • java.lang.SecurityException: Neither user 10012 nor current process has android.permission.ACCESS_COARSE_LOCATION. at android.os.Parcel.readException(Parcel.java:1425) at android.os.Parcel.readException(Parcel.java:1379) at com.android.internal.telephony.ITelephony$Stub$Proxy.getCellLocation(ITelephony.java:1261) at android.telephony.TelephonyManager.getCellLocation(TelephonyManager.java:267) at ekv.a(SourceFile:53) at com.google.android.location.os.real.SdkSpecific8.a(SourceFile:62) at ekl.handleMessage(SourceFile:187) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:137) at eko.run(SourceFile:804) at java.lang.Thread.run(Thread.java:856)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    16 times, 5 months ago
    Unknown user
    Once, 1 year ago
    Once, 1 year ago
    669 times, 1 week ago
    86 times, 1 month ago
    232 more bugmates