fix(http): properly write form-urlencoded data on android request body #7001
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ItsChaceD
requested review from
markemer,
jcesarmobile,
theproducer,
IT-MikeS and
giralte-ionic
IT-MikeS
approved these changes
Nov 3, 2023
giralte-ionic
approved these changes
Dec 8, 2023
theproducer
pushed a commit
that referenced
this pull request
Dec 14, 2023
#7001) Co-authored-by: Mark Anderson <mark@ionic.io> Co-authored-by: Dan Giralté <97970732+giralte-ionic@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the logic to write
x-www-form-urlencodeddata on Android http requests when it is sent as a serializable JSON, instead of a string.Special thanks to @nickredding
closes #6792