Cannot handle notification like Firebase "myBackgroundMessageHandler" in Killed state. about airship-flutter HOT 7 CLOSED

Right now we don't support waking the app up in the background, but would like to. I believe this requires isolates but I will see what other options flutter supports.

from airship-flutter.

Sure, Please let me know. If there is any way I can handle.

from airship-flutter.

@rakeshsalian039 I dug into the firebase implementation and they are indeed using an isolate. We attempted this in the past but it was a bit messy - https://github.com/urbanairship/airship-flutter/pull/84/files

I will try again this week on isolate support, hopefully in a way that wont completely change the plugin usage.

from airship-flutter.

Not in 5.3.0 but will target the next release. Most likely will require breaking APIs so probably a 6.0.0 release.

from airship-flutter.

So what is the timeline for 6.0.0 release? This is critical for one of the feature we have implemented.

from airship-flutter.

@rakeshsalian039 We are working on it now. Give us a few more days to get a better idea when the work will be done.

As a workaround, you could use both Airship and the firebase plugin. With firebase you can use the myBackgroundMessageHandler even for Airship pushes. The only thing you would have to do is extend the firebase messaging service from the firebase plugin, call through to airship, and register the new service at a higher priority.

from airship-flutter.

Released in 5.4.0:

Future<void> backgroundMessageHandler(
    Map<String, dynamic> payload,
    Notification? notification) async { 
  // Handle the message
  print("Received background message: $payload, $notification");
}

void main() {
  Airship.setBackgroundMessageHandler(backgroundMessageHandler);
  runApp(MyApp());
}

from airship-flutter.