Repeated Branch requests after stopping and starting app

[sgstry]

After processing the branch link result when a user clicks a link, stopping and starting the app sends a subsequent branch request for the same exact link. However, the second branch open request doesn't contain the external_intent_uri, external_intent_extra, or link_identifier attributes in the POST request. Yet still, Branch is giving back referring params with +clicked_branch_link = true.
This causes the application to process the same link twice even though it was only opened once. Any tips would be welcome, thank you!

This problem occurs on all versions from 5.0.0 - 5.1.1. Haven't tried any earlier versions.

[aungkpaing]

+1, facing the same issue, can confirm with just bare minimal setup that it's trigger on background => foreground

[damiafuentes]

+1. Any ideas?

[tommyjackson]

+1, still seeing this issue on 5.2.2

[jf-branch]

Hi all,

Android App Link can see that deep linking happens again when end-users open the app organically within the Deep Linking Duration Window right after the app is opened by deep linking because of Android App Link double deep linking issue.

Android App Link double deep linking is a known issue and has been for a while now. (We raised a Google support ticket for this a while back: Issue-978675). This bug occurs when Branch Links are Android App Linked from the Chrome Browser, Chrome triggers a client-side click before Android Applinking the user into the App.

[tommyjackson]

@jf-branch thanks for the update - I starred the issue you linked! Is there anything else I can do to help raise visibility on Google's side, like create a newer issue on the Google Issue Tracker?

[tommyjackson]

@jf-branch I commented on the issue you linked and got a response here, and it looks like Google doesn't have anything they can do on their end. Does that render this as an unfixable bug then? Or are there other options to explore?

[VvoidVano]

Hey @jf-branch does that mean it can be fixed temporarily by changing something in Deep Linking Duration Window? If so, any suggestions? Thanks in advance.

[nqtsparda]

Have anyone came up with any workaround ?