ERROR - 2025-10-04 00:12:30 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 00:12:30 --> 
ERROR - 2025-10-04 07:44:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 07:45:53 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 07:54:48 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 07:55:30 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 07:58:57 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 08:00:56 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 08:08:33 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 09:24:20 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 09:24:20 --> 
ERROR - 2025-10-04 10:02:10 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 10:02:10 --> 
ERROR - 2025-10-04 10:15:08 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 10:15:08 --> 
ERROR - 2025-10-04 10:50:52 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 10:50:52 --> 
ERROR - 2025-10-04 10:56:11 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 10:56:11 --> 
ERROR - 2025-10-04 11:29:55 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 11:29:55 --> 
ERROR - 2025-10-04 11:34:23 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 11:34:23 --> 
ERROR - 2025-10-04 12:00:37 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 12:00:37 --> 
ERROR - 2025-10-04 12:00:37 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 12:00:37 --> 
CRITICAL - 2025-10-04 12:01:48 --> Class 'App\Commands\UserDeviceModel' not found
in APPPATH/Commands/SendScheduledNotifications.php on line 75.
 1 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 2 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 3 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 12:02:47 --> Trying to get property 'target_group' of non-object
in APPPATH/Commands/SendScheduledNotifications.php on line 93.
 1 APPPATH/Commands/SendScheduledNotifications.php(93): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Trying to get property \'target_group\' of non-object', '/home/busvalle/data.busvalley.com/busvalley_new/app/Commands/SendScheduledNotifications.php', 93, [...])
 2 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 3 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 4 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 12:05:04 --> Cannot use object of type stdClass as array
in APPPATH/Commands/SendScheduledNotifications.php on line 97.
 1 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 2 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 3 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
ERROR - 2025-10-04 12:05:30 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 12:05:31 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 12:07:50 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 12:07:51 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 12:07:51 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 12:07:52 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 12:25:56 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 12:25:56 --> 
ERROR - 2025-10-04 12:34:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 12:34:03 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 12:34:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 12:34:04 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 12:39:37 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 12:39:37 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 12:39:38 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 12:39:39 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 12:41:06 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 12:41:06 --> 
ERROR - 2025-10-04 12:42:01 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 12:42:01 --> 
ERROR - 2025-10-04 12:43:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 12:43:02 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 12:43:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 12:43:03 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 12:48:12 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 12:48:12 --> 
ERROR - 2025-10-04 12:53:19 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 12:53:19 --> 
CRITICAL - 2025-10-04 13:36:46 --> Undefined variable: trips
in ROOTPATH/modules/Notification/Views/notification/new.php on line 58.
 1 ROOTPATH/modules/Notification/Views/notification/new.php(58): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined variable: trips', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php', 58, [...])
 2 SYSTEMPATH/View/View.php(226): include('/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php')
 3 SYSTEMPATH/View/View.php(229): CodeIgniter\View\View->CodeIgniter\View\{closure}()
 4 SYSTEMPATH/Common.php(1174): CodeIgniter\View\View->render('Modules\\Notification\\Views\\notification/new', [], true)
 5 ROOTPATH/modules/Notification/Controllers/Notification.php(148): view('Modules\\Notification\\Views\\notification/new', [...])
 6 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->new()
 7 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 8 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 9 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
10 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 13:37:05 --> Undefined property: stdClass::$departure_date
in ROOTPATH/modules/Notification/Views/notification/new.php on line 60.
 1 ROOTPATH/modules/Notification/Views/notification/new.php(60): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$departure_date', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php', 60, [...])
 2 SYSTEMPATH/View/View.php(226): include('/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php')
 3 SYSTEMPATH/View/View.php(229): CodeIgniter\View\View->CodeIgniter\View\{closure}()
 4 SYSTEMPATH/Common.php(1174): CodeIgniter\View\View->render('Modules\\Notification\\Views\\notification/new', [], true)
 5 ROOTPATH/modules/Notification/Controllers/Notification.php(148): view('Modules\\Notification\\Views\\notification/new', [...])
 6 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->new()
 7 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 8 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 9 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
10 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 13:37:07 --> Undefined property: stdClass::$departure_date
in ROOTPATH/modules/Notification/Views/notification/new.php on line 60.
 1 ROOTPATH/modules/Notification/Views/notification/new.php(60): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$departure_date', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php', 60, [...])
 2 SYSTEMPATH/View/View.php(226): include('/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php')
 3 SYSTEMPATH/View/View.php(229): CodeIgniter\View\View->CodeIgniter\View\{closure}()
 4 SYSTEMPATH/Common.php(1174): CodeIgniter\View\View->render('Modules\\Notification\\Views\\notification/new', [], true)
 5 ROOTPATH/modules/Notification/Controllers/Notification.php(148): view('Modules\\Notification\\Views\\notification/new', [...])
 6 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->new()
 7 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 8 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 9 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
10 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 13:37:08 --> Undefined property: stdClass::$departure_date
in ROOTPATH/modules/Notification/Views/notification/new.php on line 60.
 1 ROOTPATH/modules/Notification/Views/notification/new.php(60): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$departure_date', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php', 60, [...])
 2 SYSTEMPATH/View/View.php(226): include('/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php')
 3 SYSTEMPATH/View/View.php(229): CodeIgniter\View\View->CodeIgniter\View\{closure}()
 4 SYSTEMPATH/Common.php(1174): CodeIgniter\View\View->render('Modules\\Notification\\Views\\notification/new', [], true)
 5 ROOTPATH/modules/Notification/Controllers/Notification.php(148): view('Modules\\Notification\\Views\\notification/new', [...])
 6 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->new()
 7 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 8 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 9 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
10 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 13:40:28 --> Undefined property: stdClass::$departure_date
in ROOTPATH/modules/Notification/Views/notification/new.php on line 60.
 1 ROOTPATH/modules/Notification/Views/notification/new.php(60): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$departure_date', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php', 60, [...])
 2 SYSTEMPATH/View/View.php(226): include('/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php')
 3 SYSTEMPATH/View/View.php(229): CodeIgniter\View\View->CodeIgniter\View\{closure}()
 4 SYSTEMPATH/Common.php(1174): CodeIgniter\View\View->render('Modules\\Notification\\Views\\notification/new', [], true)
 5 ROOTPATH/modules/Notification/Controllers/Notification.php(148): view('Modules\\Notification\\Views\\notification/new', [...])
 6 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->new()
 7 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 8 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 9 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
10 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 13:41:15 --> Undefined variable: trips
in ROOTPATH/modules/Notification/Views/notification/new.php on line 58.
 1 ROOTPATH/modules/Notification/Views/notification/new.php(58): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined variable: trips', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php', 58, [...])
 2 SYSTEMPATH/View/View.php(226): include('/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php')
 3 SYSTEMPATH/View/View.php(229): CodeIgniter\View\View->CodeIgniter\View\{closure}()
 4 SYSTEMPATH/Common.php(1174): CodeIgniter\View\View->render('Modules\\Notification\\Views\\notification/new', [], true)
 5 ROOTPATH/modules/Notification/Controllers/Notification.php(164): view('Modules\\Notification\\Views\\notification/new', [...])
 6 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->new()
 7 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 8 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 9 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
10 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 13:41:27 --> Undefined property: stdClass::$company_name
in ROOTPATH/modules/Notification/Views/notification/new.php on line 60.
 1 ROOTPATH/modules/Notification/Views/notification/new.php(60): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$company_name', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php', 60, [...])
 2 SYSTEMPATH/View/View.php(226): include('/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Views/notification/new.php')
 3 SYSTEMPATH/View/View.php(229): CodeIgniter\View\View->CodeIgniter\View\{closure}()
 4 SYSTEMPATH/Common.php(1174): CodeIgniter\View\View->render('Modules\\Notification\\Views\\notification/new', [], true)
 5 ROOTPATH/modules/Notification/Controllers/Notification.php(164): view('Modules\\Notification\\Views\\notification/new', [...])
 6 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->new()
 7 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 8 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 9 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
10 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 14:06:56 --> Undefined property: stdClass::$passenger_id
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 APPPATH/Commands/SendScheduledNotifications.php(107): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$passenger_id', '/home/busvalle/data.busvalley.com/busvalley_new/app/Commands/SendScheduledNotifications.php', 107, [...])
 2 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 3 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 4 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:07:02 --> Undefined property: stdClass::$passenger_id
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 APPPATH/Commands/SendScheduledNotifications.php(107): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$passenger_id', '/home/busvalle/data.busvalley.com/busvalley_new/app/Commands/SendScheduledNotifications.php', 107, [...])
 2 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 3 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 4 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:08:02 --> Cannot use object of type stdClass as array
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 2 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 3 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:08:18 --> Cannot use object of type stdClass as array
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 2 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 3 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:08:22 --> Cannot use object of type stdClass as array
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 2 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 3 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:09:21 --> Undefined property: stdClass::$passenger_id
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 APPPATH/Commands/SendScheduledNotifications.php(107): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$passenger_id', '/home/busvalle/data.busvalley.com/busvalley_new/app/Commands/SendScheduledNotifications.php', 107, [...])
 2 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 3 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 4 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:10:28 --> Undefined property: stdClass::$passenger_id
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 APPPATH/Commands/SendScheduledNotifications.php(107): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$passenger_id', '/home/busvalle/data.busvalley.com/busvalley_new/app/Commands/SendScheduledNotifications.php', 107, [...])
 2 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 3 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 4 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:10:58 --> Undefined property: stdClass::$passenger_id
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 APPPATH/Commands/SendScheduledNotifications.php(107): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$passenger_id', '/home/busvalle/data.busvalley.com/busvalley_new/app/Commands/SendScheduledNotifications.php', 107, [...])
 2 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 3 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 4 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
CRITICAL - 2025-10-04 14:11:02 --> Undefined property: stdClass::$passenger_id
in APPPATH/Commands/SendScheduledNotifications.php on line 107.
 1 APPPATH/Commands/SendScheduledNotifications.php(107): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Undefined property: stdClass::$passenger_id', '/home/busvalle/data.busvalley.com/busvalley_new/app/Commands/SendScheduledNotifications.php', 107, [...])
 2 SYSTEMPATH/CLI/Commands.php(65): App\Commands\SendScheduledNotifications->run([])
 3 SYSTEMPATH/CLI/Console.php(37): CodeIgniter\CLI\Commands->run('notifications:send', [])
 4 ROOTPATH/spark(97): CodeIgniter\CLI\Console->run()
ERROR - 2025-10-04 14:41:56 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 14:41:56 --> 
ERROR - 2025-10-04 14:43:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 14:43:02 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 14:43:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 14:43:04 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 14:58:58 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 14:58:58 --> 
ERROR - 2025-10-04 16:11:54 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 16:11:54 --> 
ERROR - 2025-10-04 16:38:26 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 16:38:26 --> 
ERROR - 2025-10-04 17:35:07 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 17:35:07 --> 
ERROR - 2025-10-04 17:42:29 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 17:42:29 --> 
ERROR - 2025-10-04 17:52:52 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 17:52:52 --> 
ERROR - 2025-10-04 18:00:11 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:00:11 --> 
ERROR - 2025-10-04 18:12:57 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:12:57 --> 
ERROR - 2025-10-04 18:14:53 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:14:53 --> 
ERROR - 2025-10-04 18:29:54 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:29:54 --> 
ERROR - 2025-10-04 18:36:01 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:36:01 --> 
ERROR - 2025-10-04 18:37:32 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:37:32 --> 
ERROR - 2025-10-04 18:42:04 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:42:04 --> 
ERROR - 2025-10-04 18:51:49 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:51:49 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:51:50 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:51:51 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:51:51 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:52:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:52:02 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:52:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:52:03 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:52:04 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:53:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:53:02 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:53:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:53:03 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:53:04 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:54:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:54:02 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:54:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:54:04 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:54:04 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:54:43 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:54:43 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:54:44 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:54:44 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:54:45 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:55:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:55:03 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:55:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:55:04 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:55:04 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:55:13 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:55:14 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:55:14 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:55:15 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:55:15 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:56:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:56:03 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:56:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:56:04 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:56:04 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:57:02 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:57:02 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:57:03 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:57:03 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:57:04 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:57:45 --> FCM Error: SenderId mismatch
ERROR - 2025-10-04 18:57:46 --> FCM Error: 

The message could not be delivered to the device identified by 'fjU6NJcMQ0mSaadkmPenF_:APA91bGNg93ikoa-jlQeshaBa_bnYlC3Emr_Qb3yQ_mfczYLsuI7trbFg8Dg-kWMHQ8c7q05C4tYcbaJq27GI7jHShZRTtYPKhwX56awYfa4kqDtr7z-jmY'.

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.


ERROR - 2025-10-04 18:57:46 --> FCM Error: 

The message could not be delivered to the device identified by 'c0FXZQsARaqcXZgrj85JwS:APA91bHKy-1cAUFs0GfcoZSrKy_YCO0VlrHjftl995qzQUngMPb1OVH0dFuXKmY2j7--Q9Kik7eXskLMyHpV-r0Czxb3k_lQDNxyIpfh2bjXEhasgt5AQeY'.

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.


ERROR - 2025-10-04 18:57:47 --> FCM Error: 

The message could not be delivered to the device identified by 'fvkdyQhmQVuMZo-4R56zq-:APA91bGKTzvnAXu1RK0ThaEwnFgXK-U5q6bB9LWSkZGMPxsDyhmaIdzcn34ngIzShYN7NJwEdTZ52EyyjuoWnS60ecDFqX0-AaWJ2PxJJhE831W663rioHI'.

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.


ERROR - 2025-10-04 18:57:47 --> FCM Error: 

The message could not be delivered to the device identified by 'cGKW_sjcQ1CV2y4i6Vx3PR:APA91bEA8BWi2CmmOX90eg2_USW_R-4haq0G6XHTyaORc1YmhikOL7ncdEUDcLp3UCMtktlMOOCVlwciCmvxLV0qWDjvYBaQFPtDCIg8EoN7FL1whNDkRzE'.

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.


ERROR - 2025-10-04 18:58:14 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 18:58:14 --> 
CRITICAL - 2025-10-04 19:15:33 --> syntax error, unexpected 'foreach' (T_FOREACH)
in ROOTPATH/modules/Trip/Controllers/Trip.php on line 561.
 1 SYSTEMPATH/Autoloader/Autoloader.php(291): CodeIgniter\Autoloader\Autoloader->includeFile('/home/busvalle/data.busvalley.com/busvalley_new/modules/Trip/Controllers/Trip.php')
 2 SYSTEMPATH/Autoloader/Autoloader.php(269): CodeIgniter\Autoloader\Autoloader->loadInNamespace('Modules\\Trip\\Controllers\\Trip')
 3 [internal function]: CodeIgniter\Autoloader\Autoloader->loadClass('Modules\\Trip\\Controllers\\Trip')
 4 [internal function]: spl_autoload_call('Modules\\Trip\\Controllers\\Trip')
 5 SYSTEMPATH/CodeIgniter.php(890): class_exists('\\Modules\\Trip\\Controllers\\Trip', true)
 6 SYSTEMPATH/CodeIgniter.php(484): CodeIgniter\CodeIgniter->startController()
 7 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 8 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
 9 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
CRITICAL - 2025-10-04 19:21:12 --> Trying to get property 'status' of non-object
in ROOTPATH/modules/Notification/Controllers/Notification.php on line 413.
 1 ROOTPATH/modules/Notification/Controllers/Notification.php(413): CodeIgniter\Debug\Exceptions->errorHandler(8, 'Trying to get property \'status\' of non-object', '/home/busvalle/data.busvalley.com/busvalley_new/modules/Notification/Controllers/Notification.php', 413, [...])
 2 SYSTEMPATH/CodeIgniter.php(932): Modules\Notification\Controllers\Notification->cancel('18')
 3 SYSTEMPATH/CodeIgniter.php(497): CodeIgniter\CodeIgniter->runController(Object(Modules\Notification\Controllers\Notification))
 4 SYSTEMPATH/CodeIgniter.php(366): CodeIgniter\CodeIgniter->handleRequest(null, Object(Config\Cache), false)
 5 FCPATH/index.php(65): CodeIgniter\CodeIgniter->run()
 6 ROOTPATH/index.php(2): require_once('/home/busvalle/data.busvalley.com/busvalley_new/public/index.php')
ERROR - 2025-10-04 19:24:54 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 19:24:54 --> 
ERROR - 2025-10-04 19:34:16 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 19:34:16 --> 
ERROR - 2025-10-04 19:34:27 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 19:34:27 --> 
ERROR - 2025-10-04 19:51:03 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 19:51:03 --> 
ERROR - 2025-10-04 20:22:34 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 20:22:34 --> 
ERROR - 2025-10-04 20:53:07 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 20:53:07 --> 
ERROR - 2025-10-04 21:09:12 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 21:09:12 --> 
ERROR - 2025-10-04 21:43:00 --> Email: Unable to send email using PHP mail(). Your server might not be configured to send mail using this method.
ERROR - 2025-10-04 21:43:00 --> 
