Not Compitable with Chrome extension MV3

[nirvparekh]

Getting error in Gmail from content script.
`contentScript.bundle.js:54998 Error logged: EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self'".

at eval (<anonymous>)
at contentScript.bundle.js:54820 

Original error stack:
EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self'".

at eval (<anonymous>)
at chrome-extension://ipjpliddiedabogjnnnkaojcfaiccbdm/contentScript.bundle.js:54820:27 

Error logged from:
at logError (chrome-extension://ipjpliddiedabogjnnnkaojcfaiccbdm/contentScript.bundle.js:54976:56)
at chrome-extension://ipjpliddiedabogjnnnkaojcfaiccbdm/contentScript.bundle.js:54861:38

Error details: {url: 'https://www.inboxsdk.com/build/platform-implementation.js', connectivityTestResults: {…}, status: undefined, response: null, message: 'Failed to load script'}`

[Macil]

The InboxSDK doesn't support MV3 yet because of its current reliance on remote loading code. There's some information here about it: https://groups.google.com/g/inboxsdk/c/ho69zTWjxgM/m/PhrWenZcAQAJ. The InboxSDK will be MV3-compatible before it becomes required by Chrome.

[nirvparekh]

The InboxSDK doesn't support MV3 yet because of its current reliance on remote loading code. There's some information here about it: https://groups.google.com/g/inboxsdk/c/ho69zTWjxgM/m/PhrWenZcAQAJ. The InboxSDK will be MV3-compatible before it becomes required by Chrome.

Thanks @Macil for the update;

[MalikElate]

that's unfortunate

[aleemstreak]

@MalikElate this is no longer the case, the InboxSDK now supports MV3

[mayurfefar]

@aleemstreak Can you let me know what is required for inboxSDK v2. i am getting same error

[ramanjoshi90]

@tiagorangel2011 Did you get any solution for that? I am getting the same error no Gmail when I use the latest inbox SDK and load extension from my local machine.

[Lonolf]

We got the same error on our Beta (v130) and Canary (131) version. Updated InboxSDK to the last version.
Still working on the production channel.
Can you give us some help? Thanks!