Recipe Clipper not working anymore about recipesage HOT 5 CLOSED

Very odd. I see the same extension ID as you posted (1bd6f0af-1e56-4ecd-903b-495f25057d55), but that's not what's used for CORS it seems... The "Internal UUID" value is used in the moz-extension:// URL which is what CORS checks.

from recipesage.

Looks like this is intentional. Here's some documentation about it: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions#host_permissions

from recipesage.

I am also getting the action failed error but on Chrome and not for all sites.I agree that it is a CORs issue as the console error in Chrome looks like this:

Access to fetch at 'https://api.recipesage.com/proxy/ingredient-instruction-classifier?token=bef2cc6d93c4250146aa5edc0bbf389475680b5fbab1859a005fec145ca52aaee3638376baca4923c1102b2bf6ff4987' from origin 'https://hartburnvillagewi.wordpress.com' 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.

from recipesage.

Can you post some example sites where you're seeing the error?

from recipesage.

https://hartburnvillagewi.wordpress.com/
https://www.allrecipes.com is a big one and at least crock-pot-party-meatballs and chef-john-s-chicken-saltimbocca-recipe and red-wine-braised-beef-tips-recipe 3/3 on my testing.

from recipesage.