I'm writing for the Synyx GmbH & Co. KG mobile solutions blog. From time to time, I'll cross post articles here, if I think they are of interest for you. If you'd like to read all of my other posts, subscribe to the Synyx Mobile Solutions Blog.When you enable Apple Push Notifications (APN) for your App, your device generates a unique device token and pass it to the didRegisterForRemoteNotificationsWithDeviceToken method in your App delegate. Usually, you'll hand the token to your server in order for it to push notifications to your device.
There are different tokens for production and sandbox, depending on which provisioning profile you build/sign your App with. One more gotcha, you need to be aware of when it comes to those device tokens: don't mix production and sandbox tokens!
If you try to send a push notification to the production servers, using a device token meant for the sandbox, Apple's servers totally block all other notification, which you are trying to send with the same connection. If you have a scheduled push notification like we do with "I think I spider", one wrong device token ruins the fun for everyone!
We decided to separate our production and test environment and use preprocessor conditional inclusion to point to different urls in our App. Unfortunately, we had to learn the hard way how tedious this gotcha can be to track down!
Supported by:
Sherweb - Hosted Exchange Hosting
Vircom - Email Security Software
2 comments:
We have our business email on Intermedia’s hosted server. It’s worked out well having it set up to automatically archive everything. It definitely helps keep everything we could need accessible. It also is easy to check on my phone so I can stay in touch no matter where I am.
There are a lot of web-hosting services that would potentially suit your needs. We perhaps can help you, kindly check GuidesFor EmailSecurity site. We helps companies like yours compare Security tool sites across the globe.
Post a Comment