FCM delivery issues?

[John Sheehan]

Anyone else getting FCM delivery issues? I'm getting IDs back from the sendToTopic calls, but it seems a large number are not being delivered. Seeing reports from both Android and iOS users, but mostly iOS users (including me).

Submitted a ticket in case anyone can troubleshoot the specific message IDs I submitted (case #00144188)

[radwa ali]

Hi we have the same problem not all topic subscribers get notifications I noticed it in android as I am android developer  and recently direct notification  from firebase console without topic to target android not delivered too.  any way  can you please tell me how can you getting  reports  about ids because in our server side it only said sent successfully.  

[Kato Richardson]

Please check out Lifetime of a message and our guide on Understanding Delivery. The first and most important point to understand is that you shouldn't expect anything close to a 100% delivery rates. Here's a bit of copypasta on the topic. 

There are multiple reasons that can cause notifications to be delayed or undelivered. Here's an overview:

If FCM isn't returning any errors and there isn't an FCM outage posted on Status Dashboard, low delivery rates are usually caused by something going wrong on the client device:

• User's device is turned off, offline, or unable to connect to FCM.
  
• App crashes when it receives the notification. Crash reporting SDKs are the biggest help for detecting this.
  
• Some send requests encountered an error (e.g. invalid credentials, expired registration token, etc).
  
• For iOS we currently pass the notification off to APNs and whether the notification is delivered or not is determined by APNs.
  

In addition, FCM configuration can affect deliverability:

• The chosen priority and lifespan can affect whether or not your notification is shown, even if it is delivered to the device.
  
• Collapsible messages may be replaced by a new message if they have yet to be delivered to the device. Please learn more here.
  
• Topic conditions used in the message.
  

This blog post provide some more background.

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/119f13a5-4c54-48ec-8f7a-a655182be894n%40googlegroups.com.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398