Missing body field in URLRequest toMap method

[Miiha]

• I have read the Get Started - Installation section
• I have read and done the Get Started - Setup Android section
• I have read and done the Get Started - Setup iOS section
• I have already searched for the same problem

Environment

Technology	Version
Flutter version	2.5.1
Plugin version	v5.3.2
Android version	-
iOS version	15.0
Xcode version	13.0

Device information:

Description

I noticed that the URLRequest.toMap method is missing the field "body".
The counterpart URLRequest.fromMap already handles the "body" field.

Expected behavior:
URLRequest.toMap includes the requests body.

Current behavior:
URLRequest.toMap does not include the requests body.

Steps to reproduce

1. Open a form which submits by sending a POST request.
2. Override the shouldOverrideUrlLoading handler and see that navigationAction.request.body is null.

[github-actions]

👋 @Miiha

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!

[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.