Open IFTTT Webhook from chrome dont work / from android it works

I have a IFTTT webhook "kamera_aus" with works since an long time (calling from Tasker and homeatic). Today I tried zu add an action to teh Chrome zu trigger the webhook.

Calling the webhook from Join in Android works:





When I try to send the Webhook from Join Chrome Extension, it dont work (not show up as activity in IFTTT):



Sending from Chrome dont work:



Are there any Logs or debuging information? Why does the sending from Chrome not work? Trieding a an Chrome IFTTT action who sends "kamera_aus" (without quotes) dont work, too.

 

Admin?

 

Any Help?

 

No, but I dont know if there are more logs then the acivity view in ifttt. I have created a simple "test" Webhook that sends a email. This webhook can triggered from the Join app but not from the chrome extension.

 

I have enabled devmode in chrome Extension and get this error trying to send to IFTTT
Access to fetch at 'https://maker.ifttt.com/trigger/<SOME HASH>==/with/key/<KEY WAS HERE>value1=kvpVT%2F%2FmqMeGsJ6dkkT6Ag%3D%3D' from origin 'chrome-extension://flejfacjooompmliegamfbpjjdlhokhj' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

 

And a second thing: If I look at deviceIdsAndDirectDevices.js
var url = `https://maker.ifttt.com/trigger/${autoAppsCommand.command} [....]

My command is transfered ENCRYPTED and IFTTT will never understand this stuff!! (i have encryption enabled) therefore the command is nw5523CzUtvM1E5GDcfjYw== and there is a value1 because if encryption is enabled there seems to by a value pair transfered. (xxxxx==yyyyyy)

This can never be function, if encryption is enabled, because IFTTT cant decrypt this stuff.

I bet:

1. you get a CORS error, too, but this affects only the response from ITFFF therefore the command is triggered at your chrome
2. If you enable encryption, IFTTT dont work for you because the IFTTT Triggerword is transfered encrypted and IFTTT canT handle this.

Now it's your turn...

 

I tried it.

1. Disabling encryption, restart chrome
2. send command to ifttt

a) CORS error occurs; Triiher "test" is send!

b) test is triggered on IFTTT


==> If encryption enabled, triggering IFTTT from chrome wont work! Why isn't this tested before publishing a tool?

 

I h have seen you updated the chrome extension
Version 1.8.19 18. Februar 2020

but the IFTTT encryption bug is still there

 

You don't need to hurry, I've disabled encryption.