-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Invalid key name: $relatedTo with Parse.Query.and #4785
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
Can you try with:
Also please provide the server logs when running with VERBOSE=1 |
Hey @flovilmart, These are the verbose logs, before trying your approach: Your workaround worked nice so far, I'll keep testing and if I encounter another case parse fails, I'll post it here. I really appreciate your help, Thanks! |
Actually the workaround is the original way of doing it. The and operator has been added lately and as you noticed, may be problematic. I’ll fix the issue in a shot future. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can we re-open this issue? It seems to still exist in the current version of parse-server. I'm not sure how to apply the workaround above to my situation - I definitely need AND, not OR. EDIT: I figured out how to use the above workaround, thanks! I think this is still an issue and should be fixed within the SDK though. |
Uh oh!
There was an error while loading. Please reload this page.
Issue Description
Parse server is rejecting
Parse.Query.and
queries in conjution with relations,Parse.Query.or
is working correctly.my usecase is sending a push notification with complex query. therefore I need the
Parse.Query.and
Steps to reproduce
Not working:

Working:
Expected Results
$relatedTo
to be supported.Actual Outcome
an exception.
Environment Setup
Server
Database
The text was updated successfully, but these errors were encountered: