Wear OS - Google assistance is not passing key through intent [340623304]

Assigned

Bug

[AOSP] assigned

Status Update

No update yet.

Description

de...@gmail.com

created issue #1

May 15, 2024 12:41PM

Hello Team,

We are attempting to integrate Google Assistance's voice command functionality with the Android Wear OS. Google assistance opens the app when we give a command, but we are unable to get Keyworld through the intent.

We have implemented this using App shortcut and capability.

shortcuts.xml

<?xml version="1.0" encoding="utf-8"?>

<capability android:name="actions.intent.OPEN_APP_FEATURE">
    <intent
        android:action="android.intent.action.VIEW"
        android:targetClass="com.harman.gearup.presentation.MainActivity"
        android:targetPackage="{package name}">
        <parameter
            android:name="feature.name"
            android:key="featureName" />
        <extra
            android:key="requiredForegroundActivity"
            android:value="{packagename}/{{packagename}}.presentation.MainActivity" />
    </intent>
    <intent
        android:targetClass="{packagename}.presentation.MainActivity"
        android:targetPackage="com.harman.gearup">
        <parameter
            android:name="feature.name"
            android:key="featureName" />
    </intent>
</capability>



<shortcut
    android:enabled="false"
    android:shortcutId="user_profile"
    android:shortcutShortLabel="@string/label_profile">
    <capability-binding android:key="actions.intent.OPEN_APP_FEATURE">
        <parameter-binding
            android:key="feature.name"
            android:value="@array/profile_synonyms" />
    </capability-binding>
</shortcut>

</shortcuts>

We have added this in manifest, <meta-data android:name="android.app.shortcuts" android:resource="@xml/shortcuts" />

Please find the bug report attached, https://drive.google.com/file/d/1-0xjmHSMUMTKzCI7qHfIaot5BeUGECwg/view?usp=drivesdk

Comments

ra...@google.com <ra...@google.com> #2May 16, 2024 03:04AM

Assigned to ra...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android bug report (to be captured after reproducing the issue)

Android Wear devices connected to Android devices

On you Android phone, following the instructions below, under the section ‘Instructions on your companion phone or tablets (Android)’
Launch the ‘Android Wear’ app on your phone or tablet.
Tap on the three vertical ellipsis on the top right hand corner of the screen and click on “Report Wearable Bug” to capture a bug report from the watch
On the watch, you will observe a notification card with the text “Bug report #X is being generated”. It can take up to 20 minutes for the bug report to be generated and transferred to your phone.
Once the bug report is done, the notification card on the watch changes to “Bug report #X captured” and you will receive a notification on the phone that reads “Wearable bug report finished.
Tap to send." Tap on this notification and email the bug report to a pre populated email address

Instructions on your companion phone or tablets (Android)

On your Android device, go to Settings > About phone or About tablet.
At the bottom of the screen, touch 'Build number' seven times in quick succession. You’ll see a message saying you’re now in developer mode.
Press Back to go back to the main Settings screen.
Touch Developer options.
At the top of the screen, make sure 'Developer options' is set to ON.
Check the box next to USB debugging.
Check the box next to Bug report shortcut.
Reproduce the issue or error message on your phone or tablet. It’s important that your device logs at least one occurrence of the problem.
Immediately after seeing the issue, press and hold the power button until the power menu appears.
Select Take bug report, then select Report in the dialog that follows.
After a significant delay -- up to two minutes -- your phone or tablet will vibrate and display a notification saying ‘Bug report captured’. Touch the notification to open Gmail with the report attached. +After replying to this message, you can disable developer mode and bug reports by going to Settings > Developer Options and sliding the top toggle to OFF.

de...@gmail.com <de...@gmail.com> #3May 16, 2024 04:50AM

I can't seem to access this issue from my original user (this issue doesn't load in 3 browsers and 2 computers), so I'm posting the bug report from this user.

I have followed the following steps:
1. Run an app with the following permission:
<uses-permission-sdk-23 android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS"/>

2. Run either one of the two pieces of code:
// Will fail silently with ActivityTaskManager system_server I START u0 {act=android.settings.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS dat=package:cmp=com.google.android.apps.wearable.settings/com.google.android.clockwork.settings.FakeSettingsActivity}
val intent = Intent(Settings.ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS)
intent.setData(Uri.parse("package:" + context.packageName));
context.startActivity(intent);

// Will crash the app with android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.IGNORE_BATTERY_OPTIMIZATION_SETTINGS dat=package: }
val intent = Intent(Settings.ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS)
intent.setData(Uri.parse("package:" + context.packageName));
context.startActivity(intent);

I executed the first piece of code and then the second, and captured a dump state. See here (shared with android-bugreport@google.com):

https://drive.google.com/drive/folders/1VTzRUWLs0zekwXkYybG9GhoItWLfU7p_?usp=drive_link

deleted

Restricted

0 B

deleted

Restricted

0 B

de...@gmail.com <de...@gmail.com> #4May 17, 2024 03:57AM

Replying via e-mail: I attached the bug report in the above comment.

Would appreciate your assistance.

*Uri*

On Thu, Oct 31, 2024 at 7:10 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ra...@google.com <ra...@google.com> #5May 21, 2024 07:16AM

Thanks for the information. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

Issue 340623304

Description

Issue summary

Comments

ra...@google.com <ra...@google.com> #2May 16, 2024 03:04AM

de...@gmail.com <de...@gmail.com> #3May 16, 2024 04:50AM

de...@gmail.com <de...@gmail.com> #4May 17, 2024 03:57AM

ra...@google.com <ra...@google.com> #5May 21, 2024 07:16AM

Add comment

Issue metadata