React Native Android中axios的FormData处理及onUploadProgress相关问题是否已修复？

Great question—this is a frustrating issue that many React Native developers hit when using axios for multipart uploads on Android. Here's what you need to know:

• The root of the bug: As you pointed out, older axios versions mishandled FormData on React Native Android by setting an incorrect Content-Type header (missing the critical boundary parameter required for multipart requests). This broke uploads entirely, which is why so many of us switched to native fetch or raw XMLHttpRequest.

• Fix update: Good news! This bug has been resolved in axios v1.0.0 and all subsequent versions. The axios team reworked how FormData is processed in React Native environments, aligning it with the native XMLHttpRequest behavior you're manually using now. The library will automatically generate and attach the correct boundary to the Content-Type header, making multipart uploads work reliably again.

• What this means for your workflow: If you update axios to a recent v1.x release, you can safely go back to using axios's onUploadProgress with FormData on Android. The underlying logic now matches the manual XMLHttpRequest approach you're relying on, so you get the convenience of axios's API (like interceptors, request cancellation, etc.) while retaining progress tracking functionality.

• Quick way to confirm: After updating, inspect your request headers—you should see a Content-Type value like multipart/form-data; boundary=----WebKitFormBoundaryXXXX (the boundary string will vary). If that's present, the bug is fixed and your uploads should work as expected.

If you're happy with your current raw XMLHttpRequest setup, there's no pressure to switch back—but it's reassuring to know the axios option is now stable for this use case.

内容的提问来源于stack exchange，提问作者ayaz sohail