java.lang.SecurityException: Binder invocation to an incorrect interface in our app which only happens on 6.0 and 6.0.1 OS. The stack trace is pulled from a crash reporting service and could not be replicated locally on any of the Android 6 devices. The app uses a 'Service' which calls 'startForeground' and the stack trace seems to point to that method call. java.lang.SecurityException: Binder invocation to an incorrect interface

Stack Overflow | Ziad Halabi | 5 months ago
  1. 0

    java.lang.SecurityException: Binder invocation to an incorrect interface on Android 6

    Stack Overflow | 5 months ago | Ziad Halabi
    java.lang.SecurityException: Binder invocation to an incorrect interface in our app which only happens on 6.0 and 6.0.1 OS. The stack trace is pulled from a crash reporting service and could not be replicated locally on any of the Android 6 devices. The app uses a 'Service' which calls 'startForeground' and the stack trace seems to point to that method call. java.lang.SecurityException: Binder invocation to an incorrect interface
  2. 0
    Inside my mods folder I had another forge jar. Deleting is solved my problem.
  3. 0
    MANAGE_USERS has a protection level of signature|system, so your application must be signed with the platform key.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0
    You should add the permission android.permission.READ_EXTERNAL_STORAGE to your manifest file.
  6. 0

    Android In App Billing SecurityException "Binder invocation to an incorrect interface"

    Stack Overflow | 3 years ago | McFarlane
    java.lang.SecurityException: Binder invocation to an incorrect interface

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.SecurityException

      Binder invocation to an incorrect interface in our app which only happens on 6.0 and 6.0.1 OS. The stack trace is pulled from a crash reporting service and could not be replicated locally on any of the Android 6 devices. The app uses a 'Service' which calls 'startForeground' and the stack trace seems to point to that method call. java.lang.SecurityException: Binder invocation to an incorrect interface

      at android.os.Parcel.readException()
    2. Android Platform
      Service.startForeground
      1. android.os.Parcel.readException(Parcel.java:1620)
      2. android.os.Parcel.readException(Parcel.java:1573)
      3. android.app.ActivityManagerProxy.setServiceForeground(ActivityManagerNative.java:4487)
      4. android.app.Service.startForeground(Service.java:652)
      4 frames
    3. com.anghami.audio
      MusicService_$4.a
      1. com.anghami.audio.MusicService.J(MusicService.java:3517)
      2. com.anghami.audio.MusicService.b(MusicService.java:2676)
      3. com.anghami.audio.MusicService.F(MusicService.java:2647)
      4. com.anghami.audio.MusicService.a(MusicService.java:2421)
      5. com.anghami.audio.MusicService_.a(MusicService_.java:21)
      6. com.anghami.audio.MusicService_$4.a(MusicService_.java:214)
      6 frames
    4. AndroidAnnotations API
      a$a.run
      1. org.androidannotations.api.a$a.run(BackgroundExecutor.java:401)
      1 frame
    5. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)
      2. java.util.concurrent.FutureTask.run(FutureTask.java:237)
      3. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:154)
      4. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
      5. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
      6. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
      7. java.lang.Thread.run(Thread.java:818)
      7 frames