如何连接和调试定制ClockKit Complications控制器？(How to connect and debug a custom ClockKit Complications controller?)

 我想要一个定制的ClockKit Complication工作。 
 
 
 
 我创建了一个符合CLKComplicationDataSource的自定义ComplicationController 。 它作为CLKComplicationPrincipalClass添加到Watch Extension的plist中。 
 
 
 我可以在手表上选择复杂功能并激活它，但我只看到“---------------”不是我的实际占位符。 
 
 我试过的 
 
 
 
 我为我的ComplicationController添加了自定义override init(){…}并在其中放置了一个断点用于调试。 但即使运行Complication 构建方案，也不会达到这个中断点。 看起来像我的自定义ComplicationController从未实例化。 
 
 
 我看到日志消息Extension received request to wake up for complication support. 但在代码中触发的位置并不清楚。 
 
 
 我也尝试从我的主要InterfaceController调用以下内容来了解​​我的主动并发症 
if let server = CLKComplicationServer.sharedInstance() {
    for complication in server.activeComplications {
        server.reloadTimelineForComplication(complication)
    }
}
 ...但server返回零。 没有任何并发​​症似乎是积极和重新加载。 
 
 
 题 
 
 
 
 我如何成功连接我的自定义ComplicationController？ 
 也欢迎任何其他调试技巧。 
 它通常足以从手表模拟器或iPhone上的手表应用程序中消除复杂情况，或者是否需要重新安装整个手表应用程序以查看有效的并发症相关更新？ 另外，当我在自定义ComplicationController中记录一些内容时，我应该只在使用Complications构建方案运行时看到它的输出，还是应该使用正常的Watch App构建方案？ 
 
 
 任何想法找到这个问题是受欢迎的。 

I am trying get a custom ClockKit Complication working. 
 
 
 
I created a custom ComplicationController conforming to CLKComplicationDataSource. It’s added to the Watch Extension’s plist as CLKComplicationPrincipalClass.
 
 
I am able to select a complication on the watch and activate it but I only see "---------------" not my actual placeholder.
 
What I tried
 
 
 
I added custom override init(){…} to my ComplicationController and put a break point in it for debugging. But even when running the Complication build scheme this break point is never reached. It seems like my custom ComplicationController is never instantiated.
 
 
I do see a log message Extension received request to wake up for complication support. but it’s not clear to me where this is triggered in the code.
 
 
I also tried calling the following from my main InterfaceController to find out about my active complications
 
if let server = CLKComplicationServer.sharedInstance() {
    for complication in server.activeComplications {
        server.reloadTimelineForComplication(complication)
    }
}
 
… but server returns nil. No complications appear to be active and reloaded.
 
 
Question
 
 
 
How do I successfully hook up my custom ComplicationController? 
 
Also any additional tips for debugging are welcome. 
 
Is it usually enough to remove the complications from the watch simulator or the watch app on the iPhone or do you need to re-install the whole watch app to see a complication related update in effect? Also, when I log something inside my custom ComplicationController, should I only see its output when running with the Complications build scheme or also with the normal Watch App build scheme?
 
 
Any ideas for finding the issue are welcome.

原文：https://stackoverflow.com/questions/34536561