“SwiftData inheritance relationship”

Hello,I have a complication for my app correctly working and I'd like to tell my app, once it launched, which data it should show. Let's say I have a calendar application with the time travel feature and the user taps on a future event. What I would like to do here is when the user taps the complication to open, the id of the event is passed to the main app upon launching (via Handoff presumably like it's possible in Glance) so I can show the correct information to the user.I have read the documentation and I couldn't find a way to do this. The ComplicationController inherits from NSObject and so there is no way to do that via Handoff and the updateUserActivity method. Any idea how to solve this problem?Thanks a lot.

I'm trying to create a predicate with the below line, but it keeps telling me it's unable to parse the format string.var request = NSFetchRequest(entityName: Player) request.predicate = NSPredicate(format: ANY matches.bracket == %@, self)On Player's entity 'matches' is an optional to-many relationship to a Match entity. The Match entity has a to-one required attribute 'bracket' that points to a Bracket entity. I'm inside of the Bracket class with the above code, so thus the 'self' property.I want to get all Player entities where at least one of the matches pointed to belongs to the current bracket.What am I doing wrong here?

IOS 8.0+My app use UIWebview to visit a forum site. The forum front page contains two tag: default one is 'Recommend', another one is 'Newest'. Using ajax to load post data When user switch to 'Newest' tag, at the same time the page runs the follow codes to save state:window.history.pushState(null, title, url);After that if user is interesting with some post, he/she would click link and jump to a new page to view detail of the post. In this page, I use follow code to let user have a way to go back to 'Newest':history.back(-1);Now interesting thing happened, go back to 'Newest' tag but post data is very very old.After some tests, I found the data is always be the first time loaded after installed the app.This bug will not happen in Safari or Android app.I believe it should have some relationship with webView cache.But why UIWebview does't use newest cache? And how to solve this problem?

I have a couple of view controllers that can send email and was hoping to cleanup the code using a protocol extension. Something like this:protocol MailSender: class, MFMailComposeViewControllerDelegate { func composeMail(config: MFMailComposeViewController -> ()) func presentViewController(viewControllerToPresent: UIViewController, animated flag: Bool, completion: (() -> Void)?) func dismissViewControllerAnimated(flag: Bool, completion: (() -> Void)?) } extension MailSender { func composeMail(config: MFMailComposeViewController -> ()) { let mailer = MFMailComposeViewController() mailer.mailComposeDelegate = self config(mailer) presentViewController(mailer, animated: true, completion: .None) } // This method will never be called :( func mailComposeController(controller: MFMailComposeViewController, didFinishWithResult result: MFMailComposeResult, error: NSError?) { /* handle result */ dismissViewControllerAnimated(true, completion: .None) } }In use it looks like:class MyViewController: UIViewContr

protocol Person : Hashable { var fullname : String { get set } typealias R : Relationship var relationships : Array<R> { get } } protocol Relationship : Hashable { typealias P : Person var source : P { get } var target : P { get } }The above causes a compiler crash; surely it is a known issue? Is there a work-around? Is the above a coding-style that is to be avoided (in a language like Swift)?[Apple Swift version 2.0 (swiftlang-700.0.52.2 clang-700.0.65)Target: x86_64-apple-darwin14.4.0]

As of Xcode 7b6, generating NSManagedObject subclasses for Swift in Xcode for an entity with a to-many relationship will generate a property of the optional type NSSet?. From what I can tell the underlying NSManagedObject data will always contain an empty (or not empty) set for that key. Is there a good reason to keep relationships optional and having to deal with unwrapping the values every time?

Sometime in the past week or two, the Storyboard editor in Xcode 7 beta (then beta 5, now also still in beta 6) stopped recognizing the IBOutlets in _some_ (not all) of my UIViewController subclasses. (NOTE: my app is a pure Swift 2, iOS 9-targeting project.)Specifically, it cannot see the IBOutlets in VCs whose source files reside within my project's (app-specific) main folder, but it _can_ see them in (generic, non-app-specific) VCs that I keep in an Externals folder. What's more, if I move those app-specific VCs out of the main folder, the Storyboard editor sees their IBOutlets just fine:(I can't seem to post any screenshots here, so here's a diagram:)<Project Folder> IIAM.xcodeproj <-- Project Externals <-- Where I keep non-app-specific code and resources Classes Views <-- The Storyboard Editor sees the IBOutlets of all these files just fine IIAM <-- All app-specific code and resources Classes Views <-- The Storyboard Editor doesn't recognize any IBOutlets of these filesBut if I move