You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm currently using Flipper Desktop 0.176.1 on a Macbook Air M1 8gb 256gb and I noticed since a long time that when trying to debug API calls that contain files, the app freezes for a long time, sometimes more than 5 minutes, because it seems to be parsing the binaries into a text, so if we look at the Req/Res body (depends on which side is transferring the file) we usually get thousands+ of lines of parsed files into text.
To Reproduce
Simply upload any file with multipart/form-data ContentType and you will see what I'm talking about.
In the chrome developers tools we directly see [Binary] instead of the parsed file, I think this could be the correct approach.
Environment
RN 0.66.4
Flipper Desktop: 0.176.1 (this problem is also present on previous versions)
Android version: 12
iOS version: 16
The text was updated successfully, but these errors were encountered:
Yeap, Use Flipper from ~0.160 to current version 0.203 and always app freeze on upload file requests. Unpossible debug upload requests on REST API, GraphQL. RN all version from ~0.60 to 0.72
🐛 Bug Report
Hi, I'm currently using Flipper Desktop 0.176.1 on a Macbook Air M1 8gb 256gb and I noticed since a long time that when trying to debug API calls that contain files, the app freezes for a long time, sometimes more than 5 minutes, because it seems to be parsing the binaries into a text, so if we look at the Req/Res body (depends on which side is transferring the file) we usually get thousands+ of lines of parsed files into text.
To Reproduce
Simply upload any file with multipart/form-data ContentType and you will see what I'm talking about.
In the chrome developers tools we directly see [Binary] instead of the parsed file, I think this could be the correct approach.
Environment
RN 0.66.4
Flipper Desktop: 0.176.1 (this problem is also present on previous versions)
Android version: 12
iOS version: 16
The text was updated successfully, but these errors were encountered: