java.lang.RuntimeException

Unable to start activity ComponentInfo{myApp.mainActivity/myApp.mainActivity.mainLayout}: android.content.res.Resources$NotFoundException: Unable to find resource ID #0xffffffff

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 web10

  • via Stack Overflow by morg
    ,
  • via Stack Overflow by Bohsen
    ,
  • Stack trace

    • java.lang.RuntimeException: Unable to start activity ComponentInfo{myApp.mainActivity/myApp.mainActivity.mainLayout}: android.content.res.Resources$NotFoundException: Unable to find resource ID #0xffffffff at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3254) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3350) at android.app.ActivityThread.access$1100(ActivityThread.java:222) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1795) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:158) at android.app.ActivityThread.main(ActivityThread.java:7229) 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: android.content.res.Resources$NotFoundException: Unable to find resource ID #0xffffffff at android.content.res.Resources.getResourceEntryName(Resources.java:3738) at android.support.v7.widget.ResourcesWrapper.getResourceEntryName(ResourcesWrapper.java:264) at myApp.mainActivity.doStuff(mainActivity.java:341) at myApp.mainActivity.onCreate(mainActivity.java:71) at android.app.Activity.performCreate(Activity.java:6876) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1135) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3207)

    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.