Chrome: " This extension may have been corrupted." when using a custom profile folder

This issue has been tracked since 2022-05-02.

I've been (maybe naively... ) trying to isolate Chrome by launching it with a custom folder by copying a "fresh" google-chrome folder into a unique folder then defining env variables. E.g.

export CHROME_CONFIG_HOME=$DIR/$UUID
export XDG_CONFIG_HOME=$DIR/$UUID
export XDG_CACHE_HOME=$DIR/$UUID
export CHROME_CACHE_HOME=$DIR/$UUID
export CHROME_USER_DATA_DIR=$DIR/$UUID/google-chrome

It works, using this procedure I can launch a "fresh" Chrome instance there is absolutely no connection with previous runs or smth all OK except... out of several extensions ( e.g. Canvas Defender, Random User-Agent) NoScript will unavoidably become "corrupted". After a few minutes of browsing, the icon disappears and if I look into extensions I can see that " This extension may have been corrupted."

I tried everything including an /etc/opt/chrome/policies/managed/00_gssapi.json where I define NoScript to be "force_installed". Nothing worked. I ran out of ideas and the problem remains trully annoying so... any ideas?

More Details About Repo
Owner Name hackademix
Repo Name noscript
Full Name hackademix/noscript
Language JavaScript
Created Date 2018-06-30
Updated Date 2022-12-03
Star Count 573
Watcher Count 21
Fork Count 79
Issue Count 151

YOU MAY BE INTERESTED

Issue Title Created Date Updated Date