Fixed
Status Update
Comments
uv...@amd.com <uv...@amd.com> #2
Information redacted by Android Beta Feedback.
vi...@google.com <vi...@google.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:
Description
run cts -m CtsAppWidgetTestCases -t android.appwidget.cts.RequestPinAppWidgetTest#testPinWidget_launcher1
As part of the testcase, launcher1 is set and check for the Intent android.content.pm.action.CONFIRM_PIN_APPWIDGET for the current user.
requestPinAppWidget() returns fails and the BlockingBroadcastReceiver await fails.
[WHY]
When the launcher android.appwidget.cts.packages.launcher1/android.appwidget.cts.packages.Launcher is set via the below command,
"cmd package set-home-activity" if "--user " field is not provided, it will assume to be SYSTEM_USER as per the below code,
When the requestPinAppWidget() API is invoked, it check for the current user default launcher which is User-10. So the current user is not aware of the launcher1 and the intent to launch, so the requestPinAppWidget() returns FALSE.
Intent:
Intent { act=android.content.pm.action.CONFIRM_PIN_APPWIDGET pkg=com.android.car.carlauncher } launcherUserId: 10
Code Snippet:
[HOW]
Send the userId while setting the launcher.