Why did my Android push open statistics suddenly drop to zero or become very low?

A sudden and significant drop in push notification open rates for your Android application, especially after an app update, typically indicates that our SDK is no longer being notified when a user opens a push. This prevents the 'open' event from being recorded in your statistics.

The most common cause is that the /pushStat method, which is responsible for tracking push opens, is not being called correctly.

How to Diagnose and Fix the Issue

1. Check Application Logs: The first step is to get device logs from your app while you send it a test push and then open that push. You should see a /messageDeliveryEvent call in the logs, which confirms the device received the notification.

2. Look for the /pushStat Call: When you open the notification, you should see a /pushStat call in the logs immediately after. If you see /messageDeliveryEvent but /pushStat is missing, it confirms that the open tracking is broken.

3. Review Your Code: The issue is likely within the part of your application's code that handles user interaction with notifications. This is often in a service that extends FirebaseMessagingService or a custom BroadcastReceiver.

4. Verify the Implementation: Ensure that the /pushStat method is explicitly called whenever a notification is opened by the user. Review any recent code changes, particularly those related to deeplink handling or custom notification layouts, as these modifications may have inadvertently removed or altered the logic that triggers the /pushStat call.