Does WatchOS 7 have a limit on the total number of complications per app?

Question

Created Nov ’20

Replies 3

Boosts 0

Views 1.1k

Participants 2

Greetings,
Our WatchOS 7 app offers the user a complication for each of the items in the app. So if the app currently has only 5 items, we have 5 complications for each complication family type, if the user has 8 items we have 8 unique complications for each complication family and so on. This is incredibly useful, because we can now have multiple items on an active watch face.

We've noticed that if we have more than 10 items only the first 10 register in the getComplicationDescriptors() call. The rest are not visible to the user and as a result cannot be selected.

However, we've noticed that Apple's World Clock app, which shows the time for different cities has no limit. i.e. if the clock app has 18 cities in it, the user can pick from 18 complications for each complication family .

When will we be able to offer more than 10 complications?

Thank you

Boost

Answer 1

sal_from_new_york OP

Nov ’20

Any framework engineer want to chime in on this?

0

Answer 2

jphreynaud OP

Nov ’20

Sounds weird, I have no issue to get more than 10 complications descriptors that are all listed in the complication selection screen
When the number of descriptor is dynamic, you should ask the complication server to reload the descriptors as follow:

let complicationServer = CLKComplicationServer.sharedInstance()
complicationServer.reloadComplicationDescriptors()

0

Answer 3

sal_from_new_york OP

Mar ’21

Hi @jphreynaud,
just to be clear are you saying that per each complication type, you are seeing more than 10 of your complications? Mine stop at 10. The rest are not there.

let complicationServer = CLKComplicationServer.sharedInstance()
complicationServer.reloadComplicationDescriptors()

Been doing that every time my complications require changing.

0