-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Frida broken on Android 12 (emulators only?), and the error told me to file a bug report. #1917
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
Comments
Update: I do not get this behavior on a physical Android 12 device, so this may affect either only emulators or only x64. |
same issue on an android 12 emulator |
It looks like |
Oops. Hadn't seen this issue when I posted mine. Isn't the issue with the new multi arch support of Android 11+? |
+1 having the same issue |
I have the same issue with an Android 12 x86_64 AVD emulator with the latest
|
this AOSP CL ? How should we fix it ? |
Hi, when trying to run frida on an Android 12 (API 31) emulator, I get the following output:
Here's that output after formatting, for convenience:
This is all on the latest version (15.1.12), running on x86_64. The emulator in question was freshly installed (multiple times), wiped, cold booted, etc. The avdmanager string used to create the AVD is
system-images;android-31;default;x86_64
.I have also updated my pip packages, as seen here:
$ pip freeze | grep frida frida==15.1.12 frida-tools==10.4.1
And here are some additional tests (with frida-server still running after printing the original error):
Even though I could not attach to system_server by name, I can attach by PID (although it takes several seconds).
I get similar issues when running via the python bindings, which is what led me to this. Please let me know if I can help test anything else.
The text was updated successfully, but these errors were encountered: