fix: remove forced multipart header to fix Android postForm/patchForm… #7243
+16
−4
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 a long-standing issue where axios.postForm, axios.putForm, and axios.patchForm fail on React Native Android with a Network Error.
The issue occurs because Axios forces a bare:
Content-Type: multipart/form-dataheader without a boundary.
React Native Android requires a boundary (e.g. boundary=----RNFormBoundaryABC123).
When Axios overrides the header, React Native cannot append the boundary, causing the request to be malformed and immediately rejected.
iOS is more permissive, so it does not fail.
What This PR Changes:-
iOS React Native (already worked)
Standard axios.post / axios.patch / axios.put (not using FormData helpers)
Technical Summary
Before (broken on Android):
headers: { 'Content-Type': 'multipart/form-data' }After (correct):
headers: isForm ? (config?.headers || {}) : {}This lets React Native generate:
Content-Type: multipart/form-data; boundary=----RNGeneratedBoundary123which Android accepts.
Result:-
Fixes
#6968