C-Hansen
Occasional Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Testcomplete not "see" object of Android app in "Object Browser" after "adb shell am force-stop"
Thank you NikitaPyatakov. That gives me an idea about the cause but what about the solution? Is the only solution to reinstall the app then or did you get any information on this? For example: Can you call an ADB command with the prefix, add the prefix in the parameter to the LaunchPackage method or something? Otherwise I would at least like a way from TestComplete to launch the app in the needed state without reinstalling it.1.8KViews0likes3CommentsRe: Testcomplete not "see" object of Android app in "Object Browser" after "adb shell am force-stop"
Hi everyone, Have you figured out a solution to this problem or have you heard from Smartbear, because I was thinking about opening a support ticket about this issue. There is definitely something that has changed, with the new way instrumentation works in 14.70 and 14.71. At least I didn't have the issue on 14.61 and before that. We have used the adb force-stop command for a long time followed by LaunchPackage method without any issues, but now we have noticed the same thing as described by OP. After a force-stop the only way of getting TestComplete to notice the objects again seems to be to reinstall the app. Not even manually opening the app on the phone works. However I've also seen the issue without actively doing a force-stop command. Before I could instrument the app and it would just work. I could go a whole work day debugging and testing on that app. However now I notice that I often need to reinstall the app because TestComplete can't see the objects. I'm not sure when it happens, might be after a crash of the app, the system killing the app by itself or something else. After it happens there seem to be no way of launching the app again without a reinstall. Thanks.1.8KViews0likes5CommentsRe: TestComplete(14.20) stops responding when connecting to Android device
I've tried updating to 14.20 again. Now it suddenly works. I suspect that our companies safety policies and Windows Defender might have something to do with it. I could see that the process was using a lot of resources the last time I installed 14.20. Now it’s not and it works. Case closed.2.1KViews1like0CommentsTestComplete(14.20) stops responding when connecting to Android device
Hi, I've been using TestComplete 12 and now 14 to test on Android with no issues. However after updating to TestComplete 14.20 yesterday I ran into problems and was wondering if anyone has seen something similar? As soon as I connect to an Android device, TestComplete stops responding for around 5 seconds. When it starts responding and I click to do an action on the phone, TestComplete stops responding again for 5-10 seconds. This behavior will continue until I close the mobile screen window. When running an Android test without having the mobile on screen it is also super slow an unresponsive. Some steps like for example opening the app on the device will take 1-2 minutes. All this is even before I open the instrumented app on the phone. When I do that, the behavior is the same. iOS runs normally. I've tried the following: Using a different phone, both running Android 9 though Updating the Android platform tools (Wondered if it was a problem with ADB but it seems to run fine. The screen sharing program Vysor for Android also runs as usual.) Connecting to a phone without a TestComplete project open I've downgraded to TestComplete 14.10, so I can continue working and it runs all fine again. Any suggestions? Thanks in advance.Solved2.1KViews0likes2Comments