Bug: v3.13.1 (stable) & v3.14.1b doesn't automatically load in chrome

[metapea]

When starting in chrome AdNauseam doesn't automatically load
It has to loaded from "load unpacked" with the extension folder in order to be detected and it's work fine afterwords (v3.13.1) until you close the browser, where you have to repeat the same thing when you start up the browser again
I never had this problem in earlier versions like v3.13.0.

[sl1pkn07]

same here in chromium dev channel

[Jesuis33]

Did you guys managed to find solution

[metapea]

No

[mneunomne]

I missed this in this release candidate testing. I will try to fix it asap. thank you for the feedback!

[mneunomne]

Seems that there is an issue with chrome because we changed the "key" in manifesto...

@metapea @sl1pkn07 @Jesuis33 If you just change adnauseam.chromium folder location, and unpack it once again, it should go back to detecting and keeping adnauseam installed in chrome. At least that's what worked for me.

My suspicion is that changing the "key" created some kind of issue in chrome folder management for the extension, I tried changing it back to the old key but still it keeps having this issue, I went back many versions before and still the folder dist/build/adnauseam.chromium doesn't get automatically detected like before.

@dhowe not sure how to proceed with this one now, I will try to fix it, but perhaps the users who unpacked these last 2 version will face this issue and have to change folder.

[mneunomne]

(installing the unpacked on a different browser profile also worked for me)

[mneunomne]

This is fixed with the latest release, closing