Skip to main content

Apple Push Notification Changes for iOS 11

Push Notification

With the advent of iOS 11, Apple has introduced changes in the way they handle certain kinds of push messages. This was done to improve battery life, but comes at a cost of user experience that is likely to affect your app.

What Apple has done is to implement a service called the “DuetActivitySchedulerDaemon” (DASD). Part of the job of this service is to measure how frequently your app is used. If your app is not used frequently, DASD may delay or discard push messages sent to your app which have the content-available flag set.

On iOS 10, Apple acknowledged a defect where push notifications containing content-available would not be delivered after an app was force-closed and rebooted. Based on what Apple has delivered in iOS 11, we assume this defect will not be fixed.

Until we have engineered solutions to work around this issue, be aware when deploying:
  • silent (data) pushes
  • in-app messages
  • pushes with dynamic categories
  • simple pushes which have more than one associated action (these are implemented with dynamic categories)
  • API pushes you send which include content-available
These messages all make use of the content-available flag and may not be delivered except to those users who use your app frequently (multiple times a day). Simple messages with only one associated action are unaffected by this issue.

We will provide a new WCA SDK for iOS that works around these Apple issues. An ETA for that SDK should be available soon.

For further technical details, see the discussion here:
https://stackoverflow.com/questions/44796613/silent-pushes-not-delivered-to-the-app-on-ios-11/

This issue won’t be seen when your app is connected to the debugger, but will appear in production apps.

Users of Xtify 2.x product who include the “Content Available” flag in their campaigns will also be affected by this Apple decision.



Comments

Popular Posts

What are the Alternatives of device UDID in iOS? - iOS7 / iOS 6 / iOS 5 – Get Device Unique Identifier UDID

Get Device Unique Identifier UDID Following code will help you to get the unique-device-identifier known as UDID. No matter what iOS user is using, you can get the UDID of the current iOS device by following code. - ( NSString *)UDID { NSString *uuidString = nil ; // get os version NSUInteger currentOSVersion = [[[[[UIDevice currentDevice ] systemVersion ] componentsSeparatedByString: @" . " ] objectAtIndex: 0 ] integerValue ]; if (currentOSVersion <= 5 ) { if ([[ NSUserDefaults standardUserDefaults ] valueForKey: @" udid " ]) { uuidString = [[ NSUserDefaults standardDefaults ] valueForKey: @" udid " ]; } else { CFUUIDRef uuidRef = CFUUIDCreate ( kCFAllocatorDefault ); uuidString = ( NSString *) CFBridgingRelease ( CFUUIDCreateString ( NULL ,uuidRef)); CFRelease (uuidRef); [[ NSUserDefaults standardUserDefaults ] setObject: uuidString ForKey: @" udid " ]; [[ NSUserDefaults standardUserDefaults ] synchro...

Ultimate Folder Structure For Your React Native Project

  Ultimate Folder Structure For Your React Native Project React native project structure React Native is a flexible framework, giving developers the freedom to choose their code structure. However, this can be a double-edged sword for beginners. Though it offers ease of coding, it can soon become challenging to manage as your project expands. Thus, a structured folder system can be beneficial in many ways like better organization, simplified module management, adhering to coding practices, and giving a professional touch to your project. This write-up discusses a version of a folder arrangement that I employ in my React Native projects. This structure is based on best practices and can be modified to suit the specific needs of your project. Before we get into the project structure let’s give credit to @sanjay who has the original idea of the structure but I modify his version of the code, to make it better. Base library axios  — For network calling. react-navigation ...

16 AWS Gotchas

16 AWS Gotchas In January I launched the MVP for my own startup,  Proximistyle , which helps you find what you’re looking for nearby. On advice from friends and industry contacts I chose AWS as my cloud provider. Having never had to set up my own cloud infrastructure before, the learning curve to get from no experience to a stable VPC system I was happy with was significantly steeper than expected, and had its fair share of surprises. #1 Take advantage of the free resources offered AWS offers a free tier for new accounts. If you have recently bought a domain and set up a company you qualify for the free tier for a year. Additionally, if you are a bootstrapped startup you can apply for  the Startup Builders package  and get $1000 in AWS credits. After doing the above, you’re now ready to get started with setting up the AWS infrastructure for your startup. #2 Set up billing budgets and alerting The very first thing you should do after setting up billing, is enabling a budge...