How to handle connect event after a disconnect in a watch face?

In my watch face I need a temporal event scheduled at all times.

Currently I schedule the first event in `initialize`. The subsequent events are scheduled in my temporal event callback.

This works fine, but if the watch is disconnected from the phone, the temporal event callback is sometimes not called, so the watch face never schedules a temporal event again.

I don't know which methods called when the watch is connected again so I'm not sure where to schedule events again. As far as I can see the simulator cannot simulate disconnect/connect events so I can't test.

Anyone know which method (onLayout, onShow etc.) is called when the watch is connected to the phone after a disconnect?

0 jim_m_58 over 2 years ago

Nothing is called on a disconnect/connect. You can check phoneConnected or connectionAvailable in onUpdate (both in System.getDeviceSettings()).each time it's called. You may want to look at your onTemporalEvent and reschedule in all cases, even if you get an error in the callback for makeWebRequest, Or when you register, make it a duration and not a specific time, and you only need to register once

Background.registerForTemporalEvent(new Time.Duration(bgMins * 60));

0 9938694 over 2 years ago in reply to jim_m_58

Thanks. I will try to schedule a new event in onUpdate if an event is not already scheduled.

I forgot to mention, but I can't use a duration when registering as the next temporal events are not periodic, the next event time changes based on the data.

0 jim_m_58 over 2 years ago in reply to 9938694

I would then look in your service delegate and make sure you are always rescheduling one before you leave the background. Checking all the time in onUpdate is the worst option.

In the sim you can use Settings>Connection type to turn on and off BLE, Wifi or LTE..

0 9938694 over 2 years ago in reply to jim_m_58

What do you mean by leave the background? I can't really schedule a temporal event in my service delegate, I need to do it in background data handler, as the next event time depends on the data.

0 jim_m_58 over 2 years ago in reply to 9938694

The service delegate is you background code. To exit the background, you're probably doing Background.exit(), unless you just let 30 seconds pass and you time out.

If you're trying to do the scheduling in onBackgroundData(), that only runs when the main app is running.

0 9938694 over 2 years ago in reply to jim_m_58

jim_m_58 said:
If you're trying to do the scheduling in onBackgroundData(), that only runs when the main app is running.

This is indeed what I'm doing.

I'm a bit confused. I don't use `Background.exit` anywhere. Should I?

0 jim_m_58 over 2 years ago in reply to 9938694

Here's a whole thread about using a background, with a sample.

https://forums.garmin.com/developer/connect-iq/f/discussion/5287/very-simple-sample-of-a-watch-face-with-a-background-process

And here's a blog post with more details:

https://developer.garmin.com/connect-iq/connect-iq-faq/how-do-i-create-a-connect-iq-background-service/#howdoicreateaconnectiqbackgroundservice