parse-community / parse-community/parse-server
IOS Live query is not working with parse v6
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
Parse live query is not receiving updates when I have updated the parse server to version 6.0. It works fine with version 5 but as soon as we switch to version 6, it stops working. Also, version 6 works fine with Android but not working with IOS.
Steps to reproduce
Actual Outcome
Expected Outcome
Environment
Server
- Parse Server version: 6.0.0
- Operating system: AWS Linux server
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): AWS
Database
- System (MongoDB or Postgres): MongoDB
- Database version: MongoDB atlas latest
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): MongoDB Atlas
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc): iOS
- SDK version: 2.8.1
https://github.com/parse-community/ParseLiveQuery-iOS-OSX
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Parse Server 6.0.0 versus 5 behavior with the ParseLiveQuery iOS SDK 2.8.1, using the AWS and MongoDB Atlas environment described. Compare iOS live-query updates with the working Android behavior and collect the missing reproduction steps and logs. Done means iOS receives the expected live-query updates on Parse Server 6.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, javascript, mongodb
- Domain
- backend, databases, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100