Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-10081] Using identity key path is not reliable for core data predicates/expressions #52483

Open
swift-ci opened this issue Mar 11, 2019 · 2 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. standard library Area: Standard library umbrella

Comments

@swift-ci
Copy link
Collaborator

Previous ID SR-10081
Radar rdar://problem/48980810
Original Reporter sisoje (JIRA User)
Type Bug
Environment

XCode 10.2 beta 4, Swift 5, iPhone Xr simulator.

Additional Detail from JIRA
Votes 0
Component/s Standard Library
Labels Bug
Assignee None
Priority Medium

md5: f2e8ed7c7d98130934e4b2282b123693

Issue Description:

I made some snippets here:

https://gist.github.com/sisoje/a9226fc4c00613cc62648140480783ef

Crash occurs only when we use identity key path.

Expression using "expressionForEvaluatedObject" always works well.

I expected that identity key path works the same as "expressionForEvaluatedObject" but it isn't the case.

@belkadan
Copy link
Contributor

cc @jckarter. Is this a failure of key paths or CoreData?

@jckarter
Copy link
Member

I'm not sure. The identity key path ought to bridge over to the @"self" key path in Cocoa KVC. I'm not sure whether Core Data handles that.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. standard library Area: Standard library umbrella
Projects
None yet
Development

No branches or pull requests

3 participants