Skip to content
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

Live Query's Event.updated fails to send the correct fields of an object after the first update #1667

Open
4 tasks done
atonylai opened this issue Oct 5, 2022 · 1 comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@atonylai
Copy link

atonylai commented Oct 5, 2022

Issue Description

Parse Live query returns the object with the correct fields for Event.updated on the first change but fails to update any subsequent changes.

Steps to reproduce

  1. Set up a parse live query with Event.updated
  2. Update the object, whether through another device or the database manually
  3. print the object in the Event.updated handler
  4. note that the object has had the field updated
  5. Change any field on the object again
  6. note that the object sent down has the same properties as in step 4, ignoring the changes in step 5.

Having an object get updated by a different source works (such as using two phones to update the same object) as long as the source of the update is different each time

Actual Outcome

Fields should be updated on subsequent updates

Expected Outcome

Fields were not updated on subsequent updates

Environment

Back4app, Parse Server version

Client

  • Parse ObjC SDK version: 1.19.3

Server

  • Parse Server version: 4.5.0
  • Operating system: iOS 16.0
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Back4App

Database

  • System (MongoDB or Postgres): Mongo DB
  • Database version: 3.6
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Back4App

Logs

@parse-github-assistant
Copy link

parse-github-assistant bot commented Oct 5, 2022

Thanks for opening this issue!

  • ❌ Please edit your post and use the provided template when creating a new issue. This helps everyone to understand your post better and asks for essential information to quicker review the issue.

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Oct 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

2 participants