There is a server bug that is circumvented on Android and Desktop, but not on iOS.
- Bob creates a deck card.
- A notification is created on server with "You have created a deck card".
userId is Bob. author = userId is true.
- This notification is sent to Bob, as he is the author.
- However, since this notification is only made once, with Bob as
userId, it is never changed, and is also sent as a push notification to all other sharees, still appearing as "You have created a deck card". This is incorrect, as the sharees are not the author Bob.
Android and Desktop alleviate this by receiving the original notification, but then rerequesting the same notification, with their own userId for the logged in client user. This allows the notification to be constructed again, with the proper string. In this case, Alice, which author != userId. The notification will then be "Bob created a deck card".
Ultimately this bug should be resolved server side, but to keep feature parity with other clients, iOS should also rerequest an up to date notification.
There is a server bug that is circumvented on Android and Desktop, but not on iOS.
userIdis Bob.author = userIdis true.userId, it is never changed, and is also sent as a push notification to all other sharees, still appearing as "You have created a deck card". This is incorrect, as the sharees are not the author Bob.Android and Desktop alleviate this by receiving the original notification, but then rerequesting the same notification, with their own
userIdfor the logged in client user. This allows the notification to be constructed again, with the proper string. In this case, Alice, whichauthor != userId. The notification will then be "Bob created a deck card".Ultimately this bug should be resolved server side, but to keep feature parity with other clients, iOS should also rerequest an up to date notification.