Is global-uploads.webflow.com down?

Hi
Is global-uploads.webflow.com down?

I have an Error for a script in the browser for this URL:
https://global-uploads.webflow.com/6329635a75bf4fc5edffba24/js/bundle.esm.js.map

Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received

DevTools failed to load source map: Could not load content for https://global-uploads.webflow.com/6329635a75bf4fc5edffba24/js/bundle.esm.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE

PREVIEW

Thanks for Help

No.

You can’t upload JS files nor map files to the asset CDN. Not sure what you are trying to do but is is helpful to follow the post guidelines when asking for help. If you don’t then don’t expect it.

This error message suggests that there was a communication issue between the listener and the message channel. The problem arises from the internal promisification of the sendMessage function, allowing it to be awaited. However, if no callback is explicitly specified, one is added internally to ensure the call returns a Promise. Consequently, if sendResponse is not called within onMessage, the API assumes that you have made an error by not providing a response through a callback, and it reports it as such.

Since the new behaviour is very confusing for almost everyone, a solution might be to stop showing this error when the callback is not specified, however it might cause confusion for those developers who still use callbacks and forgot to call sendResponse inside onMessage by mistake, which should be reported ideally as it always was.

In some cases it may be related to the Adobe PDF extension, you can follow these steps to troubleshoot and resolve the issue. First, ensure that the Adobe PDF extension is properly installed and up to date. Check for any available updates and install them if necessary. Next, verify if there are any conflicts with other browser extensions or plugins. Temporarily disable other extensions and test if the issue persists. If the problem is resolved, re-enable the extensions one by one to identify the conflicting extension.

If still error showing, try disabled all installed extensions in Chrome then you will get a clear console without errors.