-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
PFQuery pointing to PFUser object failing to fetch data. #3325
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
Comments
@HackShitUp is this working when you point the SDK to Parse.com? |
When you check whether to append the object, shouldn't you be checking the object ids rather than using an object equality test? |
@natanrolnik yes it works with Parse.com |
@dstarke chiefly because I haven't enabled the local datastore and don't plan to |
My point was that |
@dstarke Hmmm why is that? And I've figured out how to fix this but it won't work for the version in the app store that points to Parse.com @natanrolnik. I want to fix this so that the transition occurs flawlessly; the next of my problems is actually figuring out how to save video files to the app... |
I don't think that PFUser or PFObject defines an isEqual() function, which means that |
@dstarke Alright I just tested this out, and it looks like the following syntax, before appending it to the array works:
Thanks @dstarke for the clarity! |
The below code fetches the user's object from Parse Class (soon to be MongoDB Collection) titled "Newsfeeds" where an object can hold a pointer to the PFUser class. The following code's query FETCHES the user's objects but cannot recognize the subscript syntax and in turn, DOES NOT append the user's object to the PFObject array:
`
// Query Current User's Friends
func queryFriends() {
}
`
The terminal outputs the user's object correctly being fetched, and even the terminal output is 100% fine. Why can't it recognize the subscript? I've also tried this with the .object(forKey: "") protocol and it won't work for the current app using Parse.com (I have not yet migrated it; testing it out before I replicate it with the actual data).
The text was updated successfully, but these errors were encountered: