onDeepLinking callback not invoked when app on foreground

[dalapenko]

When app on foreground and use intent with AppsFlyer link - onDeepLinking will not be invoked and intent didn't work until app will not be minimize and restore to foreground. That behaviour reproduced on AppsFlyer sample https://github.com/AppsFlyerSDK/appsflyer-onelink-android-sample-apps . If use similar intent when app is minimized or closed - it's work as expected.

How to reproduce:

• Open app with integrated AppsFlyer
• Invoke intent with AppsFlyer link, for example: adb shell 'am start -a android.intent.action.VIEW -d "https://onelink-basic-app.onelink.me/H5hv/5bq1c3v2" com.appsflyer.onelink.appsflyeronelinkbasicapp'
• If after invoked intent minimize app and return on foreground - intent will be handled by AppsFlyer SDK correct automatically

Actual behaviour:

• Intent not work, screen with deep-link information is not opened

Expected behaviour:

• • Intent work, screen with deep-link information is opened, like when call it with closed or minimized app

Potentially simmilar issues:
#74
#59

[github-actions]

👋 Hi @dalapenko and Thank you for reaching out to us.
In order for us to provide optimal support, please submit a ticket to our support team at [email protected].
When submitting the ticket, please specify:

• ✅ your AppsFlyer sign-up (account) email
• ✅ app ID
• ✅ production steps
• ✅ logs
• ✅ code snippets
• ✅ and any additional relevant information.

[dalapenko]

Quick reason: "Not a bug. By design"

Response from support:

In AppsFlyer, re-engagement measurement via DeepLink/ Push Notification only happens when the app is launched by clicking on a DeepLink URL/push notification when the app is not in an active state.
However, in your case, the app is already active in the foreground, which doesn’t support a re-engagement flow. Therefore, onDeeplinking callback is not consuming and provides the response as per design.

In case you’d like to receive the callback with the OneLink resolved Deeplink data in the foreground state, you can manually trigger the method using performOnDeepLinking . Details for this are provided [here]. Please review the document carefully and note that this workaround requires thorough testing on your end to ensure it works as expected for the foreground state as per your requirement.