I'm trying to add a select channel trait.
what I did was that I followed the docs,
1- Add the ATTRIBUTES to the device I want to apply this feature on, for example, a TV device type
2- I guess we are all done as every other command works with my code
What I actually did was the following to the device database in Firestore
then added the
case "action.devices.commands.selectChannel":
in the
switch (execution.command) {}
code
then reloaded the device from the google home app
then when I try to call
"Change to ABC on my TV"
it says
'Sorry, I don't understand.'
and nothing appears on the logs
otherwise, everything is working perfectly,i.e setting the volume and On/Off.
what am I doing wrong, please?
UPDATE:
Today I tried command "action.devices.commands.returnChannel" and "action.devices.commands.relativeChannel" and they are working fine
and all three commands belongs to the same trait!
I've seen a lot of users complaining about this command on many sites
like the following 1,2,
could this be related,
I'm still in debug mode, would it be fixed when I publish my app
UPDATE #2
I tried it today with an android phone and it works fine with selectChannel command,
previously I was testing with an iPhone with google home and google assistant apps on their latest release, and the selectChannel is the only command that didn't work there.
Hope it's just related to the debugging mode
It is usually unexpected to have a trait / feature working on the Google Home App on Android but not on the iOS version, as their functionality is nearly identical. The accuracy on the speech to text conversion on both platforms might be different, which could be affecting the functionality. You can try out typing your request to see if that helps in any way.
Related
I have three projects on Google Actions and i need to work on their respectively simulators to try solve some problems with the last version, but on two of the projects the simulator is not working, it tries to load but get stuck with a blank gray frame below the actions console menu.
It is strange as the three projects have the same code, had been tried on the simulator about a month ago and deployed on production. The only thing difference between the project is that the ones that are not working has the portuguese language added and due to some internal bug on Google Action (as Google technician had told me) approved version didn´t have the portuguese added.
I´ve tried in different machines and different browsers with the same result. I´ve contacted Google and they tell me that with their agent account that I´ve added they can access without problem.
Any idea on what to try?
Thanks in advance
Edit:
Now, without touching anything, I can´t access my action anymore (no simulator, no develop, nothing). When I try to access an error screen appears telling "There was an error completing your request". I´ve tried to download it with gactions pull but I receive a 500 error.
When using the simulator in the Actions Console, I get the response:
"Since your voice wasn’t recognized, I can’t do that right now. Check the Voice Match settings in the Google Home app."
The account under which I am developing has no devices registered, intentionally. This account is used specifically and only for development.
Why does the simulator respond like this, and how can I fix it? The account has no "Google Home app".
I have another (personal) account which I've used to develop the Action initially. The simulator works fine there. Now I'm trying to move the development to an "official" corporate account, and the simulator fails completely.
I can confirm I'm getting exactly the same occurrence here.
Doesn't matter what device type is selected as being used.
Similarly was working fine a couple of days ago.
Looks like Google has broken something with account linking and the Actions on Google Simulator.
I did however read somewhere that best practice you should be delivering some functionality that does not require account linking. That way you will still get explore ratings from users who visit your assistant but refuse to sign in.
However that doesn't fix the core issue of testing functionality that requires sign-in using Actions console simulator.
Has anyone noticed that the Simulator in the Actions on Google Console has been updated and it no longer is an accurate simulation of the assistant app on devices?
They added a display tab but it seems to not show all the output. My application often includes 2 chat bubbles in one response and the new simulator only displays one even though the tts for both is heard in the audio.
I have the same problem. Hope they don't remove the ability to add to responses. It would look terrible with only one line.
I am working on an app that uses Firebase dynamic links. All throughout testing, the base link, and deep links would open the app, as expected.
At some point, this stopped working on my test device. I tried turning the Associated Domains off and back on again (format is applinks:myappid.app.goo.gl). My URL Types setup in Info has the URL scheme set to my app's bundle id, which is also reflected in Firebase. My AASA still has the expected info in it as well.
I also tried long pressing on the link in both notes and messages (don't get an option to open in app, just open), but it still refuses to work. Oddly enough, it still works in simulator. Any help would be appreciated.
Update: I uploaded the build to TestFlight, and it works properly there. It looks like the issue only occurs on a physical test device, with the app being built from XCode.
Solution Update: Oddly enough after installing a dynamic links build via TestFlight, subsequent XCode test run builds started working properly again. Not the most elegant solution, but at least it is working now.
Update:
This most likely has to do with an open issue that prevents the AASA file from being updated or installed. Currently the only work around is to delete the app, reboot the device, and reinstall.
http://www.openradar.me/radar?id=4999496467480576
I desperately need to use the Safari console on iOS 7 to debug a site. I've hooked my iPhone (5) displaying the site to my Mac. I've started Safari (v6.0.5), gone to the Develop menu, and started the web inspector for the site I'm on. I can see the list of elements on the site, which confirms I'm inside the correct inspector.
From what I've read, the logs to the console should be displayed inside the Logs section, and from what I've found inside Apple's iOS Safari documentation, I should be able to view logs inside there. For me though, nothing is ever logged. I can't even access any variables or functions; when I type anything in (e.g. document.title), it just 'logs' exactly what I've written, with the text I've just typed still in the input field. However, typing something that causes the browser on the device to show life works (e.g. alert('hi'); displays the alert dialog box on the device).
Can anyone help? This issue we have is only happening on iOS, and there's barely any other way to find what's going wrong. Is this problem limited to iOS 7?
I can confirm that this is an iOS 7 issue. The console.log statement works fine when using an iOS 6 or below device, but with iOS 7 won't show at all :(
Apple == new Microsoft();
Only minutes after posting this I got logging to work again, not sure if this is required, but it seemed to do magic for me:
Connect iOS 7 device
Open XCode
Setup device for development
Connect using Safari
Presto, I can see log messages again?!? (Mind you, I had not made any code-changes)
I had the same problem, just after updating to iOS 7. The solution was to update safari to the latest version for developers, which is version 6.1.