TargetPlatform.macOS is not yet supported by the flutter_inappwebview plugin

[shmehdi01]

I'm using flutter_inappwebview but it is showing TargetPlatform.macOS is not yet supported by the flutter_inappwebview plugin when i'm running on Chrome Web.

It is working fine on Android and Ios.

[github-actions]

👋 @shmehdi01

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!

[pichillilorenzo]

Well... you see that no? TargetPlatform.macOS is not yet supported by the flutter_inappwebview because, well, is not yet supported...

Where did you see that this plugin supports macOS??

For desktop support, follow #460

Instead, if you mean Web support, it won't be supported because there is no such thing in HTML, CSS, javascript.
In fact, it doesn't literally make any sense in that case.

[shmehdi01]

My Bad 👍

[Sunsiha]

@shmehdi01 how did u resolve this?

[jyr]

@shmehdi01 how did u resolve this?

I have the same issue 😄. I found this, I think inappwebview 6 works, I going try

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.