Skip to content

Cannot pass Parse pointers inside arrays to cloud functions #8861

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

Closed
4 tasks done
mstniy opened this issue Jan 2, 2024 · 3 comments
Closed
4 tasks done

Cannot pass Parse pointers inside arrays to cloud functions #8861

mstniy opened this issue Jan 2, 2024 · 3 comments
Labels
state:duplicate Duplicate of already reported issue type:feature New feature or improvement of existing feature

Comments

@mstniy
Copy link
Contributor

mstniy commented Jan 2, 2024

New Issue Checklist

Issue Description

Parse server rejects cloud function calls which include Parse pointers inside arrays

Steps to reproduce

Parse.Cloud.define("test", function () {});
// Later
await Parse.Cloud.run("test", {
  a:[{__type: "Pointer", className:"foo", objectId: "foo" }]
});

Actual Outcome

Parse server returns an internal server error

Expected Outcome

The cloud function should run

Environment

Server

  • Parse Server version: 6.4.0
  • Operating system: Ubuntu
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: 6.0.12
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local

Client

  • SDK (iOS, Android, JavaScript, PHP, Unity, etc): javascript
  • SDK version: 4.3.1

Logs

Copy link

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added the type:feature New feature or improvement of existing feature label Jan 2, 2024
@mtrezza
Copy link
Member

mtrezza commented Jan 2, 2024

Not sure whether this is supposed to be supported and documented anywhere; if it is then we can reclassify this as a bug.

@mstniy
Copy link
Contributor Author

mstniy commented Jan 18, 2024

Duplicate of #8783

@mstniy mstniy closed this as completed Jan 18, 2024
@mtrezza mtrezza added the state:duplicate Duplicate of already reported issue label Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:duplicate Duplicate of already reported issue type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants