Closed ahmedsafadii closed 5 months ago
I was getting sometimes this issue into my backend side where, the returned value from FE was nil
Value where it's not a valid UUID
for the player, please ensure that the FE is sending the player_id
as expected and add a validation for checking if you are receiving the nil
from your server side skip it and continue the logic and add a retry method to send the notification for these users, also if you add a method that converting the un valid UUID
to be set as a NULL
value also will be ok.
@ahmedesmail07 Thank you for your note, yes i found the issue it was not NULL issue, it was that there is a record with empty string value which cuz the issue.
What happened?
If you try to send notification and there was at least 1 invalid player id, the request fail
Steps to reproduce?
What did you expect to happen?
to get something like
<Response [200 OK]>------{'id': '0c3212d8-ec61-4ff5-bb7f-89f8c3feab0f', 'external_id': None, 'errors': {'invalid_player_ids': ['03cec736-f85b-46a9-878a-f6d01c150483', ]
and send the notification for valid player ids
Relevant log output
Code of Conduct