Status Update
Comments
yo...@linaro.org <yo...@linaro.org> #2
Information redacted by Android Beta Feedback.
yo...@linaro.org <yo...@linaro.org> #3
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.
ra...@google.com <ra...@google.com> #4
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:
li...@google.com <li...@google.com> #5
yo...@linaro.corp-partner.google.com <yo...@linaro.corp-partner.google.com> #6
Thanks for the information! and ENABLE_XTS_DYNAMIC_DOWNLOADER=false works.
Just I am not able to access the partner docs:(. and I was thinking to disable USE_ATS before, so want to confirm here again, is setting ENABLE_XTS_DYNAMIC_DOWNLOADER=false the proper solution here for cases where the prebuilt android-cts.zip/android-vts.zip is used? and does this work for all Android versions(like from Android11 to AOSP main), or it just needs to be done for specific Android versions?
li...@google.com <li...@google.com> #7
Yes, this will be true for all Android versions, currently only support 14 and 15, and for 12 and 13 it will be supported by the end of this year.
yo...@linaro.corp-partner.google.com <yo...@linaro.corp-partner.google.com> #8
Thanks for the confirmation! will set ENABLE_XTS_DYNAMIC_DOWNLOADER=false for all the Android versions on all side to workaround the issue reported here.
we...@oppo.corp-partner.google.com <we...@oppo.corp-partner.google.com> #9
Whether subsequent tools can optimize this problem, we hope that the test can be completed without adding too many instructions like this situation
Description
To be honest, I am not sure it should be reported here or should be one libcore related issue. I think it's more related the the CTS test framework, so report the issue here first. But please feel free to change it to the proper component if necessary.
There are actually two type failures here, which I think are caused by the same root cause:
For details, please check the attached aosp-main-cts-libcore.zip file.
But these failures are not reported when running atest CtsLibcoreTestCases under the AOSP tree, or when running with export USE_ATS="false".
And btw, any document on the USE_ATS flag? it looks like the module being tested is not the one from the android-cts.zip package.