Keep receiving “(my app name) isn't responding right now. Please try again soon” on my actions on google simulator, I’ve tried almost all the solution that I found on the internet and ended up with this, I decided to copy the code from google https://developers.google.com/assistant/df-asdk/helpers#calling_the_helper it works just the permission one , for the permission handler it doesn’t work it seems like if I do not put the default response in dialogflow It wouldn’t work so I don’t want that default response because it keeps saying that response, and when I removed it , it gave me an error ,but in the debug tap it shows everything(display name, location etc.)
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
Im using RPA blueprism. Ive 2 interacting browser which is passing data between each other but i cant bring the currently interacted browser to the front. That means the process is running on the back of the first browser. Is there any global action that i can use? Ive managed to get the PID of each browser and ive tried using Focus action on html element but no luck. Do help and TQVM in advanced.
Try spying the entire browser as an element and in navigate stage use activate application. it brings the browser to the front.
Today we noticed new undesirable behavior from our DocuSign implementation. We are using the embedded signing approach.
Server-side when the form is loading we generate the recipient view URL. This part works fine.
Then we load this URL in an iframe on the form. The iframe only takes up a portion of the form.
Previously this was working fine, but as of today we noticed some errors. The signing ceremony still loads, but we can see errors in the console in Developer Tools. They seem to be coming from inside the iframe. When we remove the iframe the errors go away.
The console in Developer Tools, shows that a 400 (Bad Request) is being received from https://demo.docusign.net/Signing/monitoring?insession=1&ti=4c6f3176cf8841b7885f76a4b5261744 (picture below). This is not a URL that we are calling, so it must be called from within the iframe.
The signing ceremony still works from a user perspective, but this error seems to be halting client-side scripts on the rest of the page. When we remove the iframe, everything else works fine.
Any help would be appreciated. Thank you!
Embedding the signing ceremony inside an iframe is not recommended.
There are multiple techniques available for maintaining your application's state while the signing ceremony is proceeding. Why do you feel the need for an iFrame?
That said, please provide the envelope_id that had the problem and I'll submit an internal bug report.
Note, the initial url your app receives is not the final url for the signing ceremony. As part of the process, the response to the initial url is a redirect to another. That's been the case for a long time.
We finally got this working.
We changed this markup:
<iframe src="{SigningCeremonyUrl}" />
To this markup:
<iframe allow="geolocation" src="{SigningCeremonyUrl}"></iframe>
As you can see the only differences are:
Added allow="geolocation" (didn't fix the problem by itself)
Removed self-terminating <iframe /> tag and used opening and closing tags
(resolved the issue)
Notable discoveries:
The bug presented itself on 11/10/2017. It was demoed working at 8:00 or 9:00am EST, and then stopped working by the end of the day (3/4/5ish), without any changes being made on our end.
When we removed the iframe containing the signing ceremony URL, the rest of the page worked fine. Adding it back recreated the issue.
When changing the URL of the iframe to Google, the rest of the page worked fine. Changing it back recreated the issue.
When running the signing ceremony URL in the whole window (without the iframe), and with Developer Tools open, it did not throw any JavaScript errors.
When running in the iframe, and with Developer tools open, the only error we saw was the one posted in the question above.
When running in the iframe, with self-terminating html tag, we ran the following test, and only received 1 alert:
<script type="text/javascript">alert(0);</script>
<iframe ... />
<script type="text/javascript">alert(1);</script>
When running in the iframe, and with Developer Tools open, it was as if the our JavaScript wasn't even there. No scripts ran once the iframe loaded.
I am building a web application using the Spotify Web API. The calls are pretty straight forward and I don't understand if it is me doing something wrong, or if there is something wrong with the Spotify service.
I implemented the lookup call (works fine) and then add track IDs to my database when a button is clicked next to one of the results. I then do an ajax call to display that track in the "Play Button" iframe.
Instead of showing my playlist now, I very often get a 502 Bad Gateway error. (This error also appears on the Spotify website where the example is supposed to be shown.)
Is this something I cause? My browser / system causes?
Thanks a lot in advance!
(This error also appears on the Spotify website where the example is supposed to be shown.)
This suggests that the problem is on Spotify's side, assuming you're giving the Play Button a valid Spotify URI. Hang tight for a while and it should sort itself out.