TestComplete not recognizing test extension after update to version 15.59
We've updated our local machines with TestComplete and TestExecute on our test servers running VMs.
Every instance is having issues recognizing the test extension for Edge and Chrome. I've tried uninstalling and adding them back in, but it still doesn't see it.
These tests were all working before the update. The one thing I've noticed is the browser version for Edge is 120, but the support page says its supported up to 118. However why would it work before but not after the update?
We don't have a way to roll back the version of the browser currently. So, if this is the issue, then I'm dead in the water until the browser support is brought up to the current version.
If this isn't the issue then I need some ideas on what it could possibly be. We do run our test with the InPrivate/Incognito browsers.
Any ideas are appreciated. I've kind run the course on figuring out why this is going on.
So I found a solution to get it to work, but now I'm having issues with the ClickItem method. But at least the browsers are recognized now. I'm currently working with support for the ClickItem issue.
The last section of this doc helped me find the solution - https://support.smartbear.com/testexecute/docs/working-with/extending/messages/chrome-extension-is-not-installed.html
The most important part was to add the Test Extension ID for each browser to the tcCrHost.json file.
"C:\Program Files (x86)\Common Files\SmartBear\tcCrExtension\<extension id folder>"
The interesting thing was I had two extension Id folders. I had to look in the registry to make sure I was updating the correct file by checking the path it was referring to.
For Chrome: "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\TestComplete12.Smartbear.Chrome.Extension"
Look for Microsoft\Edge in the same path as above to find that one. They say you only need one of them but if you have it in both I'd recommend checking both just to be sure.
The key value will show the path it is pointing to, to find the extension json file.
Hope this helps anyone dealing with this issue.