Thanks @neel3o115, and apologies on the wait. The diagnosis is right, Android's RN networking layer rejects bare multipart/form-data without a boundary, iOS doesn't, and the gap exists because RN is neither hasStandardBrowserEnv (axios deliberately excludes RN from that flag in resolveConfig) nor uses Node's form-data package. The placeholder header reaches the wire untouched on RN, and Android complains. Worth fixing.

Three asks before this can merge.

First, drop the toFormData.js changes. Function('return this')() is eval in a different shape — it trips CSP without unsafe-eval, which covers most production browsers behind a CSP and several RN setups. globalThis is universally available everywhere axios runs if global access were ever needed, but it isn't here. The precedence flip from PlatformFormData || FormData to runtimeFD || PlatformFormData is also a silent breakage on Node: Node 18+ has global FormData, so this picks the spec-compliant one over form-data, and any caller of axios.toFormData(obj) on Node who relied on .getHeaders() / .getLength() (documented form-data API) gets an object without them. And it isn't needed for the RN bug — RN bundlers resolve the browser field in package.json, so PlatformFormData already points at lib/platform/browser/classes/FormData.js, which is typeof FormData !== 'undefined' ? FormData : null. In RN, that's the runtime's FormData.

Second, tighten the Axios.js change. What you have:

  headers: isForm
    ? (config && config.headers ? config.headers : {})
    : {},

config.headers is already merged in by mergeConfig(config || {}, …) — the second argument is the overlay, not the source. Re-passing config.headers is either a no-op or runs the header merge strategy twice. The minimal version is headers: {}, or drop the headers key from the overlay entirely. Same effect: no placeholder is forced, anything in config.headers still flows through normally.

Third, add tests. At minimum: postForm (and put/patch) no longer emit the bare placeholder; Node form-data path still ends up with Content-Type: multipart/form-data; boundary=… via getHeaders(); spec-compliant FormData path through the http adapter still gets a boundary via formDataToStream.