IOS Push notifications - app closed

Question

It seems push notification payload isn’t sending the Content-Available: true flag that is needed for app background message processing to be triggered. Can we somehow get around this limitation?

@pragma('vm:entry-point')Future<void> _firebaseMessagingBackgroundHandler(RemoteMessage message) async {  debugPrint('========================================');    debugPrint('BACKGROUND MESSAGE RECEIVED');    debugPrint('Message ID: ${message.messageId}');    debugPrint('========================================');

}

This vm entry point now isn’t getting reached but I notice when sending notifications through cloudkit and setting content-available: true it is getting triggered.

I also found that silent notifications from klaviyo are setting this flag, so the functionality is there.

Byrne C · Accepted Answer

Hi ​@Grandcruwijnen,Just checked in with our Push Notifications team about this. At the moment, we only support adding Content-Available: true to silent push notifications, and unfortunately, this can’t be added to standard IOS notifications. Apologies for this! Happy to reach out to our product team and recommend that we implement this in the future.

Grandcruwijnen · Answer

I have by the way also noticed the same issue for opening apps from closed state, initialMessage is not being set.

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials