Common IOS notifications problems

Push Notifications allow your app to send any kind of message to your users, enhancing their overall experience. But when enabling this feature there are a few things to keep in mind and potential pitfall to avoid. Apple Push Notifications or APNs is similar to a 3rd party API that runs on its own. When a IOS app registers for APNs it sends over the unique device ID, along with other information. It also send the Device ID to your own backend server if set-up. When you push a notification out to the APN system, it takes the device ID and sends the notification to the correct matching iPhone. One common problem is that the device IDs for that iPhone could and will change. This is done for security reasons and is random to when or why. If your backend server has an old device ID, the message sent out won’t get to the user. Therefore its important to update your backend server with the new/current device ID as often as you can. Another common issue is the fact that the APNs system has two servers, production and development. If your application is configured with the development server your production apps will stop receiving notifications after a period of time when a new device ID is generated and updated to your backend server. That new ID is also updated on APNs but now only on the developer server and not on the production server which is where your backend server is sending to. You have to make sure your app is updating the production server. This is easily done by making sure your provisional profiles that are set on the build settings are distribution profiles and not development. APNs is a complicated and advanced system and it's important to understand how it is designed and operates to make sure notifications work as well as possible