Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR implement correctly the reconnect command inside Objection.
The Problem:
Mobile testing often involves app crashes (security protections, memory pressure) or USB timeouts. Currently, when the Frida session terminates, the user must exit Objection and restart the entire process, losing context and history.
The Solution:
The reconnect command allows for a "soft-restart" within the same REPL session. It clears the stale agent state and re-invokes the core get_agent() logic to re-attach to the target bundle.
Usage Notes:
Ensure the target application is open and active on the device before running reconnect.
Tested on iOS 16.4.1 .
Uses core Objection logic, making it compatible with both iOS and Android workflows.
Handles both hard crashes (app killed) and soft crashes (session timeout).