Ranorex 9 Beta
There is shown this technological warning when using Spy....but not every time
Chrome: Version 72.0.3626.119 (Official Build) (64-bit)
When checked from Chrome, there are installed extensions v 1.2.4 and 1.2.3
There is no "Remove" option
When trying to add extension manually:
Failed to load extension
File
C:\Program Files (x86)\Ranorex\Studio Beta\Ranorex Chrome Extension
Error
Ranorex Automation (extension ID "egdlgaljianpgdlmfijpphbadibfncdm") is blocked by the administrator.
Could not load manifest.
Should I uninstall Chrome totally to get this working again?
Chrome extension problems
Re: Chrome extension problems
Hi,
We discussed a similar (if not the same) problem here:
error-loading-chrome-extension-in-9-0-t ... tml#p52986
Try to uninstall extension using Ranorex instrumentation wizard. There is definitely something wrong with chrome plugin. I had to repeat this uninstall/install process several times.
We discussed a similar (if not the same) problem here:
error-loading-chrome-extension-in-9-0-t ... tml#p52986
Try to uninstall extension using Ranorex instrumentation wizard. There is definitely something wrong with chrome plugin. I had to repeat this uninstall/install process several times.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
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
-
- Posts: 6
- Joined: Fri Oct 09, 2015 7:45 pm
Re: Chrome extension problems
I had the same problem when upgrading from Ranorex 8.3 to 9.2. Chrome simply wouldn't work and I saw the same error message shown in the original post.
In short, I was only able to fix it after I uninstalled Ranorex completely, rebooted, then reinstalled. This shouldn't have been necessary, but I'm posting it here so other affected users can have the same workaround.
In short, I was only able to fix it after I uninstalled Ranorex completely, rebooted, then reinstalled. This shouldn't have been necessary, but I'm posting it here so other affected users can have the same workaround.