Versão 1.4.1 not working onLaunch app closed

[mwaylabs]

Versão 1.4.1 not working onLaunch app closed

[szotp]

I think I know what me the issue you reported, will check later today.

[szotp]

Please check on latest prelease (1.5.0-dev.1). Note that this must be tested in release mode, otherwise app will just crash on start (known bug flutter/flutter#67624 (comment)).

[mrdc]

Please check on latest prelease (1.5.0-dev.1)

Hi, I'm testing this version right now. When app is in foreground payload.data.entries.first.key and payload.data.entries.first.value do work - I have access to the data, but when going from background to foreground with onResume, these fields are empty: in logs actionIdentifier:com.apple.UNNotificationDefaultActionIdentifier instead of real data.

BTW How can I access data in apns 1.5.0+ as in earlier versions: something like this: message['aps']['alert']['body']?

[szotp]

BTW How can I access data in apns 1.5.0+ as in earlier versions: something like this: message['aps']['alert']['body']?

That's not possible, because firebase_messaging on Android side has discarded Map<String, dynamic> in favor of RemoteMessage object. But you should be able to get body parameter with payload.notification.body

[mrdc]

That's not possible, because firebase_messaging on Android side has discarded Map<String, dynamic> in favor of RemoteMessage object. But you should be able to get body parameter with payload.notification.body

Thanks, it works. Also for subtitle, sound, badge etc via payload.notification.apple

I'm quite new to all this firebase stuff, so it's not clear - I'm using iOS, so should I switch to flutter_apns_only?

[szotp]

For most use cases I recommend using flutter_apns. If you are not supporting Android, or want to have custom notification handling there, you can go with flutter_apns_only.

[szotp]

Checked the issue, I think the problem is on your side. You are logging payload.data.entries.first but there may be more entries, so just log entire payload.data map.

Adding actionIdentifier to the data map was the easiest way to pass additional information inside RemoteMessage object, the downside is that you will see more data entries than expected.

[mrdc]

Checked the issue, I think the problem is on your side. You are logging payload.data.entries.first but there may be more entries, so just log entire payload.data map.

Double checked - I've looked at wrong output in console, so no issues :) Works fine in foreground, background, locked states.
Thanks!

[lordgreg]

@moreirawebmaster you can of course re-open the issue if your report wasn't resolved with our update. Thank you.