[AC-1951] App crashes unexpectedly
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | n/a |
Status | Closed |
Resolution | Needs more info |
Resolution Date | 2013-07-08T19:36:35.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | n/a |
Labels | n/a |
Reporter | Nedim Cholich |
Assignee | Shak Hossain |
Created | 2013-07-06T11:14:39.000+0000 |
Updated | 2016-03-08T07:40:53.000+0000 |
Description
I've sent the crash report to google and this is what my phone reported:
java.lang.NullPointerException
at ti.modules.titanium.ui.widget.TiUIDialog.processProperties(TiUIDialog.java:80)
at org.appcelerator.kroll.KrollProxy.setModelListener(KrollProxy.java:1126)
at org.appcelerator.titanium.proxy.TiViewProxy.realizeViews(TiViewProxy.java:469)
at org.appcelerator.titanium.proxy.TiViewProxy.handleGetView(TiViewProxy.java:460)
at org.appcelerator.titanium.proxy.TiViewProxy.getOrCreateView(TiViewProxy.java:438)
at ti.modules.titanium.ui.AlertDialogProxy$1.run(AlertDialogProxy.java:72)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4575)
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:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
at dalvik.system.NativeStart.main(Native Method)
Hello Nedim, Would you mind providing a simple test case that demonstrates this crash? We need a simple piece of code that can be pasted into and app.js, no longer than 50-100 lines, that demonstrates the behavior you are experiencing. This way we are both up to speed on the code in question here and once we can reproduce the bug we will know if it is a problem on our end or not and I can then report it to the engineering team. Thank you, Carter
We have not heard back from you since you posted the issue. Not sure if this is still getting this crash in your app. If so, please send us a test case so that we can take next necessary step to fix. If we don't hear back, we will assume the issue is no longer valid and close it.