Hi, most of our systems still use the Binary Provider API. Since approximately 1:48am Eastern Time on 12/5, we have been receiving about 35 errors per minute with Error Code 1, which is "Processing Error." We're seeing this across multiple data centers.
Is anyone else experiencing this? We've been sending push for years and have never hit this error code until today.
We have a new implementation also using the Binary Provider API. It is still in testing so not using the production APNS yet.
For what its worth, the test service, APNS Sandbox, is not returning any error codes. It has stopped delivering notifications as of last Friday 12/02/2016 around 5pm, but that is probably a separate issue than what you are seeing.
I should mention that retries typically succeed after one attempt, though sometimes the retry also gets error code 1 back, but then a second retry seems to succeed.
In our case it was a data issue. We had started including double-quotes in the alert text and APNS silently rejects those requests. Would have been nice to get an error code back in that case instead.
Hello John,
I have the same issue. It started yesterday and it keeps occurring today as well.
Bogdan
We're also seeing this. Has anyone had any luck with a response to radars or TSIs? I'm not sure if we should use one of our TSIs on this incident, but we rely pretty heavily on push notifications to work.
Same here, started yesterday. Random failures on pushes with error code 1: APNS Processing Error
Same here, had anyone submit a bug report?
We have been getting too many error code 1: APNS Processing Error since 16 Nov 2017.
Does anyone have same issue?
We have the same error since that date. Since we're using the not so recently maintained java-apns (https://github.com/notnoop/java-apns) Framework, we don't really see what's the actual error (it doesn't know the i.e. error code 10 and 128), but instead we see some error code 1 and a lot of error code -2 (unknown -> not 0 to 8).
I don't know if or where an official apple contact exists. Does anyone know something more or could point me into the right direction?
Since you experienced the behaviour at the same time we did I highly suspect that apple changed something with the API. I tried finding out what this could be yesterday and today but sadly I wasn't lucky.
