WAI
Status Update
No update yet.
Comments
ra...@google.com
Information redacted by Android Beta Feedback.
ra...@google.com
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.
ra...@google.com
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:
Description
At present, the preliminary analysis shows that after flashing the GSI image,
the properties of ro.roduct.brand, ro.roduct.device,
ro.roduct.manufacturer, and ro.roduct.model have changed,
resulting in a mismatch with the ID Attestation bound when writing the key;
After locally crashing the following attributes and running a test,
it was found that the original CANNOT_ATTEST-IDS error was still reported
ro.product.device_for_attestation TB335FC
ro.product.name_for_attestation TB335FC
ro.product.model_for_attestation TB335FC
ro.product.odm.brand_for_attestation Lenovo
ro.product.manufacturer_for_attestation LENOVO
May I ask how to handle this fail item? Please help guide me