Invalid value on View.findDrawableById in onLayout

You need to post some code.  Is it actually the findDrawableById() call, or maybe the line after when you try to set the value?  With "windDirection", as you sure you have a valid value?

Thanks for your help! :)

The funny thing is my Fenix 5 never shows this problem. Also over 95% of the users don't get the error.

if you fill a non-existing id the function will return null.

A snippet of the code below, nothing wrong as far as I can spot, otherwise it would have thrown an exception. I'm very puzzled... :S

class SurfWatchFaceView extends WatchUi.WatchFace {
    .
    .
    .
    private var textScroller;

    // Load your resources here
    function onLayout(dc) {
        setLayout(Rez.Layouts.WatchFace(dc));
        
	.
	.
	.
   	textScroller = View.findDrawableById("TextScroller");
    }

    .
    .
    .

    // Update the view
    function onUpdate(dc) {
	.
	.
	.
        setUpdatedTimestamp(Application.getApp().getProperty(SurfWatchFaceApp.STORE_KEY_TIMESTAMP_UPDATED));
        
        // Call the parent onUpdate function to redraw the layout
        View.onUpdate(dc);
    }

    .
    .
    .

    private function setUpdatedTimestamp(timestampNumber) {	
    	textScroller.setUpdatedTimestamp(timestampNumber);
    }

    .
    .
    .
}

class TextScroller extends WatchUi.Drawable {
    .
    .
    .
    public function setUpdatedTimestamp(updatedTimestampNumber) {
    	if (updatedTimestampNumber != null && (updatedTimestampNumber instanceof Lang.Number || updatedTimestampNumber instanceof Lang.Long)) {
       		var dataTs = Gregorian.info(new Time.Moment(updatedTimestampNumber), Time.FORMAT_MEDIUM);
       		self.updatedTimeString = Lang.format("$1$ $2$ $3$ $4$:$5$:$6$", [dataTs.day, dataTs.month, dataTs.year, dataTs.hour.format("%02d"), dataTs.min.format("%02d"), dataTs.sec.format("%02d")]);
       	} else {
       		self.updatedTimeString = "";
       	}
    }
    .
    .
}

Consider things like what happens if your getProperty() call returns a null, as can happen with the objectStore.

Thanks again for your reply!

hmm yeah... I have already built-in protection for that. There is a null check in the setUpdatedTimestamp function. Also, the function checks if the input is of the type Number and Long.

I also see that the Backtrace doesn't make sense.

The onLayout doesn't call the setUpdateTimeoutTimestamp function in any way.

SurfWatchFaceView.onLayout:54 is actually calling this:

windDirectionLabel = View.findDrawableById("windDirection");

Totally non-related to setUpdatedTimestamp.

Further, I have noticed that Time.Moment can accept a string or a null in the constructor. No error or exception will occur. Moment.value() will just return whatever is given.

However, I do see that Gregorian.info can give "invalid Value" error instead of an exception.

But it should never happen, the function is protected with checks. Also, the backtrace doesn't lead to inside the setUpdatedTimestamp function.

Well... I think I have solved it. But the problem moved to another spot.

I have solved it by changing the input value from Long to Number. Which was not a problem in 98% of cases/devices. Only on a few devices and maybe not even always.

But the invalid value occurs on a different spot now where I simply set a string. This particular code never had a problem before, the code never changed in this particular spot.

Garmin really blows my mind...