When is CLKComplicationServer.sharedInstance().activeComplications nil?

Question

Reiss OP

Created Jul ’20

Replies 2

Boosts 0

Participants 3

Sometimes CLKComplicationServer.sharedInstance().activeComplications returns nil.
Documentation states:

This property contains an array of CLKComplication objects, each of which represents a version of your complication currently displayed on the clock face. This array typically has no entries or only one entry, but it may have multiple entries if your complication is installed in more than one slot on the clock face.

Under which circumstances can it be nil?

Boost

Answer 1

AndyJJ OP

Aug ’20

Obviously at least when your app has no complications on the watch face. Or did you mean something else?

0

Answer 2

jphreynaud OP

Sep ’20

The shared complication server CLKComplicationServer.sharedInstance() is always accessible.
It seems the .activeComplications is initialized only after WKExtensionDelegate.applicationDidFinishLaunching (or in parallel to ?)
So yes it can be nil if you try to use it before its initialization.

0