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

Hooking upon iOS app launching takes too long and killed by springboard #103

Closed
guitarfeng opened this Issue Jan 30, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@guitarfeng

guitarfeng commented Jan 30, 2016

Thank all the maintainers for this amazing project.

I have one issue about hooking upon iOS app launching (the target logic only triggers during app launching). I use the following command to do this:
frida-trace -U -f $BUNDLE_ID -m "-[xxx_class xxx_method]"
The app can be launched by frida and hangs in the first page during searching for the specific method.
Unfortunately, after a while, the app is killed by the Springboard due to the following error:
": Forcing crash report of <FBApplicationProcess: 0x15ed82230; xxx; pid: xxx> (reason: 1, description: $BUNDLEID failed to launch in time)"

I think it's a common scenario using frida to hook app launching related logics. Is there any trick I can use to avoid this issue? Any response would be helpful. Thanks.

@oleavr

This comment has been minimized.

Contributor

oleavr commented Jan 31, 2016

Hi and thanks for reporting,

Which iOS version is this on? There is a known issue where we don't yet do anything about that built-in timeout, so if the instrumentation logic takes too long you will run into this issue. However, I have been wanting to optimize the Objective-C method resolving, as it would be nice to reduce that delay anyway, and it means we can figure out how to disable the timeout at a later point.

Cheers

@oleavr

This comment has been minimized.

Contributor

oleavr commented Feb 2, 2016

This issue should now be fixed in 6.2.1.

@oleavr oleavr closed this Feb 2, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment