[Question] Android Not Receiving IFirebasePushNotification.NotificationReceived Event

[jamesbdarcy]

Thomas

Your plugin is wonderful. Thank you.

I have been able to successfully integrate the plugin and have it working for both Android and iOS. I am receiving Push notifications from FCM on both OS's whether the app is stopped, in background or forground. Fabulous!

There is one anomoly, however.

I have placed event handlers for the IFirebasePushNotification events within the App.xaml.cs file, rather than a Page, as I would like to be notified at all times when an event comes in and not rely on the user being on a page. I have placed the event handlers in App.xaml.cs, rather than Platform/Android/MainActivity as I would like to be notified of the TokenRefreshed, NotificationAction and NotificationReceived events on both OS's.

Placing them in App.xaml.cs works fine for iOS but not in Android.

In Android I do receive the NotificationAction when the user selcts an action but I do not receive either of the other two events, NotificationReceived and TokenRefreshed.

Is there a reason that these events are not being raised on the Android platform? Note, that I am receiving the actual Push Notifications, but the library events are not being raised.

I hope you can assist.

Kind regards

James

[jamesbdarcy]

I should add that I am using dotnet 9. Not sure if that makes any difference.

[thomasgalliker]

Hi James. We're talking about different problems here.
First of all, it's all it's totally fine to subscribe the events in App.xaml.cs. For better testability however, I would recommend to subscribe them in a viewmodel - kind of "the main viewmodel" which is always present while the app is in use. No matter which sub-page the user navigated to, you'll still received the event notifications as long as the root/main page is on the navigation stack.

It's hard to tell why NotificationReceived and TokenRefreshed events are not fired in your case. Of course, they should be raised at some point. I would not care too much about TokenRefreshed as it takes pretty much time until a token is invalidated. Just add logging and you'll sooner or later see log messages in your log.

Generally, it pays off to setup logging. I do write a lot of useful log messages to the log which helps debugging problems.

Would you mind to create a small reproduction app so that I can see what you're trying to achieve?
Did you also checkout the sample app in this repo? And, there is a quite big postman collection with a lot of sample push notifications for several different scenarios. Have a look.

[jamesbdarcy]

Hi Thomas

Thanks for your response.

You know what, I never thought through the fact that the MainView is always on the stack! I feel kinda stupid about that. It's probably easiest if I put the event handlers in there and see what happens.

I have looked fairly closely at the sample app and that helped me understand the mechanisms of your library very well. I also use logging quite a lot.

I will have a look at th ePostman app as well.

Cheers

James

[thomasgalliker]

Don't worry. Feel free to share a small repro app so I can assist you in resolving the issue. Sometimes it just needs some time to get the stuff working. It's a pretty complex topic to be honest :)

[Bludator]

I am not receiving NotificationReceived event when the notification is shown and the app is running (i.e. notification with high importance). I this intended behavior?

[thomasgalliker]

This is not intended behavior.

[thomasgalliker]

It can have a number of reasons why NotificationReceived event is not fired. It's really hard to support the troubleshooting process if I have no additional context. I'd recommend you use the latest pre-release 3.2.8-pre which adds some fail safety in certain scenarios. Also, make sure your app uses Microsoft.Extensions.Logging as we write a lot of useful messages to ILogger.
One last hint: Try to get the sample app in this repo to work with your own GoogleService-Info.plist (iOS) resp. google-services.json (Android).

[Bludator]

You are to quick for me 😅. I have created issue for it now

[thomasgalliker]

Cool, let's discuss it there #127

[thomasgalliker]

Could this issue be related with #132?

[thomasgalliker]

There is a brand new pre-release 4.0.1-pre available which targets to solve this issue. Can you give it a try?