Assigned
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Information redacted by Android Beta Feedback.
pa...@intel.com <pa...@intel.com> #3
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
vi...@google.com <vi...@google.com> #4
HI,
Attached is a screenshot of the error message.
I get this message everytime I try to tap and pay.
I am guessing that it's because you have released the stable Android 15
QPR2 and I am stuck on the beta verson.
On Thu, 6 Mar 2025 at 09:22, <buganizer-system@google.com> wrote:
Attached is a screenshot of the error message.
I get this message everytime I try to tap and pay.
I am guessing that it's because you have released the stable Android 15
QPR2 and I am stuck on the beta verson.
On Thu, 6 Mar 2025 at 09:22, <buganizer-system@google.com> wrote:
vi...@google.com <vi...@google.com> #5 Restricted+
Restricted+
Comment has been deleted.
vi...@google.com <vi...@google.com> #6
/tmp/xts-root-dir-7cad8482-0270-4505-ad5c-98f7aec0198a/android-cts/testcases/CtsLibcoreTestCases/x86_64/xxx.apk
run cts -m CtsLibcoreTestCases -a arm64-v8a
Even though you are trying to test in arm64-v8a
, but it's using a x86_64
APK. Would the device or test being misconfigured locally?
pa...@intel.com <pa...@intel.com> #7
In fact, we can support translating arm64-v8a to x84_64 using Houdini, so we support running arm64-v8a case on sdk_phone64_x86_64.
and similar problems issue 365913977 occurred on Android 15 before, now it can run successful on emulator.
and similar problems
vi...@google.com <vi...@google.com> #8
Can you provide the value of the following system properties on your device?
adb shell getprop ro.product.cpu.abilist
pa...@intel.com <pa...@intel.com> #9
OK, it return "x86_64,arm64-v8a,x86,armeabi-v7a,armeabi"
vi...@google.com <vi...@google.com> #10
Can you check if your test APKs contain the native libraries for arm64-v8a?
pa...@intel.com <pa...@intel.com> #11
Comment has been deleted.
pa...@intel.com <pa...@intel.com> #12
yes, It contains the native libraries for arm64-v8a and armeabi-v7a
Description
They are:
CtsLibcoreTestCases
CtsNetTestCasesMaxTargetSdk31
CtsAdServicesPermissionsAppOptOutEndToEndTests
CtsAdServicesPermissionsValidEndToEndTests
steps for reproduce:
run cts -m CtsLibcoreTestCases -a arm64-v8a
run cts -m CtsNetTestCasesMaxTargetSdk31 -a arm64-v8a
run cts -m CtsAdServicesPermissionsAppOptOutEndToEndTests -a arm64-v8a
run cts -m CtsAdServicesPermissionsValidEndToEndTests -a arm64-v8a
similar error logs:
com.android.tradefed.targetprep.TargetSetupError[APK_INSTALLATION_FAILED|520001|DEPENDENCY_ISSUE]: Failed to install xxxx with [/tmp/xts-root-dir-7cad8482-0270-4505-ad5c-98f7aec0198a/android-cts/testcases/CtsLibcoreTestCases/x86_64/xxx.apk] on emulator-5554. Reason: 'INSTALL_FAILED_NO_MATCHING_ABIS: INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113'