2.20 beta: Strange NullPointerException

[corwin42]

I randomly get this NullpointerException since I use 2.20 Beta:

java.lang.NullPointerException
   at anywheresoftware.b4a.objects.Timer$TickTack.run(Timer.java:102)
   at android.os.Handler.handleCallback(Handler.java:615)
   at android.os.Handler.dispatchMessage(Handler.java:92)
   at android.os.Looper.loop(Looper.java:137)
   at android.app.ActivityThread.main(ActivityThread.java:4745)
   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)

I don't know if this is really related to the beta or if I have broken something in my code. Nevertheless I have no idea where this Exception occurs since in the call stack there is no name of a sub from my code.

 

[margret]

There is a new Beta download. It is still Beta 2.14 but it has some corrections. If you only have the first Beta, you may download the newest one and see if it helps.

 

[Erel]

It doesn't look like it is related to the new version.
Did you declare the timer as a process global variable? How do you initialize it?

 

[corwin42]

Yes, it is declared as process global variable. Timer is initialized to the next full hour. I will check my code again if I see anything strange.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2

 

[corwin42]

Hmm, changed some things now.

The Timers were NOT dimmed in process_globals but only in globals. Changed that now and another thing was that one timer was not disabled in activity_pause. Added this, too. Now I'm checking if it is better now.

Strange thing is that this seemed to work in B4A 2.02 but not in the current beta.