Chrome Extension Issue

[AidanMcArdle]

There are many threads existing on this topic, yet none seem to contain a workable solution. I see one with responses from six days ago, but it is suggested to start a new thread.
I have also tried support tickets to no avail.

This has become high-priority for us now that IE has reached end-of-lifecycle. We are currently migrating all processes from IE to Chrome and this issue has gone from occasional minor irritation to high priority. We are currently at a point of breakage where moving the entire system to a UIPath is being mentioned.



Issue: Blue Prism returns error: 'Chrome browser extension not detected' intermittently.
Extension is installed and enabled.
From what I can tell, this is due to the port connection not being correctly severed, and therefore a new connection on the same port causes confusion in the app.


Suggested solutions trialled so far;
1) Increase wait time after closing chrome.
Result: 6 seconds or 60, issue can persist.

2) Ensure fixed port is selected in Blue Prism settings (or not).
Result: We have seen the error continue whether port is set as fixed or variable.

3) Ensure Chrome setting 'Continue running background apps when Chrome is closed' is turned off.
Result: Issue persists.

4) Exit gracefully via Chrome hamburger & 'exit'. OR Exit ungracefully using 'X' to close, followed by killing Chrome process via utility/task manager.
Result: These both close all instances of chrome. Unworkable in a process with multiple (up to four) systems open in Chrome at once.

5) Await updated version of Blue Prism (Current version 6.10.2) 
Result: The issue has been present for multiple versions now and still persists. 

6) Restart Automate.exe OR robot VM. 
Result. These do work! But are also unworkable for obvious reasons. Stepping in manually 20+ times per day (or night) is not feasable.



Can anyone assist? I'm reaching the end of my tether with this bug.

[rsrivastava2]

Hi Mate,

Please refer to How to fix Chrome Edge Blue Prism extension issue

Hope this helps,
Regards

------------------------------
WeitghtRPAMatey
------------------------------

[jasminpatel]

Hey there! I can't say exactly what works everywhere, but here's what I understood from those tips:

The Problem:

Sometimes, browser extensions can act weird. This might happen because:

The extension tries to connect to Chrome too early, before Chrome is fully ready. Imagine you're trying to talk to a friend who's still starting their computer – they might not hear you right away!

When you just close Chrome by clicking the "X", leftover files (like temporary notes) might stick around and cause problems next time you open it. It's like leaving dirty dishes in the sink – they might make your next meal prep a mess!

The Tips:

The tips shared a way to potentially fix these issues using a special program called PowerShell (think of it like a fancy toolbox). Here's what it might be doing:

Making the Extension Wait: It tells the extension to wait a bit before trying to connect to Chrome, giving Chrome more time to get going. This is like giving your friend a few minutes to boot up before you call.

Closing Chrome Nicely (Maybe): It runs a command that tries to close all Chrome windows properly. This could also involve clearing out those leftover files, like cleaning the dishes before the next meal.

Important Things to Remember:

Closing Chrome Abruptly: Be careful! Forcing Chrome shut (like with that CloseMainWindow() thing) might make you lose any work you haven't saved yet. It's like yanking the plug out of your computer – not good!

Is There a Better Way?: There might be other tools that can help manage extensions without messing with closing Chrome. These could be like special switches on your fancy toolbox that work better for extensions.

This Might Not Work Everywhere: These tips might work for this specific setup, but they might not work for everyone. Like different tools work better for different jobs!

I hope this explanation makes things a bit clearer! Feel free to ask if you have any more questions

[jasminpatel]

Hi there,

It sounds like you've already tried a comprehensive range of solutions, and I can understand how frustrating this issue must be. Given that the error persists despite your efforts, I would recommend a couple of additional steps:

1. Check for Extension Updates: Ensure that both Blue Prism and the Chrome extension are up-to-date. Sometimes, compatibility issues are resolved in newer versions.

2. Review Logs and Error Messages: Look into the logs from both Blue Prism and Chrome. There might be specific error messages or patterns that could provide more insight into the root cause.

3. Consult Blue Prism Support: Since this issue has become critical, it may be worthwhile to escalate it within Blue Prism support for a more focused investigation. Providing detailed logs and steps you've already tried could help expedite the process.

4. Explore Alternative Automation Solutions: As a last resort, if the issue remains unresolved and significantly impacts your operations, considering other automation tools like UIPath, as you mentioned, could be a viable option.

I hope this helps, and best of luck with resolving the issue and please read my blog on create a chrome extension