Hello, we’re having the exact same issue with the Content Security policy. Has anyone resolved this yet?