When using AATT-App Action Test Tool for android slices. I'm getting slice in google assistant but when it comes to direct voice search or typing my event name, the slices are not able to appear like using in AATT. pls give me some answers to resolve this issue. isn't dialog flow required for this types in GA?
You can refer below links to troubleshoot your issue the problem seems similar and already reported in these questions and github issues.
Assistant shows “Sorry, I couldn't find it”
Github: Not able to open the app through google assistant
Github: Action not work via Assistant
Related
Is it possible to debug an app via the plugin (Google Assistant test) or can someone tell me how to do it via Android Studio. Normal apps can be debugged, but what about the integration of Google Assistant.
The current version must always be uploaded to the Play console, even though I'm only testing. In addition, the version number must always be changed. Is there an easier way?
About the app: I really just want to start an action with a shortcut.xml that is given a few parameters that are evaluated in the app. (Ok Google, set the clock in the kitchen to 3 o'clock, in myapp) Everything else is handled internally, so as simple as possible. No ad or anything. I can't get it. The examples are all too complex. Can anyone help me?
I want open an app that we haved coded without realse it in play store with Google assistant,
Is it possible?
Cuz when say app name it doesn't recognize our app and go to search section.
Yes, you can open your which is not published on play store with google assistant.
I have tried it with my apps and it works fine.
Just make sure your are pronouncing the name correctly.
you can also say " Open App Name from my device" so it will not go for search.
I uploaded a small video demonstrating google assistant opening an unpublished app
Edit: Please accept my answer by checking the ✔(tick symbol) next to it if you found it helpful.
The Android TV (ATV) app I'm working on has voice control capabilities. Basically, when the user presses the microphone button on a remote controller, the key event (identified by KeyEvent.KEYCODE_SEARCH) is handled by the app, speech recognition starts (using android.speech.SpeechRecognizer), the results (parsed speech) are obtained and parsed further by the app logic (e.g. showing the user search results or performing some in-app action).
Everything has been working as intended and described above, until, quite recently, Google Assistant (GA) was introduced to ATV platforms (the first one being Nvidia Shield box). Now, when the RCU mic button is pressed, the GA overlay appears and the mic key event doesn't even reach the app.
For the last few days I've done some extensive research (documentation, internet, forums, stackoverflow etc.) and experimented with some potential workarounds, but nothing's worked so far and I haven't been able to find any definite information on the topic (probably due to the ATV+GA combination being rather new on the scene, and the ATV ecosystem not being as large as the Android one).
The best hint I got so far is what's been done with the Spotify app for Android TV. When it's run on an ATV device with no GA, it basically behaves as I described above; but when GA is present, the GA overlay appears, receives the parsed speech and shows the search results, with results from Spotify in the first line - so, the Spotify app is integrated with GA, and this integration replaces the in-app voice control mechanism. This suggests that either there is no way to ignore/disable GA inside your app in order to receive the mic key event and proceed with voice control as usual, or at least this is the preferred way of handling voice commands now. It also shows that there are apps for ATV that approach voice control the way I described, so maybe someone here has already encountered similar problem.
My question(s):
is it possible to prevent Google Assistant from taking over RCU mic button signal?
is it ok to do so? (by "not ok" I would mean - are there any official guidelines that discourage such behavior - or at least are there valid reasons not to do so?)
if so, can it be done?
if not, is there a resource documenting how to integrate with GA (the way Spotify for ATV app does)?
Starting with your last question:
if not, is there a resource documenting how to integrate with GA (the way Spotify for ATV app does)?
I wrote about how to integrate on the Android Developer's Blog. Spotify has onboarded their content catalog to Google's services which is why the Google Assistant is able to work so well. You can achieve similar results if you make your app searchable (covered in the blog).
is it possible to prevent Google Assistant from taking over RCU mic button signal?
No, not at this time. The Google Assistant is a system app that takes control over the mic to give a uniform experience across all apps.
is it ok to do so? (by "not ok" I would mean - are there any official guidelines that discourage such behavior - or at least are there valid reasons not to do so?)
if so, can it be done?
You can still have an in-app search experience. There is an example in the leanback sample. You will need to set a listener on a BrowseFragment and implement a SearchFragment. We know this can be confusing, have in-app search and Google Assistant search competing, but we are working on how to improve this.
how to make invisible my android app to everyone from google play store.
only specific peoples can download it through link given or any other procedure.
mean is everyone can't find app on play store by just search app name.
Or tell me any other solution close to it.
Withing Google play you can use Alpha and Beta testers to restrict the distribution of your app.
You can define a list of users. They will be the only able to get the app. Once done you update your app in google play, wait few hours and then google play will generate a link. You just have to send this link to your users and they can install the app.
This is the summary of the Google documentation ( in better english than mine )
You don't need a production APK to publish an alpha/beta app.
Users need a Google Account (#gmail.com) or a Google Apps account to join a test.
If you're testing an existing app that you've published before, only users in your test group will receive an update for your alpha/beta version. If you're testing a new app that you haven't published before, only users in your test group can find and download your app.
After publishing an alpha/beta APK for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers.
You have the full documentation here.
If you dont explicitly need it on the play store, TestFairy is a very powerful tool. I use it to distribute to selected people until I'm ready to share it with the world.
The API is very simple and informative.
You can also build and upload versions directly from Android Studio.
Could anybody give me some directions on how to add a video ad. to my android app, I couldn't find anything on Google. Can someone explain it to me step by step?
There are a lot of Ads providers out there, few examples: Tapjoy, AppLovin, ChartBoost, MoPub...
For Video Ads, AdColony is a great provider, and is very easy to setup and code. Also they gives a few project with differents alternatives to implement.
Test it: adcolony.com