Push notifications get "syserror" status when created from API

Hey there!

The push notifications of my app have stopped working today, apparently without a reason… I haven’t changed anything, neither in the app or in the back-end.

If I try to send a notification using the ionic.io dashboard, it works.

When I try to use the API, everything seem to work well but I don’t receive the notification:

> curl -X POST -H "Authorization: Bearer API_TOKEN" -H "Content-Type: application/json" -d '{ "tokens": ["DEVICE_TOKEN"], "profile": "production","notification": {"message": "Hello!"}}' "https://api.ionic.io/push/notifications"

API response:

{"meta": {"status": 201, "version": "2.0.0-beta.0", "request_id": "..."}, "data": {"app_id": "...", "config": {"profile": "production", "tokens": ["..."], "notification": {"message": "Hello!"}}, "uuid": "...", "state": "enqueued", "status": "open", "created": "2016-09-18T18:02:16.374288+00:00"}}

If I check the notification status, I get “queued” for 10 minutes and “syserror” after that, no errors:

>curl -X GET -H "Authorization: Bearer API_TOKEN" -H "Content-Type: application/json" -d '' "https://api.ionic.io/push/notifications/UUID/messages"

Initial API response:
{"data": [{"created": "2016-09-18T17:22:43.341618+00:00", "error": null, "user_id": null, "status": "queued", "uuid": "...", "notification": "...", "token": {"app_id": "...", "created": "2016-06-05T11:32:52.419662+00:00", "id": "...", "valid": true, "type": "android", "invalidated": null, "token": "..."}}], "meta": {"request_id": "...", "status": 200, "version": "2.0.0-beta.0"}}

API response after 10 minutes:
{"data": [{"created": "2016-09-18T17:22:43.341618+00:00", "error": null, "user_id": null, "status": "syserror", "uuid": "...", "notification": "...", "token": {"app_id": "...", "created": "2016-06-05T11:32:52.419662+00:00", "id": "...", "valid": true, "type": "android", "invalidated": null, "token": "..."}}], "meta": {"request_id": "...", "status": 200, "version": "2.0.0-beta.0"}}

Any idea what’s happening?

Thank you very much!

It was related to an API bug that has already fixed.