We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From Marijn at Traverse Research:
It looks like the NDK switched to Python 3 in r25, but one of the scripts still references unicode and fails on ndk-gdb on Windows. Replacing this with str solves it for me: https://cs.android.com/android/platform/superproject/+/master:development/python-packages/adb/device.py;l=163;drc=e955f07799e7440499afccd806e621827b99c9bd
r25
No response
Windows
all?
armeabi-v7a, arm64-v8a, x86, x86_64
Other (specify below)
n/a
The text was updated successfully, but these errors were encountered:
Fwiw the -f flag resulting in a type error is a separate issue.
-f
Sorry, something went wrong.
No branches or pull requests
Description
From Marijn at Traverse Research:
It looks like the NDK switched to Python 3 in r25, but one of the scripts still references unicode and fails on ndk-gdb on Windows. Replacing this with str solves it for me:
https://cs.android.com/android/platform/superproject/+/master:development/python-packages/adb/device.py;l=163;drc=e955f07799e7440499afccd806e621827b99c9bd
Affected versions
r25
Canary version
No response
Host OS
Windows
Host OS version
all?
Affected ABIs
armeabi-v7a, arm64-v8a, x86, x86_64
Build system
Other (specify below)
Other build system
No response
minSdkVersion
n/a
Device API level
No response
The text was updated successfully, but these errors were encountered: