ChromeSafariBrowser single instance with callbacks

[zanelladev]

• I have read the Getting Started section
• I have already searched for the same problem

Environment

Technology	Version
Flutter version	3.13.6
Plugin version
Android version	11
iOS version
macOS version
Xcode version
Google Chrome version

Device information: Pixel 3a

Description

In ChromeSafariBrowser, when I use isSingleInstance: true, in Chrome, it works normally, but it doesn't close my tabs after the callback, causing several browser screens to remain open. If I use isSingleInstance: false, sometimes when I open a browser, and then open another one later, it doesn't overwrite the url, so it opens the link from the first browser. In FireFox, isSingleInstance: true, works perfectly.

Expected behavior:

Don't leave tabs open after the callback

Current behavior:

Tabs remain open after the callback

Steps to reproduce

1. Set isSingleInstance: true,
2. Open link with Chrome
3. Callback to your app
4. Tab still opened in the device

Other case is:

1. Set isSingleInstance: false,
2. Open link with Chrome or FireFox
3. Callback to your app
4. Open another link with Chrome or FireFox
5. Browser open the first link, not the second

Images

[github-actions]

👋 @zanelladev

NOTE: This comment is auto-generated.

Are you sure you have already searched for the same problem?

Some people open new issues but they didn't search for something similar or for the same issue. Please, search for it using the GitHub issue search box or on the official inappwebview.dev website, or, also, using Google, StackOverflow, etc. before posting a new one. You may already find an answer to your problem!

If this is really a new issue, then thank you for raising it. I will investigate it and get back to you as soon as possible. Please, make sure you have given me as much context as possible! Also, if you didn't already, post a code example that can replicate this issue.

In the meantime, you can already search for some possible solutions online! Because this plugin uses native WebView, you can search online for the same issue adding android WebView [MY ERROR HERE] or ios WKWebView [MY ERROR HERE] keywords.

Following these steps can save you, me, and other people a lot of time, thanks!

[zanelladev]

The problem is related to the use of android:launchMode="singleInstance" in AndroidManifest.xml along with isSingleInstance: false.

If I set android:launchMode="singleTop", I can use isSingleInstance: false for Chrome and isSingleInstance: true for FireFox and it will work perfectly.