Forum Discussion

abidnaziri's avatar
abidnaziri
New Contributor
4 years ago

Chrome not detected as a browser object

When I try to access chrome while one of my projects is open, I can access chrome as a browser object (Sys.Browser("chrome")):

 

 

But after I try another one of my projects under a different project suit, it can't seem to detect it as a Browser: 

 

This problem persists when I write subroutines in the scripts under this project (I'm using VBScript for both projects). Even if I record a test using TestComplete and it generates a subroutine using the browser object, it can't run the subroutine later on.

Even if I open a new project under the project suite that's currently holding the problematic project, I can access the browser object. I can't seem to figure out what's different with this particular project that's stopping it from accessing the browser object. Could anyone give some possible reasons for this happening?

Chrome
Object Recognition

3 Replies

Sort By
  • BibekBehera's avatar
    BibekBehera
    Icon for Alumni rankAlumni
    5 years ago
    Copy Link

    Talsht 

     

    Please update delete and regenerate the api keys and give it a try.

    Also please send the data as  raw >>JSON, it should do the trick. 

     

    If you are still facing the same issue please feel free to create a support case and we will be happy to help you!

     

    -Bibek

     

    • Talsht's avatar
      Talsht
      New Contributor
      5 years ago
      Copy Link

      Hey,

      thank you for your reply.

      Sorry for the delay, I was away for the holidays.

       

      Well I tried following your solution and to delete and reapply a new key and to send as a raw json.

      I did not work however and I got the exact same result.

       

      What did work was adding the cycleId in the request data itself.

      From the documentation the cycleId is optional in the cloud API, however in the server API the cycleId is mandatory so this is where I got the inspiration to try it here as well.

       

      did not work:

      request = {"status": status, "projectId": project_id, "issueId": issue_id, "versionId": version_id}

      did work:

      request = {"status": status, "projectId": project_id, "issueId": issue_id, "versionId": version_id, "cycleId": "-1"}

       

      This has indeed solved the problem and you can now close the post.

       

      I do strongly suggest updating the documentation to reflect that the cycleId is indeed mandatory and not optional (or maybe change the request validation so the response is not an ambigious internal server error...)

       

      Sincerely,

    • abidnaziri's avatar
      abidnaziri
      New Contributor
      4 years ago
      Copy Link

      Thanks for replying, I was waiting for someone to hopefully be able to shed some light on this. Any updates on that?

      • abidnaziri's avatar
        abidnaziri
        New Contributor
        4 years ago
        Copy Link

        Hello, did anyone get a chance to look at this? It would be really helpful if someone could give me some pointers regarding this issue.