java.lang.RuntimeException

Unable to start activity ComponentInfo{com.appc.navgroup/com.appc.navgroup.NavgroupActivity}: java.lang.NullPointerException

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web39030

  • via Appcelerator JIRA by Tony Lukasavage, 1 year ago
    Unable to start activity ComponentInfo{com.appc.navgroup/com.appc.navgroup.NavgroupActivity}: java.lang.NullPointerException
  • via Appcelerator JIRA by Tony Lukasavage, 1 year ago
    Unable to start activity ComponentInfo{com.appc.navgroup/com.appc.navgroup.NavgroupActivity}: java.lang.NullPointerException
  • Unable to start activity ComponentInfo{Activity}: java.lang.NullPointerException
  • Stack trace

    • java.lang.RuntimeException: Unable to start activity ComponentInfo{com.appc.navgroup/com.appc.navgroup.NavgroupActivity}: java.lang.NullPointerException at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1956) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1981) at android.app.ActivityThread.access$600(ActivityThread.java:123) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1147) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:4424) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.NullPointerException at com.google.android.maps.ItemizedOverlay.populate(ItemizedOverlay.java:311) at ti.modules.titanium.map.TiMapView$TitaniumOverlay.setAnnotations(TiMapView.java:186) at ti.modules.titanium.map.TiMapView.doSetAnnotations(TiMapView.java:783) at ti.modules.titanium.map.TiMapView.processProperties(TiMapView.java:657) at org.appcelerator.kroll.KrollProxy.setModelListener(KrollProxy.java:893) at org.appcelerator.titanium.proxy.TiViewProxy.realizeViews(TiViewProxy.java:442) at org.appcelerator.titanium.proxy.TiViewProxy.handleGetView(TiViewProxy.java:434) at org.appcelerator.titanium.proxy.TiViewProxy.getOrCreateView(TiViewProxy.java:412) at org.appcelerator.titanium.proxy.TiViewProxy.realizeViews(TiViewProxy.java:449) at org.appcelerator.titanium.proxy.TiViewProxy.handleGetView(TiViewProxy.java:434) at org.appcelerator.titanium.proxy.TiViewProxy.getOrCreateView(TiViewProxy.java:412) at org.appcelerator.titanium.proxy.TiViewProxy.handleAdd(TiViewProxy.java:528) at org.appcelerator.titanium.proxy.TiViewProxy.handleMessage(TiViewProxy.java:205) at android.os.Handler.dispatchMessage(Handler.java:95) at org.appcelerator.kroll.common.TiMessenger.dispatchMessage(TiMessenger.java:365) at org.appcelerator.kroll.common.TiMessenger.dispatchPendingMessages(TiMessenger.java:350) at org.appcelerator.kroll.common.TiMessenger$2.getResult(TiMessenger.java:235) at org.appcelerator.kroll.common.TiMessenger.sendBlockingMessage(TiMessenger.java:262) at org.appcelerator.kroll.common.TiMessenger.sendBlockingRuntimeMessage(TiMessenger.java:187) at org.appcelerator.kroll.KrollProxy.fireSyncEvent(KrollProxy.java:612) at org.appcelerator.titanium.TiBaseActivity.onCreate(TiBaseActivity.java:437) at org.appcelerator.titanium.TiLaunchActivity.onCreate(TiLaunchActivity.java:162) at org.appcelerator.titanium.TiRootActivity.onCreate(TiRootActivity.java:99) at android.app.Activity.performCreate(Activity.java:4465) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1920) ... 11 more

    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

    You’re the first here who have seen this exception.