The browser extension was not detected

[AJP]

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.

[jasminpatel]

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:

1. 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.

2. 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.

3. 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.

4. 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.

[john.hammond]

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.

[Tejaskumar_Darji]

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?

[monicab]

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