Ads click is not redirecting the user to the correct screen when pressing back from chrome.

[Abhishek Pundir]

Hi Team,
I was having an issue in which when we click on the google ad it takes us to the chrome, but on pressing back from chrome, we are not landing on the same activity screen from where we navigated to the chrome in the first place.
Attaching the build as well as a recording for you to check, along with the demo project link.

Link: (https://github.com/pundirAbhishek/GoogleAdMobIssue/tree/main)

The main reason i found this to be happening is because i am using  android:documentLaunchMode="intoExisting"  in my project which i want to open multiple windows.
If i remove this configuration and then run teh exact workflow then it works as expected, so there must be some handling done in the admob sdk that is causing this issue and not compatable with android:documentLaunchMode="intoExisting"

[Abhishek Pundir]

Sharing the demo project and a demo for the issue : https://drive.google.com/drive/folders/1VUCrS2T_Yig6KrFvjczppQ9eCtRE6X-V?usp=drive_link

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

I will raise this issue with the wider team and will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-05-08 20:17:57Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01qWKu1:ref" (ADR-00304592)

[Mobile Ads SDK Forum Advisor]

Hi,

This is expected behavior, As defined here, this attribute is designed for apps that manage multiple "documents". It appears that this flag causes Android to flatten the back stack or re-evaluate the task hierarchy in a way that relates to the launched "document" (i.e., Chrome). The Android system possibly considers LauncherActivity as the perceived "parent" rather than MainActivity. MainActivity itself might be bypassed in the back stack transition after the document-mode-launched external activity (Chrome) finishes.

Therefore, this SHOULDN'T be considered either as an SDK issue.
 

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-06-03 23:27:13Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01qWKu1:ref" (ADR-00304592)