[2026-04-07 17:40:09] production.ERROR: 

The message could not be delivered to the device identified by 'fqRML36ohUqQrfrjEetWUg:APA91bEVUcrWZ3rS5pUO7f0ZV9Dwus4Tew98h9Saj0JQRrvfRaRX-dw0OLGzif5p2Cs4ssueXhmx1wfifMcugmVZKIUcmcDGTQhYIcRbZkr-KwBzTg5b_yUqaiTjYfaFkpX-gEcseCcc'.

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.

  
[2026-04-07 17:40:10] production.ERROR: 

The message could not be delivered to the device identified by 'ceSLcn69JUQRvzwoYNSF08:APA91bFG7AHzh0iKQNSONwZn8LvViK3szxOINF209cqoDVZ4ebE0tsNy0KfI8B0W38yM-93bIziM4pVzprMJVKfB__ZYtTIS3zBRXoD9CCyTP74Yie9n_rk'.

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.

  
[2026-04-07 17:40:22] production.ERROR: 

The message could not be delivered to the device identified by 'fqRML36ohUqQrfrjEetWUg:APA91bEVUcrWZ3rS5pUO7f0ZV9Dwus4Tew98h9Saj0JQRrvfRaRX-dw0OLGzif5p2Cs4ssueXhmx1wfifMcugmVZKIUcmcDGTQhYIcRbZkr-KwBzTg5b_yUqaiTjYfaFkpX-gEcseCcc'.

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.

  
[2026-04-07 17:40:23] production.ERROR: 

The message could not be delivered to the device identified by 'ceSLcn69JUQRvzwoYNSF08:APA91bFG7AHzh0iKQNSONwZn8LvViK3szxOINF209cqoDVZ4ebE0tsNy0KfI8B0W38yM-93bIziM4pVzprMJVKfB__ZYtTIS3zBRXoD9CCyTP74Yie9n_rk'.

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.