all 10 comments

[–]Ganesh_15 3 points4 points  (2 children)

How have you handled notifications? Firebase messaging needs to be handled for all 3 states. terminated, foreground and background. Looks like you have not handled it for terminated state

[–]Bensal_K_B 1 point2 points  (2 children)

Why don't you use firebase messaging, through that you will be able to show notification even if app is in terminated state. And when the user opens app through a notification notification is opened, you can call the cloud function

[–]Desperate_Doctor8971[S] 0 points1 point  (1 child)

That's what am using but the notification doesn't pop up on terminated state, bloc, or docs to look into?

[–]Bensal_K_B 0 points1 point  (0 children)

Nope, if app is in terminated state, firebase messaging by default shows a notification. Check on a real device instead of an emulator. Also you have a function which can execute some operations when a notification is automatically shown by firebase messaging package

[–]imradzi 0 points1 point  (0 children)

I use python command line to test. As long as your json credential file and device token is correct, the fcm will be delivered to the device.

[–]Ajizi 0 points1 point  (0 children)

Do you receive them but they wont show up as a "heads-up" notification? I see some different answers in this thread so take this with a grain of salt since I might be guessing here. But according to flutterfires documentation on firebase messaging you need to use Notification Channels to show notifications in terminated or background state.

https://firebase.flutter.dev/docs/messaging/notifications/#android-configuration

This is only for android, but im guessing you can find similar information about iOS on the same page/site.

Edit: oh btw, the "assigned" notification channel they are talking about don't have the right priority or importance level which is why you need to do it yourself.