java.lang.RuntimeException

Failure delivering result ResultInfo{who=null, request=1601, result=-1, data=Intent { VirtualScreenParam=Params{mDisplayId=-1, null, mFlags=0x00000000)}(has extras) }} to activity {com.example.jamessingleton.chffrapi/com.example.jamessingleton.chffrapi.MainActivity}: java.lang.IllegalArgumentException: account is null

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web6

  • via GitHub by cooliean
    ,
  • Stack trace

    • java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=1601, result=-1, data=Intent { VirtualScreenParam=Params{mDisplayId=-1, null, mFlags=0x00000000)}(has extras) }} to activity {com.example.jamessingleton.chffrapi/com.example.jamessingleton.chffrapi.MainActivity}: java.lang.IllegalArgumentException: account is null at android.app.ActivityThread.deliverResults(ActivityThread.java:4920) at android.app.ActivityThread.handleSendResult(ActivityThread.java:4963) at android.app.ActivityThread.access$1600(ActivityThread.java:221) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1848) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:158) at android.app.ActivityThread.main(ActivityThread.java:7224) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120) Caused by: java.lang.IllegalArgumentException: account is null at android.accounts.AccountManager.getAuthToken(AccountManager.java:1267) at com.example.jamessingleton.chffrapi.MainActivity.requestToken(MainActivity.java:152) at com.example.jamessingleton.chffrapi.MainActivity.onActivityResult(MainActivity.java:181) at android.app.Activity.dispatchActivityResult(Activity.java:7137) at android.app.ActivityThread.deliverResults(ActivityThread.java:4916)

    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

    We couldn't find other users who have seen this exception.