actions-on-google/appactions-common-biis-kotlin

This sample Android app manages items on to-do lists using Google Assistant implemented via App Actions.

*:warning: Warning: Go to App Actions to-do list sample for maintained sample.

⚠️ Warning: This App Actions to-do list sample has migrated to App-Action directory in Andriod Github. This version will no longer be maintained.

This sample Android app manages items on to-do lists. Users can add items to to-do lists, search for items by category, and view information about completed tasks.

Note: This sample application is a fork of the Android to-do sample.

This is the starting code for the Extend an Android app to Google Assistant with App Actions codelab.

To see the completed project, go to master branch.

Contribution guidelines

If you want to contribute to this project, be sure to review the contribution guidelines.

We use GitHub issues for tracking requests and bugs, please get support by posting your technical questions to Stack Overflow.

Report general issues with App Actions features or make suggestions for additional built-in intents through our public issue tracker.

References

• App Actions Overview
• Built-in Intents reference
• App Actions Test Tool
• Codelab
• Other samples

appactions-common-biis-kotlin's Issues

Action problem

Hi
I am trying to get this app to work.
My device runs android 9
google assistant version: 11.42.16.23.arm64
I have followed the steps in the readme.
I have set the invocation name to "test app"
The problem I have it that actions 5-6 do not work using my voice in google assistant (instead of opening the app the google assistant shows search results), it only works from the android test tool in android studio. The other actions work flawlessly without a hitch. Why is this? Many thanks

1. "Open active tasks in test app action"
   

2. "Open completed tasks in test app action"
   

3. "Open all tasks in test app action"
   

4. "Open stats in test app action"
   

5. "Search family in test app action"
   

6. "Look up eggs in test app action"
   

Many problems while going through tutorial

• When on app opens, it doesn't prefilled TODO list with the repository data
• When shortcuts are defined, the App Actions Test Tool v3.5.5 reports an error: No Android Module with actions file reference found. Do we need actions.xml? If yes, please provide the steps in the tutorial here
• I've noticed meta-data tag for the shortcuts, defined under activity tag in AndroidManifest.xml. I've tried moving it one level up, under application tag, still plugin error
• The App Actions Gradle Plugin error, was not able to create a preview
• Had problems with Google PlayStore and privacy url. Had to provide it with one
  Please provide a feedback. I would love to continue with the Google Shortcuts tutorial.

actions.intent.GET_THING does not working

Hi
I am trying to get this app to work.
My device runs android 9
google assistant version: 11.42.16.23.arm64
I have followed the steps in the readme.
I have set the invocation name to "test app"
The problem I have it that actions 5-6 do not work using my voice in google assistant (instead of opening the app the google assistant shows search results), it only works from the android test tool in android studio. The other actions work flawlessly without a hitch. Why is this? Many thanks

1. "Open active tasks in test app action"
   

2. "Open completed tasks in test app action"
   

3. "Open all tasks in test app action"
   

4. "Open stats in test app action"
   

5. "Search family in test app action"
   

6. "Look up eggs in test app action"
   

Doesn't seem to work on Giraffe

I am trying to use this project as part of the "Extend your Android App to Google Assistant with App Actions" codelab and cannot build it! I am using the Android Studio Giragge (2022.3.1 Patch 1), which uses a JVM v17.

I have downloaded the "codelab-start" branch as instructed here, but when I try to build the project, I have issues:

FIRST ATTEMPT

1. It raises a Mockito version not found... I followed the suggested IDE action and upgraded it.
2. The build now fails like this (which looks like a JVM version incompatibility?)

> Task :app:kaptGenerateStubsDebugKotlin e: java.lang.IllegalAccessError: class org.jetbrains.kotlin.kapt3.base.KaptContext (in unnamed module @0x78e8a243) cannot access class com.sun.tools.javac.util.Context (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.util to unnamed module @0x78e8a243

SECOND ATTEMPT
3. I tried to upgrade the Kotlin plugin version to 1.8.22 and 1.9.0 as recommended here for a similar problem.
4. It seems to go further on the building process, but now it breaks on what seems to be a language semantics problem:

codelab-todolist-error.log

Working on iOS

Does the Google Assistant SDK also work on iOS? I couldn't find documentation for developing for iOS. Do the biis here work there? Is Google exposing an sdk for iOS?

App Actions sample code doesn't work on my device

I set up all with guide you provided,but I didn't get a good result.
In the process of my solve this problem,I found that app actions doesn't available on android TV。
So I wonder if app actions doesn't work on android TV, if so I may should try another way.

Hope your response, thx

"Tools > App Actions" Doesn't Exist

I can't use the tool to view my app actions on Android Studio. I see XML Actions, but no App Actions.

It works through ADB but not with Voice

I managed to make work the App following instructions.
I can execute the action with Google Assistant plugin and works fine (launching the intent with adb). App is opened with Term in the textfield to be searched.
But I cannot trigger the same action with my voice. Assistant does not recognize "Todo App" or any phrase that is mentioned in the Codelab. I have tried many phrases, but with no success.

Is there anything we need to do to let Google Assistant recognize the name of the App?
the action the name of the App is the label (android:label="@string/app_name"), the name that appears under the icon.
Note that I am testing with the App in internal test, not in production, could this be the issue?