Skip to content
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

[bug] Job not created when loading script using import command #365

Open
Techbrunch opened this issue Apr 19, 2020 · 6 comments · May be fixed by #705
Open

[bug] Job not created when loading script using import command #365

Techbrunch opened this issue Apr 19, 2020 · 6 comments · May be fixed by #705

Comments

@Techbrunch
Copy link
Contributor

According to the documentation in the wiki:

Frida scripts loaded with the import command are also run as jobs automatically

Describe the bug

When loading a script with the import command, the script is successfully loaded but no jobs is created.

To Reproduce

  1. import test.js
  2. jobs list

Expected behavior

The job should be listed when running jobs list

Environment:

  • Frida Version 12.8.19
  • Objection Version v1.9.1
@Techbrunch Techbrunch added the freshissue Default label for new, untriaged issues. label Apr 19, 2020
@leonjza leonjza added documentation and removed freshissue Default label for new, untriaged issues. labels Apr 19, 2020
@leonjza
Copy link
Member

leonjza commented Apr 19, 2020

Ah right, I need to update the documentation. This is actually not the case anymore.

@Techbrunch
Copy link
Contributor Author

@leonjza Maybe consider moving the documentation out of the wiki since we can't really make pull requests to update the documentation

@root-intruder
Copy link
Contributor

does that mean, that the whole "Jobs" functionallity is not working? what's the reason behind it? was it intentionally nuked/ is it a bug?

@leonjza
Copy link
Member

leonjza commented Aug 3, 2020

Jobs still exist, we just don't glue whatever your custom script does to a job you can see in jobs list anymore. I forget the history on how it worked, but what I think should happen now (as in the code should be written for it) is that we should have something like jobs imports commands to keep track of and work with custom scripts that were injected.

@dgrivera
Copy link

is there a update about this? been waiting for it, thank you good sir

@IPMegladon
Copy link
Collaborator

Should be fixed in #705

@IPMegladon IPMegladon linked a pull request Jan 16, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants