This was due to a bug in discourse-push-notifications and has been fixed in
discourse-push-notifications
Thanks for reporting @steveb