Ranorex Plugin will not persist on Chrome or EdgeChromium

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
Posts: 34
Joined: Mon Sep 24, 2012 9:45 pm
Location: Kansas City

Ranorex Plugin will not persist on Chrome or EdgeChromium

Post by kdreiling » Wed Jun 30, 2021 11:41 pm

The Ranorex Plug in will not persist on Google Chrome and keeps falling off the browser. I consistently have to use the wizard to re-attach the plug in.

EdgeChromium does retain the plug in, but when the browser is opened, a pop-up "Disable developer mode extensions displays". This causes automation to fail if the test case happens to need to click behind that pop-up, which it does often.

I have tried using this link to resolve the issue, but am unable to Pack the extension because the "Private Key" although is supposed to be optional is required: https://techjourney.net/remove-disable- ... rome-edge/

We do not have the ability to change the registry settings on our VDI's, so do I need to have our infrastructure team change the registry settings?

If you have experienced this situation, how did you resolve it, and if you have any links that I could pass on to our technical team, I would appreciate it.

Thanks in advance for any information you can share.

User avatar
Ranorex Guru
Ranorex Guru
Posts: 7469
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Ranorex Plugin will not persist on Chrome or EdgeChromium

Post by odklizec » Thu Jul 01, 2021 9:49 am


Is there a reason, why you are trying to run Ranorex tests on Edge with enabled Developer mode? I believe that normal users will not run browser in a dev. mode? So it would be better to run automated tests in non-dev mode as well. Simply disable the Developers mode and you should not see the warning?

As for the persistence and stability of Chrome/Edge plugin, I agree that this plugin is not the best example of stability ;) However, I found that most of the issues are caused by enabled Chrome/Edge process running on background, eventually, if Chrome and Edge are running at the same time. This is a big No-No!

But yes, Chrome plugin definitely needs an overhaul. There is just too many problems reported by users, so it's not a coincidence. Plus it seriously slows down the tests, by number of errors and warnings reported in log.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration