GPT Actions: Refused to execute inline script because it violates the following Content Security Policy directive:

Hi,

When migrating a plugin that is OAuth’ed into the new GPT Actions, we can’t seem to access our own API anymore due to the following authentication error

[Report Only] Refused to execute inline script because it violates the following Content Security Policy directive: "script-src https://xxx.cloudfront.net https://auth.xxx.com".
Either the 'unsafe-inline' keyword, a hash ('sha256-xxxx'), or a nonce ('nonce-...') is required to enable inline execution.

Has anyone else encountered this ? It was working fine previously but something must have changed with the new Oauth flow that breaks that call

// EDIT: This has been fixed from OpenAI’s side and is working properly now