Leon Jacobs

I'm not sure where this is going wrong to be honest. Printing the raw values of the constants using this snippet, I get ```objc NSLog(@"kSecAttrAccessibleAlwaysThisDeviceOnly: %@", kSecAttrAccessibleAlwaysThisDeviceOnly); NSLog(@"kSecAttrAccessibleAlways : %@",...

This is useful thanks. Look like [`decodeAcl()`](com/sensepost/objection/blob/master/agent/src/ios/keychain.ts#L191) has a parsing issue here.

I think the spawning code could use some love. Happy to accept a PR for this. For reference, the relevant logic lives [here](https://github.com/sensepost/objection/blob/1.10.1/objection/utils/agent.py).

Yeah there were changes to how things spawn in more recent versions of Frida where it supports injecting Frida in a debuggable app (in a jailed env). The launcher/spawning logic...

Sorry, I am not sure what the question is here.

Hey! So the early instrumentation in objection is at fault here, and not the way you had to patch the agent in. Launching objection and then running the `import` command...

When you patch an app, the launchable activity gets a `loadLibrary` call (unless you specify another class to target) in its constructor. After you install the patched app on your...

Gotcha. So I think there could be a few reasons and it would definitely need some debugging. I would consider: - Is objection patching the right class (the default is...

Patching should be ok even if the app is obfuscated. Last thing I can suggest is to try patch the class defined in the app manifests `app:name` key in the...

> I'm not sure if this fault is Frida or Objection. This looks like objections fault for not getting the right PID to resume the app when you provide a...