I've posted a game on Google Actions named "Jeu du pendu".
When it is launched with the invocation phrase ("Parler avec jeu du pendu" / "Talk to the hangman game") it works normally.
But when it is launched via a tap in the list of games, the conversation ends immediately and the game does not start.
The same problem occurs on the Nest Hub Max or on a smartphone.
On the hub max you just hear 2 beeps. On the smartphone there is a message "Jeu du pendu a quitté la conversation" / "Jeu du pendu has left the conversation"
There is no crash reports of this event in Analytics page, neither in the Api logs.
I reached the Google Support team but they said they can't help with that.
Does anyone have an idea of what could be missing ?
Thanks in advance.
Finnaly I got the solution.
After searching a little more, I saw a built-in Invocation named 'PLAY_GAME'.
By default it redirects to the 'End Conversation' action.
I changed it to redirect to the 1st game Action like for the Main Invocation (invocation phrase). I re-published the game like that a few days ago.
I just tried now and it works !
It seems that there is no way to test this launching method in the Test console.
Thank for your help.
Related
I deployed the production release for my first Google Action. But even 2 weeks after the approved deployment I can find my action neither in the Google Assistant store nor directly via voice activation.
The test versions ran fine and was found every single time. So the invocation name should not be the problem. When I use the generated action link from the console I find the action in the store and can send it to my Smartphone, where I can start it with the sent link. But after closing the app I cannot open it again via voice.
I used two different google accounts on different devices (all are set up in the right language: german), but no chance.
Is this a mistake on Googles side or do I miss anything? In this state I have to open the action every time over the action link which is useless for a voice app :)
Here is the link to my action: https://assistant.google.com/services/invoke/uid/000000c77f740137?hl=de
The invocation would be for example: "Mit Erfolgs-Fans sprechen" (like said, on the test this name was found every single time)
This happened to me too. Though it wasn't in production when I faced it. I was also not able to see the action in Assistant-enabled devices (Google home app/assistant).
It is probably not the invocation name issue, it is just that the action is not being made visible across all the platforms. Some of the solutions I tried were-
Clean cache of the device
Create a new action with everything just the same as in your current actions. It worked once for me!
Go to GCP and under your project, try to understand if there is any pending activity.
Once I created so many actions because I wasn't able to see it that after around 30 days all those actions started to become visible. So, if you can wait that is fine.
In the end, do contact their support with all the relevant information. I hope they should be able to help.
Thank you!
I'm setting up about my 10th (test/demo) Action on Google, and the simulator ONLY supports me starting my brand new app via "Talk to my test app".
How do I get to the point I can say "Talk to {my app name here}"?
IN THE PAST, after setting up all the Action details (via 'Overview' screen), and clicking 'TEST DRAFT', it usually resolves and the simulator starts suggesting to me "Talk to {my app name here}".
But this time it's not happening. It's stuck on "Talk to my test app", and has been for almost 24 hours.
Does anyone know the magical incantation required to get the Actions Simulator to accept invocations using my actual app name?
I'm using Dialogflow, which was all setup using the Jovo framework actually - using 'jovo deploy' to stand up the Dialogflow agent and Actions config. I can't see that Jovo would have anything to do with the issue here, but you never know with software! All the config in Dialogflow and Actions looks good to me.
What you've described sounds like it should work, but it sounds like you should double-check for any errors.
In the Actions Console, make sure you don't have any errors indicated on the overview screen. If you do (or even if you don't), click on the Edit button for stage 2: App Information.
In there, check the error messages to make sure they're not applying to the name or pronunciation. Make sure both the name and pronunciation are valid and accepted.
If you're working in more than one language, make sure these are set ok for all the languages you have set.
Test it from the Simulator link on the left navigation instead of going back through Dialogflow. They should do the same thing, but it sounds like it is possible that isn't taking in this case.
During 10.8 times I created macro in Keyboard Maestro for adding web pages to Reminders list to read them later.
In Mountain Lion and Maverics it worked fine but in Yosemite something wrong is going on resulting very slow executions.
Previously execution time was about 1-2 seconds now its over 40 seconds or even one minute!
Apple team provided me with wrong solution ordered to "code sign" my script, but there is no "file" to codesign and applescripts can be executed in command line. So IMO they messed up something in osascript and still couldn't fix it till 10.10.4. But I need someone to confirm or to advice me how to debug problem, because I cannot find in system console log lines relevant to problem.
UPDATE:
On El Capitan 10.11.1 problem still persist.
Macro
Could anyone test and confirm this? I provided link to macro.
It is bind currently to F1 - change as you like. Before execution create "2Read" list in Reminders on OSX.
I've tried it and it's done in about 1-2 seconds on my machine. So I do not experience the same problem as you.
I'm running OS X 10.10.4 on a late 2013 MBP Retina.
Maybe your "2Read" list is too long?
Another tip:
I used to have a problem with long lists in Applescript, too. Sometimes it would take minutes to run through a list, but after using some if these tips the time for the lists was brought back to only seconds.
From your pastebin link (yeah, I did warn you it'd look like mince):
Keyboard Maestro event logs
(1) KM sends an 'open' event ('aevt/odoc') to Growl, telling it to open a temp file (presumably to make Growl display a message)
(2) Bartender sends a 'get scripting terminology' event ('ascr/gdut') to KM
(3) Bartender sends a 'BTDR/Load' event to KM, which looks like Bt telling KM to load a plugin named "BartenderHelperNinetyOne.bbundle"
(4) KM send a 'KeyC/KeyB' event to something (it doesn't give the name of the process, only its Process Serial Number, which is the classic MacOS equivalent to a Unix process ID). Probably easiest just to ask the KM devs about that one.
(5,6,7) KM then sends three 'application died' events ('aevt/obit') to Keyboard Maestro Engine (I'm guessing that's a faceless helper app that runs constantly in the background), informing it that three osascript processes (PSNs 312312, 315315, 316316) have terminated. This doesn't necessarily mean that osascript has crashed as those events contain an error number ('errn') parameter with value 0, and command-line processes normally return error code 0 to indicate they've completed successfully. It's quite likely these are normal internal notifications sent between KM and KME to indicate when a task is completed. The first of those osascript processes (PSN 312312) is related to the Reminders activity below; the other two I'm guessing are you running other AppleScript macros and probably not relevant here.
Reminders event logs
(1,2,3) The 'osascript' process with PSN 312312 sends Reminders a 'make' ('core/crel') event and two 'set' ('core/setd') events, which is obviously your AppleScript being run.
(4) The Dock sends it a 'reopen' ('aevt/rapp') event, which is probably just you clicking on Reminders' dock icon to bring it to the front.
The main problem, of course, is that without timestamps I can't tell you where your 40-second delay is occurring. You'd really need to do it again, this time manually noting the time at which each message is logged. And if you see a single 40-second delay somewhere in the middle, it should easy enough to determine which events it's occurring inbetween, which should start to point towards a cause. At which point, you're probably best contacting the KM vendor to discuss it with them.
HTH
In the past I had successfully created several Google Earth tours complete with audio and animation. As best I can remember, I looked at one of my tours 2weeks ago? and things were working fine.
But I look at the tours now on both my local machine and my host web server and the google earth tours have disappeared. When I look in firebug at where the code should be, I see the following error:
Failed to process gadget http://code.google.com/apis/kml/embed/tourgadget.xml. Reason: Unable to retrieve spec for... code.google.com/apis/kml/embed/tourgadget.xml. HTTP error 404
I have not changed anything within my code, so am completely at a loss.
Can anyone share what might have happened or what I need to do to get my GEs going again?
My web site is www.kavelookout.com...See www.kavelookout.com/fingers.html for where a tour should be.
UPDATE:
I believe this is the GE tour gadget code I need...
http://www.gmodules.com/ig/creator?synd=open&url=http://code.google.com/apis/kml/embed/tourgadget.xml
but as you can see, clicking on the 'More info...' link takes me to... google.com/ig/directory?synd=open&url=http://…
Does anyone know why GE Gadgets is not working at this time? Or what link I should be using to embed GE Tours? Can anyone confirm that GE Tours are having a problem, or is it me?
Much Thanks,
k
You should notice that the pages you're trying to process are no longer available, so, that's the nature of the error.
Check the link, it sais that the page is not being found, that's why you're getting a 404 error.
So I figured it out.
The embed code that was generated in the past was...
script src="http:// www.gmodules.com/ig/ifr?url=http://code.google.com/apis/kml/embed/tourgadget.xml
I'm not sure why or when it changed, but I found that the GE Tour gadget at this URL...
http://www.gmodules.com/ig/creator?synd=open&url=http://dl.google.com/developers/maps/tourgadget.xml
...now generates this new embed code...notice the differences...
script src="//www.gmodules.com/ig/ifr?url=http://dl.google.com/developers/maps/tourgadget.xml
Again, I'd love to know why things changed, but am happy to know there is an answer.
I am getting the following error on my facebook app with the facebook live stream widget, but only at random times:
Live Stream Box configuration error
Live Stream Box couldn't be loaded at this time. Please try again later. For more detailed information on the Live Stream Box please visit the Developer Wiki.
Any ideas? It is really strange because it works sometimes and doesn't work other times. I would have thought that if there was really a configuration issue that it would work 0 times?
Try putting the at the bottom of the page, right before the "< body>".
It worked for me.
http://www.codecheetah.com/solution-facebook-live-stream-box-configuration-error/