topic RE: The browser extension was not detected in Product Forum

The browser extension was not detected

AJP — Fri, 13 Jan 2023 05:27:00 GMT

Intermittently getting below error while launching and navigating through the chrome browser.

The browser extension was not detected, please check that it has been installed and enabled. For more information, see the browser extension user guide.
https://bpdocs.blueprism.com/bp-6-10/en-us/Guides/chrome-firefox/chrome-firefox.htm

It works sometimes and then starts failing for no reason. Has anyone encountered this and knows a solution?
BP Version - 6.10.1
Chrome extension - Blue Prism Extension 6.5 - 6.10 Manifest V3

Thanks.

RE: The browser extension was not detected

sumire — Fri, 13 Jan 2023 06:05:00 GMT

Hello @AJP ,

Sorry for not answering your question.
I'm using Edge and the same thing happens every so often.
I want to know the solution to this problem as well as you.

BP Version - 6.10.5

------------------------------
Mitsuko
Asia/Tokyo
------------------------------

RE: The browser extension was not detected

Prasanth_IRPA_Dev — Fri, 13 Jan 2023 06:37:00 GMT

Hi

In BP version 6.10.* are using ports => https://portal.blueprism.com/customer-support/support-center#/path/Upgrade-Expansion/Upgrade/1579866972/What-are-the-known-issues-in-Blue-Prism-Version-6-10-releases.htm

My suggestion is always to use the throttle or static wait after launching the browser (wait 10-15sec) and also after the kill the browser (wait 10-15sec) in Object Level. I checked with 12 sec now all is good

------------------------------
Thanks
Prasanth
Software Engineer | RPA Developer
------------------------------

RE: The browser extension was not detected

AJP — Fri, 13 Jan 2023 07:58:00 GMT

Thanks, Prasanth.

We have got some throttling in place but that might not be adequate. Let me increase that to see if it makes any difference.

Thanks again.

------------------------------
AJP
------------------------------

RE: The browser extension was not detected

_Amlansahoo — Mon, 16 Jan 2023 05:35:00 GMT

This issue will come if you are not selected the "Browser Fixed Port" settings. I have faced the same issue.
If you have multiple browsers open at the same time then this issue used to come, Once you select that option this issue will not appear.
There are a few drawbacks on selecting that option but this option will only fix that issue.

------------------------------
Amlan Sahoo
Senior RPA Consultant
WonderBotz
------------------------------

RE: The browser extension was not detected

Tejaskumar_Darji — Mon, 16 Jan 2023 05:44:00 GMT

Honestly saying I also could not find any proper solution to this, the fixed port checkbox is suggested in the KB article but even with that box checked I have seen this issue keep appearing on my machine as well as on the other 2 colleagues.

We also tried the delay thing to wait before and after the browser but that also could not rule out the issue.

Earlier I faced this in 6.10.4 so updated it to 6.10.5 and it worked fine for a couple of weeks and then again it started.

------------------------------
If I was of assistance, please vote for it to be the "Best Answer".

Thanks & Regards,
Tejaskumar Darji
Sr. Consultant-Technical Lead
------------------------------

RE: The browser extension was not detected

PvD_SE — Mon, 16 Jan 2023 07:41:00 GMT

Hi,

Perhaps far fetched but I give it a try anyway:
Could it be that you have two instances of the browser (Chrome) installed on you PC (or VDI)? One instance in .../Program Files/... and the other in .../Program Files (x86)/... and only one of them having the BP plugin installed?

------------------------------
Happy coding!
---------------
Paul
Sweden
------------------------------

RE: The browser extension was not detected

AJP — Tue, 17 Jan 2023 03:23:00 GMT

Thanks for the responses.

As of now, I have increased throttling to 15 seconds which was set to 5 seconds earlier, and have not encountered the issue yesterday. Perhaps, I will wait for a couple of more days to confirm if that works as the issue was intermittent.

------------------------------
AJP
------------------------------

RE: The browser extension was not detected

NileshJadhavBP — Tue, 17 Jan 2023 14:45:00 GMT

Hi @AJP

We had faced same issue and found that the edge is connecting to blue prism browser port.

Please kill msedge.exe before launch Chrome.

Please let me know if its work with you or not.

------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

RE: The browser extension was not detected

MahalakshmiPadm — Mon, 03 Apr 2023 13:43:00 GMT

Hi All,

I have tried all the above mentioned possibilities, but still no luck.
BP Version - 7.1.2
Chrome and Edge same version only.
Please let me know if any possible solution for this issue.

------------------------------
Mahalakshmi Padmanabhan
------------------------------

Re: The browser extension was not detected

jasminpatel — Wed, 10 Jul 2024 09:27:08 GMT

Yes, this is a reported issue with Blue Prism and Chrome browser extension using Manifest V3. Here's what you might be facing:

Manifest V3 incompatibility: Chrome and Edge browsers are phasing out Manifest V2 extensions in favor of Manifest V3. The Blue Prism Extension 6.5 - 6.10 uses Manifest V3, which might have limitations compared to V2.
Intermittent detection: Manifest V3 extensions might have limitations in communication between the browser and Blue Prism, leading to occasional detection failures.

Here are some solutions you can try:

Check Blue Prism Community: Several users have reported this issue on the Blue Prism community forums. Search for "The browser extension was not detected" to see if there are any updates or workarounds mentioned.
Upgrade Blue Prism (if possible): Blue Prism versions 7.2 and above (for version 7) and 6.10.6 and above (for version 6) include the Browser Automation Agent by default. This agent offers improved browser interaction compared to the Manifest V3 extension. Upgrading Blue Prism might resolve the issue if compatible with your system.
Use the Manifest V2 Impact Assessment Utility: Blue Prism offers a utility to identify if your automations rely on features not supported by Manifest V3 extensions. This can help you plan your upgrade strategy or identify areas needing adjustments.
Contact Blue Prism Support: If none of the above solutions work, consider contacting Blue Prism support for further assistance. They might have additional insights or recommendations specific to your environment.

Re: The browser extension was not detected

john.hammond — Fri, 01 Nov 2024 09:57:28 GMT

Has there been any further update with this issue? We're currently running 6.10.5 and have noticed an uptick in instances of this over the past month or so. As other contributors have discussed, all suggestions (Fixed Port, Reboots, Increased throttling) have - at best - mixed success rates, and the issue is still occurring frequently enough for this to become a more significant issue.

Just to clarify, we're having this issue with both Edge and Chrome-based automations.

Re: The browser extension was not detected

Tejaskumar_Darji — Wed, 11 Dec 2024 11:18:27 GMT

I’m revisiting this thread as some colleagues are still encountering this issue in version 7.3.1.

The release notes for the new 7.4 version don’t indicate that this issue has been addressed, so upgrading isn’t a viable solution at this time for this issue.

Error: The Browser Extension could not be detected

All the resolutions suggested in the KB article, as well as those from other community members, have already been tried.

Is anyone else still experiencing this problem with browser automations?

Re: The browser extension was not detected

monicab — Fri, 13 Dec 2024 09:47:25 GMT

Yes. We are using 7.2.1 and this issue suddenly returned today.

Re: The browser extension was not detected

Nandhakumar — Fri, 03 Jan 2025 03:37:37 GMT

We are using 6.10.5 and facing the same issue.

Failed to perform step 1 in Navigate Stage 'Launch' on page 'Launch App New' - The browser extension was not detected, please check that it has been installed and enabled. For more information, see the browser extension user guide.

Re: The browser extension was not detected

jared.ayson — Tue, 25 Feb 2025 15:59:26 GMT

do we have solution to this? i am also encountering this with 7.0 version.

Re: The browser extension was not detected

michaeloneil — Wed, 26 Feb 2025 20:14:32 GMT

hi @AJP

I've had a similar issue before and it was during launch but the edge opened fine with the correct site so i just added in exception handling for this to catch the error at the launch stage, recover and then attach. This worked to keep the process moving without continual failures. I should also note this issue was resolved in the newer versions of blueprism so if its an option I would suggest upgrading to the latest version.

Re: The browser extension was not detected

Luis_Rios — Wed, 26 Feb 2025 21:22:47 GMT

Hi, do you have solution to this? I'm also encountering this with 7.4 version.

Re: The browser extension was not detected

stepher — Fri, 28 Feb 2025 16:32:13 GMT

Good morning, All,

The Blue Prism browser extensions for 6.10.x and 7.x.x are supposed to be very different, so I think this might be a conflation of issues here.

In 6.10.x, the 'The browser extension was not detected,' is a known issue. It seems to occur when there has been insufficient time between the termination of one instance of MS Edge and the initialization of the next (on the same machine). We are currently on 6.10.2 and have seen a significant increase in this error, but we have also made changes to certain processes that make this more likely. We are still working on addressing this.
There have been a number of reported issues with 7.x where the 'Launch' process times out because the BP extension does not load in time. We are currently in testing for 7.3.1 (but likely will go to 7.3.2). Our solution has been to use a 'Start Process' and 'Wait for Process Window' approach. This is very similar to the approach @michaeloneil states.

I can try to connect at least one of the Launch/Start Process threads in a separate reply.

Take care,

Red

Re: The browser extension was not detected

stepher — Fri, 28 Feb 2025 16:59:40 GMT

To follow up. The link below connects to a more in-depth discussion of the trials and tribulations of MS Edge in version 7.x.

https://community.blueprism.com/t5/Product-Forum/Native-Messaging-Host-Blueprism-MessagingHost-exe-launch-delay/m-p/117433#M52482

Take care,

Red