enter image description here
Can anyone recommend how I can do something here to continue on with my work? It says this API is obsolete
Related
I use an Google Assistant (Google Home) and would have an answer, which my Website gives.
For Example:
- I say: Hey Google, buy 3 Eggs
- my Website is beeing called (Webhook/wget/etc.):
http://url.de/befehl.php?befehl=buy 3 Eggs
or without keyword
http://url.de/befehl.php?befehl=3 Eggs
my Website gives following text/content: ok that was successful
Google simply says this text, which he got from Website: ok that was successful
IFTTT can only send a command to Website (Webhook) and lets google speak a fixed answer, but not dynamic answer.
Is it possible to realize that (IFTTT, Olisto, etc.) ?
It would be possible to run a Script, which itself gets the content/text of an Website and says what the Website gives (IFTTT-Webhook could do this, but says always the same text (not dynamic)).
Any Ideas, Tipps, Tricks?
Greetings,
Niko
It is definitely possible. You don't really need IFTTT.
I'll give you an example with something I am working on. I would assume you are working on Dialogflow to build your voice app.
Important: Calls outside the google network only work from an enterprise app NOT from the free version
You can just make a call from dialogflow like this for example:
const response = axios.post(...);
conv.ask(response.speech);
That is assuming your response from the server looks something like this:
{
status: 200,
speech: "ok that was successful",
response: "ok that was successful"
}
I have a webapp in production that interacts with Google Drive through Google Drive API.
I need to change some settings in Drive interaction but I can't save.
When I save the Drive UI integration page, I receive this error:
There's a problem at our end.
Please try again. If the problem persists, please let us know using
the "Send feedback" link below. Thanks!
(spying Network console: there is an Internal Server Error in a POST call)
I tried to send feedback for months: nobody answers and the bug is still there.
I tried also to create another project: I can save the first time but then the bug returns.
How can I do? Has someone the same problem?
Is there a way to receive a reply from Google? Is there some workaround?
Thank you.
i think that problem must be Client ID
before adding Client ID, go to the Credentials -> OAuth 2.0 Client IDs
then select edit your Client ID. after that your production site url add to Authorized JavaScript origins and Authorized redirect URIs.
then enter your Client ID in Drive UI integration page
For myself trying to get the Drive UI configured I noticed a couple of errors (that don't have any specific error messages)
When adding in an Open URL it has to be a valid domain, so for instance I tried to test it out with local host, to no avail. However something like https://devbox.app.com worked, but something like https://localhost:8888 does not. Even though https://localhost is a valid javascript origin in the client_id configuration (at least for the app I am working on, not sure about other apps), localhost doesn't work as an open URL.
When adding in the mimeTypes it needs to be in the format */* and can include custom mimeTypes like application/custom+xml and application/custom-name+json not sure for other custom types that are not in a particular format like xml or json. Also not sure about wildcards.
When adding in file extensions do not add in the '.' just the name of the file extension.
The app icon I found only failed to upload the image when the image wasn't the exact dimensions, I actually ended up editing some icons in photoshop to change the pixel x pixel values as a quick work around during dev.
That worked for me to get it to save and I tested it with a file that had a custom mimeType (application/custom-name+xml specifically) and custom file extension!
I shared a post from an application but the image doesn't show up in the update. I realise this question is asked a couple of times already and I checked all the info I could find here, to no avail.
I checked content type, which is correct.
I checked the url, which works.
I checked the ssl certificate which seems to be fine.
The image in question is: https://soworker.com/files/images/608-3XZcFrnujD_LN.JPG
The share is being made using the REST Api and the share itself gives a success message.
How can I debug why the image is not showing up? Am I missing something?
Thanks in advance for your response.
I am having this same issue. When I post this url via the API - https://blog.calevans.com/2016/05/16/postcards-life-010/ - it will not show the image.
However, when I post this one - http://voicesoftheelephpant.com/2016/05/17/interview-amanda-folson/ - it works.
Since they both sit on the same server and are both running the same software, my current theory is that LinkedIn can't read images from secure servers. Alternatively, however, less likely, it may be that they won't read from sites using Let's Encrypt images.
UPDATE: It seems to be Let's Encrypt. The podcast is also available encrypted but not using a Let's Encrypt cert because Apple won't read them. I posted a second update using the https:// version and it worked.
So it LOOKS like LinkedIn doesn't like Let's Encrypt.
HTH,
=C=
Apparently LinkedIn didn't like Lets Encrypt certificates. The problems is completely resolved now though and I don't think this will be a certificate issue anymore.
I built my first forefox addon and trying to submit it but when I try to submit if gives an error
Your add-on failed validation with 1 error.
There was a problem contacting the server.
It doesnt give any other error or warning. What does the above error mean. Did any one else face this problem?
Sounds like a temporary outage. Or your add-on really crashes the validator.
Having said this, SO isn't really the AMO support forum...
Better suited places would be the AMO forums, the AMO editors mailing list amo-editors#mozilla.org or the #amo and/or #addons IRC channels on irc.mozilla.org.
You may also run the validator locally if you're adventurous, but the correct setup of the tool can be quite a hurdle...
I'm using PusherApp, and I'm having issues with using presence channels. I'm authenticating, and passing this along to the "send" function. Attached are two screen shots. I have no idea how the formatting got messed up as the screen shots will show. You won't see the auth string portion as I took it out only for the screenshot but I know it's in the format:
applicationKey:signature
I took the sample signature for ruby and I generated it in .net and its the same so my procedure is correct I think.
Any ideas?
Thanks much,
David Whitten
David eventually answered this question himself and provided Pusher with the code. This has been rolled into the Pusher .NET REST Library.
Specifically, the code for presence authentication can be seen here.