You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@gsakakihara
Hey there,
I don't want to open a new ticket for this, since my problem is kind of coming from the same source, the
`FcmLifecycleCallbacks`.
Just to add, the callbacks do not only not recognize `onNewIntent` calls, but they also do not recognize
if the same intent was already used for logging.
Use Case Example:
1. LaunchActivity (which is called by fcm notification with data in Intent)
2. SomeOtherActivity which is called from LaunchActivity
If the LaunchActivity blindly forwards it's Intent data to the "SomeOtherActivity" for any reasons,
the `notification_open` event will be tracked twice, because the `FcmLifecycleCallbacks` is invoked
two times.
This can easily be avoided, but was not easy to find. So this is more an additional info for you.
Maybe it's a good idea to check if the intent from `onCreate` is coming from an activity
with `category.LAUNCHER` Intent-filter first, before pushing the fcm event. But thats not
to me to decide.
Have a great day,
Cheers
The text was updated successfully, but these errors were encountered:
Hey @SteveBurkert, thank you for reaching out. I was able to reproduce the issue you reported. I'll notify our engineers about this and also the possible fix you suggested. Thank you for that. I'll get back to you once I hear from them.
- Changed to use the message ID when checking for duplicate notification_open logging instead of the Activity's Intent. This should avoid logging again when an app starts another activity using a copy of the notification's intent (#6091).
…6112)
- Changed to use the message ID when checking for duplicate
notification_open logging instead of the Activity's Intent. This should
avoid logging again when an app starts another activity using a copy of
the notification's intent
(#6091).
Issue is created on behalf of the Developer.
Originally posted by @SteveBurkert in #3799 (comment)
The text was updated successfully, but these errors were encountered: