-
Notifications
You must be signed in to change notification settings - Fork 265
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
Unable to intercept function #22
Comments
Just tested on another device(Redmi note 3), it worked fine now. |
Glad it worked on another device. What was the device you were having the issues with first time? |
It's Pixel 2 and the OS version is 8.1.0 |
In my case, rebooting the device and rerunning |
I also met this problem and tried all the methods except changing my phone(oppo R11). But it didn't work, any suggestions? |
What version of Frida are you running with? Can you try again with Frida 16? |
I had this problem too, using the latest version: |
After running "jnitrace - l xxx. so xx. xxx. com" using frida16.2.1 and jnistrac 3.3.1, the app cannot start and the following error is reported
7727 ms [+] JNIEnv->ExceptionCheck 7727 ms ------------------------Backtrace------------------------
7735 ms [+] JNIEnv->NewStringUTF 7735 ms ------------------------Backtrace------------------------ ERROR: {'type': 'error', 'description': 'Error: access violation accessing 0x4', 'stack': 'Error: access violation accessing 0x4\n at (node_modules/jnitrace-engine/dist/jni/ 7743 ms ------------------------Backtrace------------------------ ERROR: {'type': 'error', 'description': 'Error: access violation accessing 0x4', 'stack': 'Error: access violation accessing 0x4\n at (node_modules/jnitrace-engine/dist/jni/ ERROR: {'type': 'error', 'description': 'Error: access violation accessing 0x4', 'stack': 'Error: access violation accessing 0x4\n at (node_modules/jnitrace-engine/dist/jni/jni_env_interceptor.js:159)', 'fileName': 'n |
Hi, I got an error when using
jnitrace
:And at the same time, the app crashed,
Please help me to resolve it, thanks.
The text was updated successfully, but these errors were encountered: