[2025-08-29 11:53:03] production.ERROR: 

The message could not be delivered to the device identified by 'ejEZlMKMrUxksxdvxiKh99:APA91bFILE1MRSH1FlyLtRIZBkmr5va6Ojso2rnTb3BkzOUvtD4Qjy0mnNQNL6CC7Z2JUKK-wkcR9SpZtq-YtL-hRzv8xjWeRjAfnpNCsbGANbo1gQfsUoNImUQ_PpMx38oo1PAldz25'.

Although the token is syntactically correct, it is not known to the Firebase
project you are using. This could have the following reasons:

- The token has been unregistered from the project. This can happen when a user
  has logged out from the application on the given client, or if they have
  uninstalled or re-installed the application.

- The token has been registered to a different Firebase project than the project
  you are using to send the message. A common reason for this is when you work
  with different application environments and are sending a message from one
  environment to a device in another environment.

  
[2025-08-29 11:53:03] production.ERROR: 

The message could not be delivered to the device identified by 'dh93YbRBp02onf6qKG6FYH:APA91bH-apNFym-bcb-4KNk9Usd2udupBcrJMJTcrAK8EJFaQYKE8e41ybN121fu7V5P1uPOaC5yMIlM0cLKFK-GRMOeBEj1XDaRgCVw9j9WWlPPRuQr5jw'.

Although the token is syntactically correct, it is not known to the Firebase
project you are using. This could have the following reasons:

- The token has been unregistered from the project. This can happen when a user
  has logged out from the application on the given client, or if they have
  uninstalled or re-installed the application.

- The token has been registered to a different Firebase project than the project
  you are using to send the message. A common reason for this is when you work
  with different application environments and are sending a message from one
  environment to a device in another environment.

  
[2025-08-29 11:53:26] production.ERROR: 

The message could not be delivered to the device identified by 'ejEZlMKMrUxksxdvxiKh99:APA91bFILE1MRSH1FlyLtRIZBkmr5va6Ojso2rnTb3BkzOUvtD4Qjy0mnNQNL6CC7Z2JUKK-wkcR9SpZtq-YtL-hRzv8xjWeRjAfnpNCsbGANbo1gQfsUoNImUQ_PpMx38oo1PAldz25'.

Although the token is syntactically correct, it is not known to the Firebase
project you are using. This could have the following reasons:

- The token has been unregistered from the project. This can happen when a user
  has logged out from the application on the given client, or if they have
  uninstalled or re-installed the application.

- The token has been registered to a different Firebase project than the project
  you are using to send the message. A common reason for this is when you work
  with different application environments and are sending a message from one
  environment to a device in another environment.

  
[2025-08-29 11:53:26] production.ERROR: 

The message could not be delivered to the device identified by 'dh93YbRBp02onf6qKG6FYH:APA91bH-apNFym-bcb-4KNk9Usd2udupBcrJMJTcrAK8EJFaQYKE8e41ybN121fu7V5P1uPOaC5yMIlM0cLKFK-GRMOeBEj1XDaRgCVw9j9WWlPPRuQr5jw'.

Although the token is syntactically correct, it is not known to the Firebase
project you are using. This could have the following reasons:

- The token has been unregistered from the project. This can happen when a user
  has logged out from the application on the given client, or if they have
  uninstalled or re-installed the application.

- The token has been registered to a different Firebase project than the project
  you are using to send the message. A common reason for this is when you work
  with different application environments and are sending a message from one
  environment to a device in another environment.