Libin Lu
Libin Lu
@dowgsss then why not just act on the callback data?
`getInitialNotification()` should not be updated because the app is just suspended, not killed. The app status is persisted. Are you still on the same page when you resume the app?
clear derived data? usually it happens when the build is reusing some old derived data
I use ios/Frameworks for both react and fcm library. check the manual linking
is there any docs about the change?
`issue 1: I am unable to get custom data (key:value) sent along the notification in the app` If you are setting `data` together with `notification`. Data will be ignored in...
could it be phone setting that limits it?
``` async (notif) => { // optional, do some component related stuff alert(JSON.stringify(notif)) ``` blow up, possibly `alert`?
where is your `show_in_foreground` assignment? try calling presentLocalNotification directly and see if you see error also it is very rare that you will need to call `presentLocalNotification` in notification callback...
you see the error because something in the handler callback threw javascript error. do try catch and print out the exception also, where do you see the example calling FCM.presentLocalNotification...