Unhandled exception in Timer initialization

beva 7 hours ago

Very rarely I get an unhandled exception when I set a timer.

I don't use timers for that reason, however I added a non essential timer for the review process that invokes the review process once after 20 minutes after initialization. I tried to search the forum for similar exceptions but didn't find any.

Error Name: Unhandled Exception
Occurrences: 1
First Occurrence: 2026-02-01
Last Occurrence: 2026-02-01
Devices:
fēnix® 8 Solar 47mm: 20.29
App Versions: 2.0 Sponsor 4.50
Languages: dut
Backtrace:
tixView.onLayout:102

101 var reviewTimer = new Timer.Timer();

102 reviewTimer.start(method(:checkReview), REQREVTIME, false);

Suggestions?

For now I'll put it in a try catch construction.

flocsy🤠 5 hours ago

1. catch the exception, then log the message, and let us know.

2. I never heard about this issue. The only timer related problem I encountered was when I already had 3 timers and tried to create a 4th one.

My guess is that it is more related to the fact that you're calling it from onLayout than to being a timer.

beva 5 hours ago in reply to flocsy🤠

I load it from onLayout as that is how it is showed in the sdk sample and documentation.

flocsy🤠 5 hours ago in reply to beva

I'm not saying it is wrong, certainly not according to the logic. But I did encounter strange things with onLayout in the past.

beva 2 hours ago in reply to flocsy🤠

Ah oke, what did you stumble into?

flocsy🤠 1 hour ago in reply to beva

In my case it was a datafield (which can't be your case because you use timer) and some functions that are supposed to work in onLayout only work in onUpdate. Also onLayout might be called not exactly when you expect, especially if you add more than one times the same field to an activity (it'll depend on many factors, i.e: the geometry of the different field positions you added them to (width, height, obscurity flags))

And if I remember correctly other developers also wrote strange things about onLayout.