parse-community / parse-community/parse-server
Push Notifications Stuck in 'Sent' Status with Parse Server (Postgres), Not Delivered to Devices
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
Issue Description
Push notifications sent from the Parse Dashboard remain stuck in the "sent" status and do not get delivered to devices. While using Postgres, the logs show the error:
Postgres doesn't support this query type yet ["e_NgpzQw8xiY8...(all the tokens I got)"].
Despite the curl test succeeding and getting a positive response from the push sending function in the code ({ success: true, message: "Notification sent to devices." }), the notifications do not show up on devices.
Switching to MongoDB is not an option because the server hardware does not support AVX instructions, resulting in an illegal instruction (signal=ILL) error.
Steps to reproduce
Set up a Parse Server with Postgres as the database.
Register a device and get the FCM token.
Try sending a push notification from the Parse Dashboard.
Observe that the notification status in the dashboard remains stuck on "sent" and does not deliver.
Actual Outcome
Parse Dashboard shows notifications stuck in the "sent" status.
Notifications do not appear on registered devices.
Logs include the error:
Postgres doesn't support this query type yet ["e_NgpzQw8xiY8...(all the tokens I got)"].
Expected Outcome
Notifications should be delivered to the registered devices.
Server
Parse Server version: 7.4.0
Parse Dashboard version: 6.0.0
Operating system: Debian GNU/Linux 12 (bookworm)
Local or remote host: Local server
Database
System: Postgres
Database version: 15.3
Local or remote host: Local
Client
SDK: JavaScript
SDK version: 9.6.1 (Firebase Messaging)
Logs
From the Parse Server logs:
Postgres doesn't support this query type yet ["e_NgpzQw8xiY8..."]
From the JavaScript console:
Push notification response: Object { success: true, message: "Notification sent to devices." }
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 Dashboard push flow with Parse Server 7.4.0, Postgres 15.3, and Firebase Messaging, then inspect the server logs around the reported unsupported Postgres query. Compare the successful push response with delivery and dashboard status, and confirm done when registered devices receive notifications and the status no longer remains stuck at "sent".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase, javascript, postgres
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100