Getting "This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions" on extension page

[mattsmith321]

I've been using the MultiPass extension successfully for a while now to deal with basic authentication prompts in my Selenium testing. It has worked great. It has even worked great in a Selenium Grid environment. Until today.

Now I am getting the following error when trying to run my test cases against Selenium Grid in headless mode:

System.InvalidOperationException : Could not start a new session. 
Could not start a new session. 
Error while creating session with the driver service. 
Stopping driver service: Could not start a new session. 
Response code 500. Message: session not created: failed to wait for extension background page to load: 
chrome-extension://enhldmjbphoeibbpdhmjkchohnidgnah/_generated_background_page.html
from unknown 
error: page could not be found: chrome-extension://enhldmjbphoeibbpdhmjkchohnidgnah/_generated_background_page.html 

Interestingly, the test cases pass when running in non-headless mode on Selenium Grid. And they pass locally in both headless and non-headless mode.

I do see on the Chrome extension download page the following message:

This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions.

I see the extension hasn't been updated in a while so not sure if this will get picked up. I may have to see if there are other options out there.

[krtek4]

Hi,

Hadn't really had time to migrate to manifest v3, tried it beginning of the year but there was some issues with the upload.

I'll try to make a fix this week and let you know.

[mattsmith321]

Sweet! Thanks for the prompt response. Looks like this was happening on Chrome v128. I've upgraded to v129 locally and everything still seems fine locally.

Side note that I don't think is related to the extension: When running locally in headless mode now, a blank window will pop up for each of my tests. This was not happening previously. It doesn't even put an icon in the task bar, just pops up a completely blank square on the screen with no indication it is Chrome or anything. And then closes when the test completes.

[mattsmith321]

Fingers crossed that you can get it resolved. I spent all day yesterday looking at alternatives such as HasAuthentication (not available in the Selenium dotnet version) and using Chrome Dev Tools using CDP but ran into issues no matter which way I went. I even tried updating the extension locally and trying to deal with it unpacked but Chrome didn't like that at all.

[mattsmith321]

Well, the good news is that apparently our issues are not due to the manifest v3 issues. Something odd happened on our Selenium Grid servers. Not sure if something happened to tests while they were running or if TI made some changes or what. I went back through the servers, rebooted them all, and re-installed Chrome and now everything seems to be working again. Very odd, especially since I rebooted and saw Chrome get updated yesterday.

So, I still hope you can get MultiPass updated so that there aren't issues down the road. It's definitely been the easiest option to deal with our legacy Basic Authentication prompts.

[krtek4]

So, the end of my week was a bit more ectic than planned, but I managed to upload a new version today.

It's currently pending review, since the way an extension gets permissions changed I had to make a few change.

Fingers crossed everything will be fine.

[mattsmith321]

So, the end of my week was a bit more ectic than planned, but I managed to upload a new version today.

It's currently pending review, since the way an extension gets permissions changed I had to make a few change.

Fingers crossed everything will be fine.

Looks like it hasn't been approved yet.

On another note, any interest in putting together an Edge version?

[krtek4]

Hello,

Some family emergences have come up and I hadn't had the time to finish the migration.

There is apparently an error with in the extension itself which isn't working well anymore. I'll need to set up some kind of test environement to debug it.

Concerning Edge, don't know if something particular needs to be done ? I was under the impression that any chrome extension could be installed ? is there a specific store ?

[mattsmith321]

No worries on the timing. As I mentioned in one of my responses, I'm actually good to go for now and it turns out there wasn't a real issue on my end.

Good question about Edge. I was wondering if Chrome extensions would work since they are both based on Chromium. I will have to experiment and find out. I'll get back to you at some point and let you know.

Hope all is well with the family.

Thanks, Matt

On Wed, Oct 30, 2024 at 12:13 PM Gilles Crettenand @.***> wrote:

Hello,

Some family emergences have come up and I hadn't had the time to finish the migration.

There is apparently an error with in the extension itself which isn't working well anymore. I'll need to set up some kind of test environement to debug it.

Concerning Edge, don't know if something particular needs to be done ? I was under the impression that any chrome extension could be installed ? is there a specific store ?

— Reply to this email directly, view it on GitHub https://github.com/krtek4/MultiPass/issues/106#issuecomment-2447845261, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOXAEUKKQ27KV4PNGXMPEDZ6EHT3AVCNFSM6AAAAABONUQEIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBXHA2DKMRWGE . You are receiving this because you authored the thread.Message ID: @.***>

[mattsmith321]

Very cool. I was able to manually add the Multipass extension to Chrome. The challenge I will have to look into later is seeing if I can use WebDriver to drive Chrome and install the extension programmatically like I am doing for Chrome now. That will be an experiment for another week though.

Thanks for the tip!

On Wed, Oct 30, 2024 at 1:36 PM Matt Smith @.***> wrote:

No worries on the timing. As I mentioned in one of my responses, I'm actually good to go for now and it turns out there wasn't a real issue on my end.

Good question about Edge. I was wondering if Chrome extensions would work since they are both based on Chromium. I will have to experiment and find out. I'll get back to you at some point and let you know.

Hope all is well with the family.

Thanks, Matt

On Wed, Oct 30, 2024 at 12:13 PM Gilles Crettenand < @.***> wrote:

Hello,

Some family emergences have come up and I hadn't had the time to finish the migration.

There is apparently an error with in the extension itself which isn't working well anymore. I'll need to set up some kind of test environement to debug it.

Concerning Edge, don't know if something particular needs to be done ? I was under the impression that any chrome extension could be installed ? is there a specific store ?

— Reply to this email directly, view it on GitHub https://github.com/krtek4/MultiPass/issues/106#issuecomment-2447845261, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOXAEUKKQ27KV4PNGXMPEDZ6EHT3AVCNFSM6AAAAABONUQEIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBXHA2DKMRWGE . You are receiving this because you authored the thread.Message ID: @.***>

[mattsmith321]

Sweet! It worked. I had to make code changes to set ChromeOptions and EdgeOptions independently and pass those to the driver accordingly. But I was able to use the existing code to launch with without any issues:

        protected void AuthenticateViaMultipass(string url, string username, string password)
        {
            _driver.Url = "chrome-extension://randomextensionkey/popin.html";
            _driver.FindElement(By.Id("url")).SendKeys(url);
            _driver.FindElement(By.Id("username")).SendKeys(username);
            _driver.FindElement(By.Id("password")).SendKeys(password);
            _driver.FindElement(By.XPath("//button[.='Add']")).Click();
        }

Thanks for the tip and thanks for the extension! It is allowing us to continue to push out moving away from basic auth even longer! 😉

[d4rky-pl]

@krtek4 I'm afraid Chrome is now disabling the extension because they conveniently forgot to tell everyone Jan 1st 2025 is the deadline 🤦

Any chance the Manifest v3 version gets released any time soon? 🙏

[krtek4]

Hey,

The current stat is that the extension was rejected because it didn't do what it was supposed to according to the message I received.

I imagine I must have messed something up when trying to adapt it to v3.

I'll probably have some time this weekend to try to check and fix this, I'll keep you posted.

In the meantime if someone wants to try fixing it I'll gladly accept a PR. Explanation in the readme should be enough to start hacking.

Happy new year everyone ;)

[krtek4]

So, I took the time to configure a test bed, tested the extension and.... it worked.

I tried having a look on the developer dashboard if I could appeal the rejection, but found nothing so I tried submitting the same version again.

If anyone knows if an appeal can be made ?

It this doesn't work, I'll try to rework the wording leading to the rejection ( https://developer.chrome.com/docs/webstore/troubleshooting/#deceptive-behavior )

[krtek4]

While waiting for approval on the store, I published a new release here : https://github.com/krtek4/MultiPass/releases/tag/v1.0.0

You can take the zip file and manually install it inside Chrome. You need to unzip the file somewhere, switch to developer mode in chrome://extensions/ and then add an unpacked extension.

[krtek4]

Hey everyone, closing this since it seems that my last publishing try was successful.