You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems to be a bug because I did not find any breaking changes documented regarding aggregate.
Parse Server 3.1.0 made the jump from Parse JS SDK 2.0.2 to 2.1.0, so maybe it is a bug in the JS SDK.
Note: I am not using the Parse JS SDK as a client, it is only used through cloud code.
Any ideas?
I posted this on SO before, but it looks like a bug, so posting here.
The text was updated successfully, but these errors were encountered:
To rule out possibly conflicting parse-server / parse JS SDK versions, I deleted parse dependency from parse-server-example and deployed on heroku with node_module_cache=false.
npm list shows parse@2.1.0 installed under parse-server@3.1.3.
Still getting the error.
It would be great if anyone could try to reproduce this with a simple aggregate query in cloud code.
So it's not a bug, it was a Parse Server vs. Parse JS SDJ mismatch.
I had two parse servers running on the same DB for testing during migration. Turns out that some URLs in the v3.x server still pointed to the other v2.8.4 server. After correcting the URLs all works fine.
After upgrading from Parse Server 3.0.0 to a version >3.0.0 and <=3.1.3 (latest) the aggregate query in cloud code does not work anymore.
The query:
fails with error:
I also tried the pipeline object as array which also fails:
Such an error can be thrown at:
Seems to be a bug because I did not find any breaking changes documented regarding
aggregate
.Parse Server 3.1.0 made the jump from Parse JS SDK 2.0.2 to 2.1.0, so maybe it is a bug in the JS SDK.
Note: I am not using the Parse JS SDK as a client, it is only used through cloud code.
Any ideas?
I posted this on SO before, but it looks like a bug, so posting here.
The text was updated successfully, but these errors were encountered: