Setting both the 'Origin' and 'Authorization' headers is forbidden about javascript

[ducan-ne]

I have exactly the same issue when follow the instructions from chrome-extension readme

Already patch {"allowed_origins": ["chrome-extension://hffncgjlomhcifdgaagggiemefokmpnp"]} to project

More context: I'm running in content scripts, not sure if it's the root cause. This now is the blocking to my release 🥲

[stelmakhivan]

Faced the same response error, using @clerk/clerk-expo and sign-up with Google
Possible because of this line
https://github.com/clerk/javascript/blob/main/packages/expo/src/singleton.ts#L43

[tmilewski]

Hi all,

The issue here is that the ID for the Chrome Extension / Expo application has changed since allowed_origins was set.

This can happen in a number of scenarios, for example, when uninstalling and re-installing a Chrome Extension.

Two options are either update to allowed_origins with the new origin, or to set a unique ID.