awesome_notifications | complete solution to create Local Notifications | Notification library

I finally found the solution: upgrading packages (flutter pub upgrade). By chance, the issue was fixed by maintainers of path_provider. I was in version 2.0.10 when the issue occurs and the version 2.0.11 fixes it.

I tried to do this but only in December, when I got the issue for the first time and it did not solve it at this time.

To understand the origin of the fix, I checked which packages were updated in pubspec.lock. I saw that path_provider_android was updated and not path_provider became 'transitive':

Found the answer while surfing the GitHub Repository of awesome_notifications. The notification can straightly be dismissed without opening the app by adding buttonType as ActionButtonType.DisabledAction in the NotificationActionButton

just like this:

As suggested by שו אוהב אותך, problem seems to be with flutter_sound plugin. I switched from flutter_sound to flutter_sound_lite but problem remained.

So finally I ended up developing my own plugin for Flutter. Currently it's working for android only but will be brought available for IOS soon.

Now my appbundle size has reduced to 47.6 MBs from 123.6 MBs.

Plugin link is given below if anyone has the same issue:

Flutter Sound System - Plugin Link

FCM does not work on the iOS simulator, so thats half the question solved. For physical devices, take a look at some debugging steps I wrote in detail on a library I work on.

There are multiple ways push notification can go wrong on iOS. When you say: the app never receives, do you mean your Flutter application doesn't get the message? Your device could still be receiving them.

• Open Console.app on your mac, and start the logging for your physical device. Filter for dasd process, and you can see push notification related logs to see if your device rejected the push notification and did not send it to your app. Most likely, its a problem with how you structured your message.
• You can also try to debug the didReceiveRemoteNotification method on the iOS side inside the Flutterfire firebase_messaging iOS code. That would mean the message is received by the app.

1. My iOS physical device receives push notifications, but only when the app is in the background or closed but NOT when in the foreground.

So you want to show notifications in the foreground? You need to implement userNotificationCenter(_:willPresent:withCompletionHandler:), for example, in Swift:

Firebase Cloud Messaging(FCM) has two types of messages:

• Notification messages in which FCM automatically displays the message to end-user devices on behalf of the client app.
• Data messages in which your app is responsible for processing data messages.

About FCM messages

You should use a data message so your app does not display the automatic notification that comes with the notification message type that you currently use.

So if your cloud function contained this code below to send notification messages:

The error you get is not caused by _notificationsActionStreamSubscription.

If you read carefully it says

Stream has already been listened to

That means that probably AwesomeNotifications().actionStream can only handle one listener at a time.

_notificationsActionStreamSubscription.cancel() doesn't seem to work, it is possible that AwesomeNotifications().actionStream doesn't know that the stream listener has been closed.

Every time the page get pushed, it is rebuilt, and AwesomeNotifications() throw an error becouse it thinks that you are attacching a second listener.

So I came with this solution: Move the notificationsActionStreamSubscription to a widget which is parent to HomeView. Create the instance right there in the parent, and then attach it to the actionStream. Every time you call Navigator.pushReplacement send it as a parameter.

HomeView: (I made it a statefullwidget)

in order to send custom notifications you can create your own server environment (backend) and from there perform all the logic to be able to send the notifications to the devices.

The only thing you need to be able to send a personalized notification from an external environment is to have the token device, in the case that you will send it to a specific person, you can also send notifications if the devices are subscribed to a topic.

This is the documentation to send notifications from a server to the device:

https://firebase.google.com/docs/cloud-messaging/http-server-ref