Can't access a httpOnly Cookies using the CookieManager

[escamoteur]

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

Environment

Technology	Version
Flutter version	3.16.5
Plugin version	6.0.0
Android version	14
iOS version
macOS version
Xcode version
Google Chrome version

Device information: Pixel 7

Description

We have to handle Cloud Flare User Challenges that need to be shown in a WebView (in this case I used the WCInAppBrowser which works fine so far. unfortuantely the way the Cloudflare challenge works is that is stores a HttpOnly cookie on success which I need so that I can pass it with my API requests after the challenge suceeded.

I tried to list the existing cookies but the one from cloudflare that I can see in our webapp is not returned when I try:

            await browser.openData(
              data: response.body,
              settings: InAppBrowserClassSettings(
                webViewSettings: InAppWebViewSettings(
                  javaScriptEnabled: true,
                ),
              ),
              baseUrl: webUri,
            );
            await browser.exitCompleter.future;

            final cookies = await CookieManager.instance().getCookies(
                url: WebUri('https://mysite.com/'),
                webViewController: browser.webViewController);

Other cookies are sucessfully returned

Is there another way to intercept when the page creates the cookie?

[github-actions]

👋 @escamoteur

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!

[escamoteur]

Yep, I think I have tried almost everything and also did a lot of research

[pichillilorenzo]

Maybe the cookie is using another domain.
Open the WebView chrome inspector and check what domain is using the cookie you want to access.

[escamoteur]

Hi, How do I open the web view chrome inspector? Cheers Thomas Am 24. Jan. 2024, 23:03 +0100 schrieb Lorenzo Pichilli ***@***.***>:

…

Maybe the cookie is using another domain. Open the WebView chrome inspector and check what domain is using the cookie you want to access. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[pichillilorenzo]

As already written in the official website docs here: https://inappwebview.dev/docs/debugging-webviews#inspect-android-webviews:

On Android, in order to enable/disable debugging WebViews using chrome:https://inspect/#devices on Chrome, you should use the InAppWebViewController.setWebContentsDebuggingEnabled(bool debuggingEnabled) static method.

[escamoteur]

Thanks, will look into it Am 24. Jan. 2024, 23:08 +0100 schrieb Lorenzo Pichilli ***@***.***>:

…

As already written in the official website docs here: https://inappwebview.dev/docs/debugging-webviews#inspect-android-webviews: > On Android, in order to enable/disable debugging WebViews using chrome:https://inspect/#devices on Chrome, you should use the InAppWebViewController.setWebContentsDebuggingEnabled(bool debuggingEnabled) static method. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[escamoteur]

OK, it turned out that the inapp browser seems not to create cookies when using the browser.openData method. when use the openURLRequest method it works