Are complications only received when the WatchFace derived View is active?

Looking to where I should put my Complications specific functions in my watch face. From logging statements put in the watch face code, I see that no complication is ever received when the watch is showing a glance/widget or an activity app. Are there situations where complications could be received by the watch face when the WatchFace View isn't showing? If no, then are there reason for NOT putting the complication in the WatchFace derived class instead of the appBase derived class. I'm trying to save space from the background space.

0 SylvainGa over 2 years ago in reply to jim_m_58

Jim, I'm not seeing this behavior. How do you close the watch face? Thanks.

0 jim_m_58 over 2 years ago in reply to SylvainGa

How are you publishing? In a background service? You need to do that for the watch face to update.

Use "kill app" in the sim to terminate the watch face so you can wait and run it later.

0 SylvainGa over 2 years ago in reply to jim_m_58

Ok, that's what I did. Except, when I activated the background process of the Glance app after I killed the watch face and then relaunched the watch face, there was no background process waiting to be read. That's what I gathered should have happened while reading your previous reply.

0 jim_m_58 over 2 years ago in reply to SylvainGa

The background process in your widget/glance. Not in your watch faces. The watch face doesn't need a background service to use complications.

It's been working fine for me for the last few months. In the sim as well as on a real device.

0 SylvainGa over 2 years ago in reply to jim_m_58

Yeah, that's what I meant. While the watch face was closed (quit), I initiated a TemporalEvent from the Glance app that was running in the background (through Simulation/Complication menu).

Ok thanks. At least I know that it should work and see if I can figure out what I'm doing different for it not working.