I add the URL in the Webhook field of the Fulfilment page and it works. Start testing and for no reason it stops working. Check and the URL is gone and I have to add it again. Yes I am Saving and Yes I go back and check. This has started happening over the last few days.
Very annoying.
It seems to have stopped now. Something that just happens sometimes.
Related
I built a Google Home action using Dialogflow a few years ago, and it's been working nicely. A week or so ago it stopped working mysteriously. I have been debugging it, and all I can find is that the webhook comes back with "Webhook call failed. Error: DEADLINE_EXCEEDED."
I actually tried creating a brand new Dialowflow agent, and I'm getting the same error with the default fulfillment code. I'm guessing it could be related to the Node.js 10 upgrade on the back-end, but I'm stumped. Does anyone have any ideas of how to fix this issue?
Gordon
I had the same issue and found that the problem was that I did not programatically set the intent map for every intent in my DialogFlow app. I had to set this even for intents which didn't have webhook enabled, and required no use of the webhook code.
So all I did was added the following lines in my code for every intent and it solved the problem:
intentMap.set("Intent name",function_to_call);
A week or so after I posted this, everything mysteriously started working again. I think there was an issue on the Dialogflow side.
I have an extension that has been working for almost 2 years now with out issue. I havent made any changes in about a year, but recently i started seeing some change in behavior.
I use the Webrequest APi to intercept navigations. During the callback for some websites i need to do some security evaluations async. When this happens I redirect to a local resource (html) as an interstatial page that tells the user what I am doing. Once complete based off the evaualtion the page is redirected where it should be. This is ussually very fast and has worked great for the last 2 years. Since the latest version of chrome things dont seem to work anymore for all cases.
If i intercept an address bar navigation. everything works as expected. The interstatial pops and everythings great. However. If i click on the same website as a link on a webpage. I get the "Blocked by Extension page". (what you would get if the nav was cancelled). I also noticed that my interstatial is showing up in the web history and if i click on it from my history page everything works.
It seems as if a bug might have been introduced by google?
Just wondering if anyone has seen this.
Thanks
The _actions_on_google_ context stopped appearing in the contexts section, and I think this may be a clue to what's gone wrong.
It's just stopped doing anything, it'll get the required parameter then the JSON says it's sent it to webhook but there's only the 'secure' context in that (I remember seeing an actions on google one by default). When I remove my custom context it doesn't help, and I've updated firebase.
How do I get this back?
I think the issue was that I had deleted something in the code, maybe the }); at the end.
If you have the same issue, go OCD through your code and match everything together to check it's all good.
I've gotten a subscription product working fine with Google's Wallet for Digital Goods, but I can't make user's cancelling their orders work correctly.
If I cancel for them via the merchant center, it works just fine (I get the postback with the orderId as expected). If the user tries to cancel (and this is the same in the sandbox and in production), they see the "Are you sure you want to cancel" dialog, and when they say "yes" it immediately fails. There is simply no delay there.
From everything I've looked at I'm not getting a postback at all in this case (and I'm handling the postback fine when we cancel from the merchant center). I've looked through the logs on our web server, as well as instrumented the postback handler, and it seems to be failing before it ever gets to my code.
I got the same problem. Seems like there is something wrong at Google. These errors appear in the console.
GET https://224.32.32.221/90187 gr_full.js:26
GET https://224.32.32.221/90188 gr_full.js:26
POST https://wallet.google.com/manage/r903944a86542ecd9d4195e49cd5a8668/rpc/subscription 500 (Internal Server Error) com.google.checkout.buyercenter.client.buyercenter-0.js:4267
I'm trying to launch a "logout" page if the usesr closes the browser...I've looked for a couple of days and I think I have looked at all of the related topics...tried quite a few...but so far, nothing is working the way I need it to...
Everything seems to trigger just navigating to the next page...I want to be able to navigate the site and NOTHING IF I LOG OUT...but if I CLOSE THE BROWSER (or the DOMAIN changes), I want to fire the logout page.
Actually, it really doesn't need to open a popup...but that would be my preference...
Thanks for any help in getting a definitive answer...
HOLD THE PHONE...
Just FYI...I found what seems to be working here:
[http://eureka.ykyuen.info/2011/02/22/jquery-javascript-capture-the-browser-or-tab-closed-event/][1]
...and it also seems that there are some very useful variations from contributers.
I also added a line to the original script to execute my logout page...
You should be able to add a listener using onbeforeunload and ask the user if they want to log out in the prompt https://developer.mozilla.org/en-US/docs/DOM/window.onbeforeunload