Incorrectly marking devices as inactive about fcm-django HOT 6 OPEN

It's like you desribed - devices not receiving notifications are marked as inactive. So if a notification cannot be sent to a device, it's marked as inactive. There's no network checks and if the user is using the app and so forth. May I ask why they are not receiving notifications?

from fcm-django.

Some of the devices that were marked as inactive are being actively used for testing the application. These devices were online and had the application open in front of me when I attempted to push notifications. Despite this, these devices were marked as inactive after the notification push attempt.

Here are the specific observations:

1. Active and Online Devices: The devices were connected to the network and actively running the application.
2. Notification Push: I attempted to push notifications to all devices listed in the FCMDevice model.
3. Mixed Results: Out of all devices, only one device successfully received the notification and was not marked as inactive. The rest, despite being active and online, did not receive the notification and were subsequently marked as inactive.

from fcm-django.

I would suggest logging out the actual reason why FCM was unable to deliver the notification?

from fcm-django.

I would suggest logging out the actual reason why FCM was unable to deliver the notification?

as i mentioned in previous replay , The devices were connected to the network and actively running the application. means they were logged-in

from fcm-django.

Understood. But that alone is not informational enough. You will require the actual response from FCM, to be able to infer any conclusions here.

from fcm-django.

Also @irfankpr FCM will sometimes replace tokens for active devices in which case old ones will not work. In any way, you will need to diagnose why they got deactivated to proceed further

from fcm-django.