Navigating from notification click results in stacked screens (iOS and android)

[Manuelkpatsu]

Hi,

I'm encountering an issue with the latest version of the package. When a notification is tapped to navigate to a screen, the navigation is triggered multiple times.

As a result, the target screen is pushed onto the stack several times, and closing it requires multiple pops. This appears to be caused by OneSignal.Notifications.addClickListener firing the callback more than once.

Is anyone else experiencing this? If there's a reliable solution or workaround, I’d really appreciate your help.

Thanks!

[nan-li]

Hi @Manuelkpatsu, thanks for reaching out.

The navigation is happening within the notification click listener correct? The target screen is pushed onto the stack the same number of times as the click listener is fired?

Are you using hot reload? Which may call your addClickListener multiple times causing multiple click listeners to be added.

[Manuelkpatsu]

Hi @Manuelkpatsu, thanks for reaching out.

The navigation is happening within the notification click listener correct? The target screen is pushed onto the stack the same number of times as the click listener is fired?

Are you using hot reload? Which may call your addClickListener multiple times causing multiple click listeners to be added.

@nan-li yes, the navigation is happening within the click listener and yes, the target screen is pushed onto the stack the same number of times as the click listener is fired.

We are experiencing it in production. This was reported by the users and my investigations pointed me out to this behaviour. It wasn't always like this when we were using OneSignal.shared.setNotificationOpenedHandler but after upgrading the package to the latest version this year, that was when we started experiencing this. This has nothing to do with hot reload.

[nan-li]

@Manuelkpatsu I think your click listener is being added multiple times.

Since you are not using hot reload, can you share more information about how you are initializing the SDK and where you are calling OneSignal.Notifications.addClickListener?

I will investigate how it can be added or triggered multiple times.

[Manuelkpatsu]

@Manuelkpatsu I think your click listener is being added multiple times.

Since you are not using hot reload, can you share more information about how you are initializing the SDK and where you are calling OneSignal.Notifications.addClickListener?

I will investigate how it can be added or triggered multiple times.

@nan-li i was able to figure it out, the issue was due to where I was calling OneSignal.Notifications.addClickListener. I’ll go ahead and close the comment.

Thanks again for taking the time to help out!

[Topiya]

@Manuelkpatsu
Can you please let me know how did you fix this issue? I am also facing the same issue.