We're having problems with IOS notifications taking some considerable time to come through, and when they come through the phone thinks they arrived up to 25 minutes before we see them.
We've just setup a second PushWoosh app.
This second app has an identical backend feeding it as our first PushWoosh app which has been running for over a year. Indeed it is the same backend as our first app, not just identical :) We push similar information to two different apps from the same backend server. We just change the credentials over.
We are seeing notifications arrive on our first app as we expect, but notifications sent in exactly the same way for the second app (with different PushWoosh credentials for the different apps) can take some time to appear.
We've checked out logs on our server and it looks OK, we see the same OK responses from PushWoosh.
We have checked the PushWoosh Push History and it doesn't really say a great deal, we can see at a high level that we have sent X number of pushes and it says they are OK. However they don't necessarily appear on our phones or they suddenly turn up 30 minutes after they were sent. We can see a few pushes that say invalid token but no further details. It would be great to find out what these are.
Due to the nature of the data, we can go for hours without any pushes being sent which makes debugging difficult. If we send things from a test server to IOS apps that we have built and installed locally, it seems to work OK.
We are using the Cordova PushWoosh plugin 6.4.1 We are using IOS 8,9 and 10 for testing. The client code for receiving the notifications is identical across our two apps. Its been running for nearly a year so we think it should be fine.
We're going to setup a pre-production server to try this out so we have live data but in a test environment as we currently use test data in a test environment. We are wondering if Apple certificates are anything to do with this. They do seem to cause problems. This will be tomorrows activity, but we'd be interested if there are known problems sending out this evening around 1900GMT.
Also suggestions for better debugging welcomed as we're struggling to find any obvious errors.
Please sign in to leave a comment.