-
-
Notifications
You must be signed in to change notification settings - Fork 134
LiveQuery Not working with PFUser #56
Comments
Having the same issue |
Same here! I think the above error applies to pointer-comparisons in general... |
I just decided to make another column with an array of strings of the objectId's for now, works great :) |
Good job, but still, the problem remains! Using objectIds isn't always possible.. Sometimes pointers are the only way to go... |
True, we need this fixed ! :( |
I opened this issue 1 month ago and no one from parse team didn't look and gave an answer. How we can fix it ? |
Can we get a bump on this? @richardjrossiii @nlutsenko |
See #59, i'm sure you can do something nearly identical to allow pfobject pointers. |
@kajensen , as in the decode functionality like that PR does for geo? |
Yeah just check if its a pfobject and create the dictionary with classname and id. Same thing can be done for nsdates. Not sure what would go into making subqueries and the more complex query parts work. |
@kajensen I'll look into that. So I theoretically could watch on the PFUser, but getting any relational data back for instance and working with that would prove to be more challenging? |
Yeah, the issue is encoding the non-primitive data types. @richardjrossiii mentioned that the goal was to use the iOS sdk for such things but this is a quick workaround for the time being. I'm not sure of the progress (if any) on that front, i'll defer to the main contributors for that. Encoding/decoding is the main issue with this library (from what I can tell). If people want to see this library useable (as do I), we're going to need to contribute and not just post "we want this fixed" or "how much longer til this gets fixed". As you can see its not super active nor ready for primetime. |
same issue |
@kajensen @AnChiChang have you checked at PR's #86 and #87 ? Doe they help? |
I had try this
or
get the same error message |
Sorry, my fault. After update my ParseLiveQuery to 2.0. The problem is solved. Thanks for helping. |
All good then! Let's close that one! |
hello @flovilmart I found a issue, can help ? |
Can you provide the logs or debugger dumps from the JSON responses? |
I am not sure which logs actually can help, just paste the dump information from xCode. If you need others, please let me know. Thanks.
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Invalid type in JSON write (PFObject)' |
I have saw someone can catch the JSON log, how to do that? |
run parse-server with VERBOSE=1 |
verbose: Request: {"sessionToken":"","op":"connect","applicationId":"6gyO0FRa7kb6PjT6b5fum7f09Z2M85St"}
|
Below will success subscribe:
Below will dump when subscribe:
|
So anyone struggling with this, my workaround has been:
Usage: Can be used in LiveQuery. |
Hi,
I'm trying to use live query with pfuser. As shown on code.But I'm getting this error when I use PFUser in query.
Error:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Invalid type in JSON write (PFUser)'
The text was updated successfully, but these errors were encountered: