-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
fetchAllIfNeededInBackground() error might be a server-side issue #2391
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
Hey @acegreen any chance you can provide a list of repro steps? I know you covered some of this in the related issues, and in order to ensure this is a Parse Server issue it would be very useful to get a list of HTTP requests (e.g. using curl) alongside some sample data that can reliably reproduce the issue. Bonus points if you can identify the cause and provide a PR :D |
hey @hramos, I can certainly provide some more details to reproduce the issue. I'm not savvy enough to play around with the Parse Server repo yet. Though I recall looking into this a while ago but was able to find the root cause. The main idea resolves around an array that contains two or more different class Steps:
So in my case, I have my User class and I added a column called "recentSearches" which contains an array of & I was unable to find if the results appear as part of the initial request or if its the second time around.
|
Can you provide the logs please? |
Given the code in the iOS SDK (and my last comment) that makes sense it fails as the Don't pass arrays with mixed objects classNames to that method, and you should be good. |
Issue Description
Two related issue detailed here:
parse-community/Parse-SDK-iOS-OSX#986
parse-community/Parse-SDK-iOS-OSX#987
Steps to reproduce
described in issues
Expected Results
fetchAllIfNeeded should return objects because objects exist.
Actual Outcome
[Error]: Object not found. (Code: 101, Version: 1.14.1)
Environment Setup
Logs/Trace
Not sure if someone can make something of this
parse-server.info.2016-07-22.zip
The text was updated successfully, but these errors were encountered: