-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ANDROID] - Notifications do not trigger onForegroundEvent #530
Comments
Hi @LcsGrz, thanks for reaching out. Can you test extending your Firebase service to the Iterable service so it can forward |
Hii, thank you very much for your answer, I was on vacation so I just saw your message :), tomorrow morning I will try what you tell me and I will edit this message hugs! |
@jena-chakour
and then run |
Notifications do not trigger onForegroundEvent (Android)
I did several tests, I do not understand how to solve it.
In my project I am using
iterable, firebase messaging and notifee
.the question is that when a new notification arrives from iterable I receive it from firebase and it is shown automatically.
In android when I press that notification with the app open, nothing happens, no notifee event is executed where I can give an action in the code, the opposite happens in IOs, if the
onForegroundEvent
function of notifee is executed.How can I implement an onPress in android, or how can I solve the problem?
I don't know if this issue should go here or in another of the packages I mentioned.
I am going to show the versions of the libraries and how I implemented it.
the code looks too simple, it is worth noting that when I receive an event from firebase and the notification is iterable I do not show it a second time with notifee
EDIT 1:
to explain a little bit about the execution flow
I was testing and the difference I can find between this notification and the one I launch from notifee is the channelID, which is the firebase default, although I don't think it has any relevance
fcm_fallback_notification_channel
The text was updated successfully, but these errors were encountered: