ContributionsMost RecentMost LikesSolutionsRe: Issues with new chrome UPDATE*** I have tracked down what my issue is. FOR ANYONE seeing the Red rectangle of death on the full browser window: I was using remote desktop to work on a scripting box that I do ALL of my ui testing on, so it doesn't destroy my local things. 12.5 with chrome, will not function this way. If I access the machine directly and run the exact same test, no problems. All other browsers work through Remote Desktop Connection.. 12.42 worked just great this way as well with all browsers, including chrome. So my question for the devs is, what changed with how we interact with chrome and 12.5? Re: Issues with new chrome Any progress with this? I'm on 12.5 and have had issues with chrome since updating. All other browsers work just fine. I've uninstalled and reinstalled, uninstalled and reinstalled the Chrome Extension. Object spy doesn't work, old tests can't recognize objects, it's garbage. Has anyone been given a solution? Re: Meet TestComplete 12.5 I'm also seeing the issues with Chrome 65 and TC 12.5 all other browsers function as expected.. I've uninstalled, deleted the Common Files folder where the extension lives, re-installed, removed/deleted the extension from chrome, manually added the new installed extension, enabled it. Still the issue persists. Unable to instrument the .apk application Hello, I recently received a new apk build from my dev. I have given him the most recent PatchServices.jar to build with, he has also ensured me that he is calling it in the OnCreate method, the app is also a debug build. By all accounts, this app has been instrumented for TC within it's build process. However, upon running, the app will crash stating that it was unable to be instrumented stating: "TestComplete did not find the needed classes in the package. Possible causes: • Your package was built with the Instant Run feature enabled. Currently, such packages are not supported. Turn Instant Run off and rebuild your package. • The package is not a UI application (for example, it is a service), and it does not contain elements for functional testing with TestComplete. TestComplete did not find the needed classes in the package. Possible causes: • Your package was built with the <a href="https://developer.android.com/studio/run/index.html#instant-run">Instant Run</a> feature enabled. Currently, such packages are not supported. Turn Instant Run off and rebuild your package. • The package is not a UI application (for example, it is a service), and it does not contain elements for functional testing with TestComplete." So I tried instrumenting the application manually in the TestedApps wizard. I got the most recent debug.keystore along with the correct alias and password/phrase. TestComplete also refuses to instrument stating the same error as above. I have confirmed that the build does not have "Instant Run" enabled. I have confirmed that this is definitely also a UI app (not service). I'm at a loss as to what to do next here. Version 12.31 Windows 10 SolvedRe: My app crashes when I tried to view the objects in the object tree I'm having the same issue.. oddly enough, object spy works fine on the landing page of the android application, after moving forward however, it will crash upon spying, the spy will in fact gather the data from the object in question, but the app crashes in the same instant. Anyone get around this? I instrumented the .apk through TestComplete UI, I have Android Agent installed, open to suggestions.. Re: aqReporter.dll Error Any solution for this? I too am getting the same error, TC freezes up and sits as the top program on the window, meanwhile you are unable to click anything, close anything, nada. After a good 5-10 minutes the error of "TestComplete has encountered a problem in module aqReporter.dll" comes up.