-
Notifications
You must be signed in to change notification settings - Fork 224
FAQ
This project uses the latest ECMAScript feature in server side. You need node v7.10.1 at least, but v8.x and above is recommended.
Because of the package size. That's all.
Make sure you have frida.re successfully installed. Also, check if the version on of frida on device matches. Frida offers both 32bit and 64bit version, wrong architecture will not work.
Users from China mainland may encounter network problem. Try npm mirrors like cnpm. But some prebuilt packages may still need to be downloaded from GitHub, a reliable proxy would help.
中国内地使用 npm 可能会遇到网络问题。请尝试使用国内镜像加速安装
Besides, after updating source with git pull
, or having nodejs engine upgraded, you may need to remove node_modules
directory and re-run npm install
.
The app you're trying to attach has multiple processes, and frida couldn't decide which one to inject. You can try terminate the app via device gesture.
https://github.com/chaitin/passionfruit/issues/39
The file browser is based on process injection (instead of ssh), so it can't access locations outside the sandbox or protected by system. Since iOS 11, Library/Caches/Snapshots/
is no longer readable within app sandbox.
You may see one of the following messages:
- unexpectedly timed out while initializing suspended process
- spawn already in progress for the specified identifier
- Unexpected error while probing dyld of target process
This is due to frida failed to spawn the process(https://github.com/frida/frida-core/issues/193):
➜ ~ frida -U -f com.apple.mobileslideshow
____
/ _ | Frida 11.0.13 - A world-class dynamic instrumentation toolkit
| (_| |
> _ | Commands:
/_/ |_| help -> Displays the help system
. . . . object? -> Display information about 'object'
. . . . exit/quit -> Exit
. . . .
. . . . More info at http://www.frida.re/docs/home/
Failed to spawn: unexpectedly timed out while initializing suspended process
If you keep seeing this, you can manually start App on iDevice and bring it to front. If App is already running, Passionfruit will try to attach it instead of spawn a new instance.