Skip to content

Push Notifications Stuck in 'Sent' Status with Parse Server (Postgres), Not Delivered to Devices #9507

Open
@AnahitaHonarmandian

Description

@AnahitaHonarmandian

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." }

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:bugImpaired feature or lacking behavior that is likely assumed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions