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

Post a Comment

Thank You.

Popular Posts

How I Reduced the Size of My React Native App by 85%

How and Why You Should Do It I borrowed 25$ from my friend to start a Play Store Developer account to put up my first app. I had already created the app, created the assets and published it in the store. Nobody wants to download a todo list app that costs 25mb of bandwidth and another 25 MB of storage space. So today I am going to share with you how I reduced the size of Tet from 25 MB to around 3.5 MB. Size Matters Like any beginner, I wrote my app using Expo, the awesome React Native platform that makes creating native apps a breeze. There is no native setup, you write javascript and Expo builds the binaries for you. I love everything about Expo except the size of the binaries. Each binary weighs around 25 MB regardless of your app. So the first thing I did was to migrate my existing Expo app to React Native. Migrating to React Native react-native init  a new project with the same name Copy the  source  files over from Expo project Install all de...
Post a Comment
Read more

How to recover data of your Android KeyStore?

These methods can save you by recovering Key Alias and Key Password and KeyStore Password. This dialog becomes trouble to you? You should always keep the keystore file safe as you will not be able to update your previously uploaded APKs on PlayStore. It always need same keystore file for every version releases. But it’s even worse when you have KeyStore file and you forget any credentials shown in above box. But Good thing is you can recover them with certain tricks [Yes, there are always ways]. So let’s get straight to those ways. 1. Check your log files → For  windows  users, Go to windows file explorer C://Users/your PC name/.AndroidStudio1.4 ( your android studio version )\system\log\idea.log.1 ( or any old log number ) Open your log file in Notepad++ or Any text editor, and search for: android.injected.signing and if you are lucky enough then you will start seeing these. Pandroid.injected.signing.store.file = This is  file path where t...
Post a Comment
Read more

Video Calling In IOS Objective C

Video Calling Sources Project homepage on GIT — https://github.com/QuickBlox/quickblox-ios-sdk/tree/master/sample-videochat-webrtc Download ZIP - https://github.com/QuickBlox/quickblox-ios-sdk/archive/master.zip Overview The VideoChat code sample allows you to easily add video calling and audio calling features into your iOS app. Enable a video call function similar to FaceTime or Skype using this code sample as a basis. It is built on the top of WebRTC technology.            System requirements The QuickbloxWebRTC.framework supports the next:     * Quickblox.framework v2.7 (pod QuickBlox)     * iPhone 4S+.     * iPad 2+.     * iPod Touch 5+.     * iOS 8+.     * iOS simulator 32/64 bit (audio might not work on simulators).     * Wi-Fi and 4G/LTE connections. Getting Started with Video Calling API Installation with CocoaPods CocoaPods is a dependency manag...
Post a Comment
Read more