I am writing an application that also has the Today extension (or widget). Apple's recommended way to share code between extensions and containing applications is to put common code inside an inline structure that both the application and the extension can use. Therefore, as I understand it, I have to write general code and make the general code the target structure, and then the application and extension will declare the structure as a dependency. However, in practice, I have found that although the application recognizes the framework as just fine, the Today extension does not.
To be more specific: I put a simple table view in the controller inside my extension “My” (which I will call “Widget”) and as a tab in my application (which I will call “App”), and then a frame (I will call "Framework") with common code. The widget comes with TodayViewController, which contains a view of the table. This table view has a custom cell that I call CalendarCell. Therefore, the corresponding common classes / files:
- TodayViewController.h / m
- CalendarCell.xib
- CalendarCell.h / m
And then, of course, I have a storyboard for the widget and a storyboard of applications that are not shared.
So, in the phase of my target target phase of the application, I have Framework as the target dependency, and widgets as the target dependency (this was the case when I created the target, and deleting it did not seem to help). Similarly, in the build phase of the target widget, I use the Framework as the target dependency. The Framework lists TodayViewController.m and CalendarCell.m as compilation sources and CalendarCell.xib as a bundle resource.
, : Widget CalendarCell.m, TodayViewController.m CalendarCell.xib , . , TodayViewController.m , ( ). TodayViewController.m , / , ( , ). , - .
- , . Xcode 6/iOS 8? - ?