-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Cloud function retuning array of PFObject, can not be cast in iOS (Swift) #112
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
cc @nlutsenko |
Sounds strange - any chance you can try to print out that array? It might be coming back as array of dictionaries instead of array of Parse Objects / Pointers - that's the only reason that comes to my mind. |
Self hosted parse-server |
Parse.com |
I haven't print them out, At least in XCode debugger, it was showing NSDirectory. I will confirm it if there is difference between them. |
I have the same problem, I think is because the result is missing "__type" and "className" |
I thin this can be related to parse JS lib, ParseObject.js have 2 methods:
and the express framework is using "toJSON" |
Yup - it needs the |
I'm trying to use a "json replacer" function to use _toFullJSON function, or to add the both properties, bu, no luck so far... Any recommendation? |
I am not hands on with nodejs (that was the reason, I started with Parse), Anyone has any idea or work around to continue my migration? At this point I have stuck. Thanks a lot. |
I opened a bug on the Parse-SDK-JS, I think the problem is there. |
I know how to solve this when I return this: But no if I return something like this: any idea? |
I did solve it... |
German: Thanks a lot. I just tested out and it works like a charm. Do you know when is it going to be in master branch? |
Just merged it, already on master ;) |
Making ParseInstallation subclassable
I am returning PFObjects from cloud function(s) and in my app (iOS SDK), I am using Subclassing. However, it gives error:
fatal error: NSArray element failed to match the Swift Array Element type
It works fine with api.parse.com but not with my local parse-server. Thanks
The text was updated successfully, but these errors were encountered: