Restricting Complication Families

Sometimes, a particular complication family just doesn’t make sense for your data. A complication to show a random inspirational quote probably wouldn’t make sense in the Modular Small family. To that end, you can tell watchOS which complication families you support, so that it won’t offer your complication to the user on the wrong watch face. In Xcode, open your project settings; then select the NomNomNom WatchKit Extension target. Under the Info tab, there are two key/value pairs of interest. The first, CLKComplicationPrincipalClass, tells watchOS which class it should instantiate to create complication data. In this case, you can leave it at its default value of $(PRODUCT_MODULE_NAME).ComplicationController, which maps to your ComplicationController class.

The second interesting key/value pair is CLKComplicationSupportedFamilies. The value for this key is an array of strings, each representing a supported family. Delete CLKComplicationFamilyModularSmall, CLKComplicationFamilyUtilitarianSmall, and CLKComplicationFamilyCircularSmall to match what you’ve implemented in the app.

In general, it’s good practice to implement as many complication families as you can, but there are certain situations where you may not be able to implement all of them. If that happens, don’t sweat it—just edit the project info to hide those families you can’t implement.