Assigned
Status Update
No update yet.
Comments
vi...@google.com
Information redacted by Android Beta Feedback.
bi...@gmail.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.
bi...@gmail.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:
tw...@google.com
I have had this error on the beta since December, updated to the stable now and it still like this.
bi...@gmail.com
Thanks! If so, it will be supported in android-15 on April?
Description
./cts-tradefed
./run cts -m CtsSecurityHostTestCases -t android.security.cts.SELinuxNeverallowRulesTestVendor#testNeverallowRules[ver=202404;idx=291]
100% chance.
=========================================
Background:
On evk_95, libcamera is used, and the IPA will run in isolation mode if it's signature verified fail.
Related code to run isolation need to set some sepolicy. One is below.
allow hal_camera_default hal_camera_default:user_namespace { create };
=========================================
CTS cases under CtsSecurityHostTestCases will use “secilc” tool to compile the sepolicy on device at runtime. The problematic commit adds below selinux rule but it can’t be recognized by the “secilc” tool:
allow hal_camera_default hal_camera_default:user_namespace { create };
The “secilc” tool will return below error:
Failed to resolve AST
Failed to compile cildb: -2
And the error code “-2” has the definition like below:
#define SEPOL_ENOTSUP (-2) /* feature not supported in module language */
=========================================
Maybe need refine the tool to support "user_namespace" better? Or there are other ways to fix/avoid the issue.
Attach the CTS log/result and bug report.
Thanks!