Process terminated when file explorer opens

[igolaizola]

Hi!
I'm able to intercept requests using the settings in this project and the following command:

frida -U \
    -l ./config.js \
    -l ./native-connect-hook.js \
    -l ./native-tls-hook.js \
    -l ./android/android-proxy-override.js \
    -l ./android/android-system-certificate-injection.js \
    -l ./android/android-certificate-unpinning.js \
    -l ./android/android-certificate-unpinning-fallback.js \
    -l ./android/android-disable-root-detection.js \
    -l ./android/android-disable-flutter-certificate-pinning.js \
    -f $PACKAGE_ID

However, when the app's UI requires opening the file explorer to select a file, the process terminates with the message "Process terminated."

Is there any workaround to keep the process alive when the app switches to the file explorer?
Thanks!

[pimterry]

Hmm, I haven't seen this myself. Can you try removing scripts one by one, until you work out which script causes this? All scripts can be used independently, except config.js (all other scripts depend on this) and ./android/android-certificate-unpinning-fallback.js (which depends on ./android/android-certificate-unpinning.js).

[igolaizola]

I solved the issue by launching Frida first with -W and then launching the app.

frida -U \
    -l ./config.js \
    -l ./native-connect-hook.js \
    -l ./native-tls-hook.js \
    -l ./android/android-proxy-override.js \
    -l ./android/android-system-certificate-injection.js \
    -l ./android/android-certificate-unpinning.js \
    -l ./android/android-certificate-unpinning-fallback.js \
    -l ./android/android-disable-root-detection.js \
    -l ./android/android-disable-flutter-certificate-pinning.js \
    -W $PACKAGE_ID

[pimterry]

Huh, interesting. There must be something related to initialization here then that's causing issues (I think -W will run the scripts fractionally later, effectively attaching to the running app, rather than injecting at the very very start before anything can get involved). Glad it's working for you now though.

If you do run into more issues, please try hunting down the specific script that causes them, as above. If you have any specific easy-to-reproduce examples that you can share where this happens, that would also be helpful so that others can test and investigate this in future.