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
At the moment, the push notification is immediately sent to users. However, the local news endpoint does not immediately include the new news item. If I click on the push notification, I am greeted with a not found error message in the app (as the api does not include the news item yet).
The push notification should only be sent once the news item is available in the API.
Maybe this is primarily an test cms issue though as it was not yet reported by anyone.
@steffenkleinle I just tested this on production and it works without a problem - but makes sense to keep it in mind and test it after the next release, right?
@steffenkleinle I just tested this on production and it works without a problem - but makes sense to keep it in mind and test it after the next release, right?
Hmm, interesting. Then it is maybe actually just a problem in the test cms due to less resources/computing power here?
Perhaps the order should still be fixed here (i.e. first saving and making sure the api is ready and only then push notification), but has no high prio at all. But feel free to just close this issue.
Describe the Bug
At the moment, the push notification is immediately sent to users. However, the local news endpoint does not immediately include the new news item. If I click on the push notification, I am greeted with a not found error message in the app (as the api does not include the news item yet).
The push notification should only be sent once the news item is available in the API.
Maybe this is primarily an test cms issue though as it was not yet reported by anyone.
Steps to Reproduce
Expected Behavior
The push notification is not sent before the news are ready in the api.
Actual Behavior
The push notification is sent before the news are ready in the api.
Additional Information
In the app we already make use of 1 second, but this does not seem to be enough.
Related Issues
N/A
The text was updated successfully, but these errors were encountered: