You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is important to note that the issue does not depend on which user the notify method is executed for, nor does it vary based on the specific notification being sent. The error occurs consistently across different users and notification types.
After investigating, I found that the problems arise here in the ExpoNotificationsService::checkAndStoreTickets(Collection $tokens), particularly in this line: $this->ticketStorage->store($ticket->ticketId, $tokens->get($index));
Variable dumps from the first call ($user->notify(new NewMessageNotification());):
It tries to re-store record [0], instead of storing only [1].
I also couldn’t find any logic to clear $this->tokens, which means that beyond the storage problem, I encounter issues using the notify method in a queue container. Over time, $this->tokens accumulates many records.
I was also able to reproduce the issue by executing the following in Tinker:
I encountered an issue when sending multiple notifications using notify().
Steps to Reproduce:
Expected Result:
Notifications should be sent without exceptions.
Actual Result:
After investigating, I found that the problems arise here in the
ExpoNotificationsService::checkAndStoreTickets(Collection $tokens)
, particularly in this line:$this->ticketStorage->store($ticket->ticketId, $tokens->get($index));
Variable dumps from the first call (
$user->notify(new NewMessageNotification());
):From the next call ($user2->notify(new UpcomingCallNotification());):
It tries to re-store record [0], instead of storing only [1].
I also couldn’t find any logic to clear
$this->tokens
, which means that beyond the storage problem, I encounter issues using the notify method in a queue container. Over time, $this->tokens accumulates many records.I was also able to reproduce the issue by executing the following in Tinker:
This results in the following error:
The text was updated successfully, but these errors were encountered: