You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.
Hi
Help with this would be greatly appreciated.
I am using the latest google assistant on my android device (11.41.10.23.arm64)
I am following the documentation here: https://codelabs.developers.google.com/codelabs/appactions/#4
Last night I was successfully triggering this intent from the app actions test tool (version 3.5.1) but the voice commands where not working from google assistant when saying "Hey Google, start running in Fit Actions".
But this morning these intents aren't even working from the App Actions Test Tools despite not changing anything from last night. Assistant is saying "Sorry I couldn't find that".
Yesterday evening I went through all the troubleshooting tips I found on the official google docs https://developers.google.com/assistant/app/troubleshoot and in other github issues for this repo. E.g. Setting locale to en-US on my andorid device and the App Actions Test Tool but no luck.
If it helps the app package name is "com.dave.android.fitactions"
These are the commands I used to generate the APK: ./gradlew assembleRelease jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 -keystore my-release-key.keystore app/build/outputs/apk/release/app-release-unsigned.apk alias_name
I have submitted this APK to google to be internal tested. I am running the same APK on my device installed with "adb install app/build/outputs/apk/release/app-release-unsigned.apk" (ignore the file name; it is in fact a signed APK)
Does this whole thing work if and only if I download the APK through the internal testing play store once it has been approved? Or can it work with locally installed APKs?
I am lost with this
Many thanks
The text was updated successfully, but these errors were encountered:
Same here, I even were never able to run it anytime. I also did this https://codelabs.developers.google.com/codelabs/appactions/#4 until the plugin step. But running the adb command in the plugin won't trigger the Intent.
Also in the codelabs, there is no google-services.json generated as described here
So here it is described to put a google-services.json into /app folder.
In the codelabs tutorial we upload an internal test release version to play store
?!?
@ArseneR81 I gave up lol. We now use vosk for hot word detection and then google SST for everything else. Our app is always in the foreground so we could get away with doing this
Hi
Help with this would be greatly appreciated.
I am using the latest google assistant on my android device (11.41.10.23.arm64)
I am following the documentation here: https://codelabs.developers.google.com/codelabs/appactions/#4
Last night I was successfully triggering this intent from the app actions test tool (version 3.5.1) but the voice commands where not working from google assistant when saying "Hey Google, start running in Fit Actions".
But this morning these intents aren't even working from the App Actions Test Tools despite not changing anything from last night. Assistant is saying "Sorry I couldn't find that".
Yesterday evening I went through all the troubleshooting tips I found on the official google docs https://developers.google.com/assistant/app/troubleshoot and in other github issues for this repo. E.g. Setting locale to en-US on my andorid device and the App Actions Test Tool but no luck.
If it helps the app package name is "com.dave.android.fitactions"
These are the commands I used to generate the APK:
./gradlew assembleRelease
jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 -keystore my-release-key.keystore app/build/outputs/apk/release/app-release-unsigned.apk alias_name
I have submitted this APK to google to be internal tested. I am running the same APK on my device installed with
"adb install app/build/outputs/apk/release/app-release-unsigned.apk"
(ignore the file name; it is in fact a signed APK)Does this whole thing work if and only if I download the APK through the internal testing play store once it has been approved? Or can it work with locally installed APKs?
I am lost with this
Many thanks
The text was updated successfully, but these errors were encountered: