Forum Discussion

sgarcia's avatar
sgarcia
Contributor
11 months ago

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 uni...
  • sgarcia's avatar
    sgarcia
    10 months ago

    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. 

    Example json:

    Hope this helps anyone dealing with this issue. 

BreezerK's avatar
BreezerK
Occasional Contributor
10 months ago

I am surprised this isn't getting any more traction and that more people are not having issues.

We are also staying on 15.58 as well for the same reasons. The extension doesn't seem to work properly. TC is unable to recognize objects on screen anymore. 

I also assume it is related to Manifest v3 (I told my teams to assume any testing we plan for June will be delayed since that is when Manifest v3 is planned to go live. I do not have faith TestComplete will be working well in time).

This reminds me of the Chromium 113 issues 8-9 months ago where object recognition was all messed up because Manifest v3 stuff was added (and then rolled back).

  • Michael_B's avatar
    Michael_B
    Occasional Contributor
    10 months ago

    That jogs my memory. I remember rolling everyone back to Edge v112 after our monthly updates rolled. I'm going to try SGarcia's fix and see if it helps.

    • Michael_B's avatar
      Michael_B
      Occasional Contributor
      10 months ago

      A question for anyone who sees this issue. Do you have strict security/group policies to control browser extensions? The KB points to this extension URL which is the extension we are allowing via GP: 


      But it looks like there is a newer version. I'm going to update our GP with this version and see if that fixes the issue. Will report back. Its weird though. If I search all extenstions for this ID, it does not seem to come up. https://microsoftedge.microsoft.com/addons/detail/smartbear-test-extension/hlicljijpmhapnbjeddcmimplcalfkic 

      • Michael_B's avatar
        Michael_B
        Occasional Contributor
        10 months ago

        Ya - I was shooting us in the foot with my group policy. I'll work with my team on a cutover. I reached out to SmartBear to update the KB. Thanks for your time on this everyone.