Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS app crashes when exporting many requests #2227

Open
drzazga3009 opened this issue Jan 5, 2025 · 6 comments
Open

iOS app crashes when exporting many requests #2227

drzazga3009 opened this issue Jan 5, 2025 · 6 comments
Assignees
Labels
bug Something isn't working ✅ Done Ticket is addressed and fixed.

Comments

@drzazga3009
Copy link

Description

My use case is saving live video streams that don't provide replays. I capture data segments on mobile, then export the session to a file and import it in proxyman on Mac. From there I can export the stream segments and merge them into a single video. This works for shorter streams but is problematic for longer streams because the mobile app usually crashes on export. In the past it used to work after a few tries but this time I can't get the data exported. I could export an 80 minutes long stream, around 1.5 GB. This time it's only 1h long stream but the app always crashes. There are around 1900 responses, each 500KB.

Could be related to #1946 but I don't use airdrop. In fact, the app crashes before I'm able to choose the sharing method.

Steps to Reproduce

  1. Capture a lot of traffic i.e. several thousands requests, 1GB of data.
  2. Use share option for the whole domain to export to a file.
  3. The app crashes.

Current Behavior

Sharing captured traffic doesn't work for larger data sets.

Expected Behavior

Save correctly to a file in Files. Alternatively, allow iCloud sync to Mac (related to #2209 ?). Another alternative could be enabling File-Sharing, if I understand it correctly that would allow Mac/PC users to just copy the internal files of the mobile app in iTunes/Finder.

Environment

  • App version: Proxyman 2.21.1
  • OS version: iOS 18.1.1
@drzazga3009 drzazga3009 added the bug Something isn't working label Jan 5, 2025
@NghiaTranUIT
Copy link
Member

@drzazga3009 it's huge data, so it's out of memory when arching the data for sharing.

Can you work around this by adding certain domains to the Pin folder? Then sharing the Pin folder instead of all Domains? 🤔

@drzazga3009
Copy link
Author

Thank you for your response. I already tried to share only that one specific domain but, as suggested, I tried again using pin folder. This also crashes the app. Unfortunately, I can't select a range of request on mobile, which means I can only export hundreds of requests one by one.

Okay, so it's not a bug but a hardware limitation? If so, what do you think of my suggestions in "expected behavior"? Another thing that comes to mind is automatically splitting the export into smaller parts. From what I see, the exported file is just a zip with requests in separate files. The app could group the requests into packages of a specific size (let's say 100 MB max, not sure if appropriate) and export into multiple, smaller files.

@drzazga3009
Copy link
Author

@NghiaTranUIT are there any plans to change the export behaviour to make it more robust?

@NghiaTranUIT
Copy link
Member

@drzazga3009 can you use iMazing app to copy Proxyman's Document Folder and share it with me at [email protected]?

I'd like to reproduce on our end and fix it.

When zipping many small files into a big file, it can consume a lot of RAM -> iOS will kill the app. So I'm not sure your solution can fix it.

@drzazga3009
Copy link
Author

I just sent you a link to the extracted file on google drive. I hope it helps.

@NghiaTranUIT
Copy link
Member

Fixed with v2.22.1 on AppStore 👍

@NghiaTranUIT NghiaTranUIT self-assigned this Jan 13, 2025
@NghiaTranUIT NghiaTranUIT added the ✅ Done Ticket is addressed and fixed. label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ✅ Done Ticket is addressed and fixed.
Projects
None yet
Development

No branches or pull requests

2 participants