I am currently working on a clients page trying to help them fix two 404 errors that the site is getting.
We are having trouble figuring out where it is coming from. I suspect its one of the apps/extensions installed. Since I don’t see anything when searching in the theme file. But all we can see is some ID’s. Is there any chance someone has an idea?
The site is attempting to load a. js file and a .css file in the head:
Any chance I can somehow identify where this is coming from..? Can anyone check what extension this id is? 763537e8-9172-4618-9bd3-c8ffb0e5ea75
Hey! I have the same error! Do you have any Ideas to fix that?
Sorry i am looking for a solution here on the forum, but seems no one knows 
I’m trying to find a way to connect that UUID back to the App, but found nothing so far. Debugging by disabling the apps one by one is not feasible for a live store with dozens of apps - I know, I know!
I’ve tried everything and looked everywhere to see if the UUID matches up with anything, but could find nothing. I’ve contacted Shopify Partner support and hopefully they know a way to debug this.
Sometimes it feels like back in the WordPress days with all the half-baked Plugins getting installed by customers 
HI @mcb-jra I was seeing a very similar error on one of my client’s sites and it turned out to be caused by a Klaviyo embedded form using their app block. As soon as I disabled the block and loaded the site those console errors disappeared.
Hi @Jesse_Meyers , I have the same error. How can I find the form to “unblock”? Thanks!
Hi @martiperin the app block I was referring to is a technology that allows for apps like Klaviyo to provide widgets in theme customizer rather than having to edit the theme code manually. To remove the Klaviyo app blocks, open the theme customizer for your live theme, view the page in the customizer that is reporting errors, and if it is the same issue then you should see somewhere in the settings an app block for Klaviyo like in the attached image. Just click the eyeball icon to hide it, save the change, and then see if the error is resolved.
Hi @Jesse_Meyers , thank you!
