Rank 2: Process
Hi, I don't know exactly when, but I see that the push targets of almost all users have disappeared, is this normal?
Prj. ID. 6665de8b001d6c9b0a25
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 2: Process
Hi, I don't know exactly when, but I see that the push targets of almost all users have disappeared, is this normal?
Prj. ID. 6665de8b001d6c9b0a25
Ya all the same
How many? Could it be that some targets were expired, but not the one specified?
Rank 2: Process
sometimes 1, sometimes 2
Rank 2: Process
I once tried to send a push manually to an expired token and it sent it correctly, again via appwrite
Rank 2: Process
yes but even if it was considered expired it didn't delete them, today I found many deleted items, is there any scheduled event that cleans?
Send to only 1 target and you got an error saying it was expired?
Yes, they are deleted as a background job. No guarantee as to when exactly it'll run
Rank 2: Process
ah...but why they are expired...
Rank 2: Process
i need to investigate..
Rank 2: Process
no it is sent without errors, I will try again as soon as I have time
The only thing I can think of is it is marked as expired in Appwrite, then you update it, but it's still marked as expired, and then it gets deleted
Rank 2: Process
Is it marked as expired only when Google is engaged in an attempt to send a push?
What do you mean? The API call is made to Google/firebase and then we mark it as expired depending on the response
Rank 2: Process
On appwrite, is the status of "EXPIRED" inserted when the first push is sent?
It's supposed to be marked as expired only if firebase returns the not found or unregistered error
But I think we may be correlating it wrong so the wrong target in the batch is marked as expired
This is a PR to fix it: https://github.com/utopia-php/messaging/pull/88
Rank 2: Process
so there is actually an index problem, and a token that has not actually expired is then updated in the table
Rank 2: Process
@Steven Hi Steven, I saw that the fix to this problem was merged into master, just out of curiosity, how will this be released on the cloud now?
we need to deploy it
We've deployed the fix.
Let me know how it goes.
Rank 2: Process
good, for 1. where i can see if the push target is marked expired or not?
In the payload. For example, account.get() includes the targets.
Rank 2: Process
Perfect, I think I can see it with command cli, top, thank you