URGENT: Inconsistent Push Notification Deliverability

Database & APIs

Is anyone else experiencing inconsistent push notification deliverability? Specifically, I have a chat app where, when a user hits the send button, it triggers a push notification to the recipient user. This is handled via the FlutterFlow push notification cloud function.

Up until recently, I had no issues, but I recently redeployed the function and since then notifications are inconsistently delivered. The recipient may receive a push notification 1 out of 5 times (sometimes more, sometimes less), but it's very inconsistent. Sometimes the num_sent value is 0, and the recipient doesn’t receive the push notification. Other times, num_sent is 1 or greater, and the recipient successfully receives the notification.

This inconsistency ONLY occurs when notifications are triggered through the app. When sending push notifications through the Firebase console directly, they are always delivered with num_sent = 1.

Note, this is all tested with the app in the background or in a closed state, I'm aware that FCM doesn't work in the foreground for FlutterFlow. Additionally, FCM tokens have been checked and are valid, so I don't believe that's the issue either.

Is anyone else encountering this issue, and are there any known solutions?

What have you tried so far?
  • Checked FCM tokens, which are generating correctly. Users receive notifications just inconsistently, maybe 1 in 5 or so.

  • Checked network connectivity and battery levels on recipient devices. I’m aware that iOS can prioritize deliverability based on certain device-specific settings, but I’ve ruled this out as a potential cause.

  • Deleted and redeployed the cloud function.

  • Sent messages directly from the Firebase console (works great).

  • Checked Google Console Logs, which come up clean, no errors.

It seems to me this is a bug related to how FlutterFlow interacts with the Google Cloud Function.

Did you check FlutterFlow's Documentation for this topic?
Yes
2
4 replies