Complete
over 4 years ago

When is it not ok to call WatchUi.requestUpdate();?

Hi,

This one is a new one on me!

I saw an ERA log from onSettingsChanged that crashed out on my DataField onSettingsChanged handerl:

    function onSettingsChanged() {
        if(view) {
            view.onSettingsChanged();
            WatchUi.requestUpdate(); // CRASHES HERE
        }
    }

There is nothing contentious that I can see in onSettingsChanged (except a slightly annoying Attention.playTone that I had decided to remove on account of it being annoying in any case) - just some maths that is null checked, valid and safe.

So:

1. Is there any time that it is either illegal or unwise to call WatchUi.requestUpdate()

2. How does one test for that?

Thanks,
G

Parents
  • [quote userid="117737" url="~/developer/connect-iq/f/discussion/246510/when-is-it-not-ok-to-call-watchui-requestupdate/1171891"]If you are (or were) seeing a crash from a call to WatchUi.requestUpdate() could you elaborate on the use case so that I can file a bug report? From my reading of the above the request is happening in onSettingsChanged() for a data field app. Is that sufficient to reproduce the problem?[/quote] I saw the report a few months ago also in my watch face code (only in era reports though, I didn't see the watch face actually crash)
Comment
  • [quote userid="117737" url="~/developer/connect-iq/f/discussion/246510/when-is-it-not-ok-to-call-watchui-requestupdate/1171891"]If you are (or were) seeing a crash from a call to WatchUi.requestUpdate() could you elaborate on the use case so that I can file a bug report? From my reading of the above the request is happening in onSettingsChanged() for a data field app. Is that sufficient to reproduce the problem?[/quote] I saw the report a few months ago also in my watch face code (only in era reports though, I didn't see the watch face actually crash)
Children
No Data