Leon Jacobs
Leon Jacobs
Can you connect the vanilla frida client?
Try and use the full bundle identifier of your app instead of `Gadget`.
Right, you will have to debug this locally. Could be some security feature of the application preventing Frida from working.
We've run into this internally as well. For now, downgrading frida-server (or gadget by patching with the --gadget-version flag) and local `frida` python package to latest 14x for now should...
Right. Only other thing I can suggest now is to check your local frida package version. ``` ❯ pip3 freeze | grep -i frida frida==14.2.18 ```
This error is definitely a little misleading, and hard to figure out whats happening. In short, the `device_type` property is set in the [`get_device_info()`](https://github.com/sensepost/objection/blob/1.11.0/objection/commands/device.py#L9) call, which in turn calls [`runtime`](https://github.com/sensepost/objection/blob/1.11.0/agent/src/generic/environment.ts#L21-L26)...
Been pondering this one a long time now, and I think its time to get rid of the preflight logic entirely. For 3.x I think this should be a key...
Implemented [here](https://github.com/sensepost/gowitness/commit/1503c5b8b0285f25d03f4893ae2c92674451bacc), making it more versatile for more more than one response code.
Thank you. While you showing some stats, Im super curious about top 0 src-ip :P (masking the actual ips ofc). As for the problem at hand, a change will be...
@MilosRasic sure, if only such a thing existed. @Regner thanks :)