Hello, I am running a long running test on an android device. It takes a long time because our android application runs a long time... processing a lot of stuff. This is as designed. When I manually run this test on either a physical device or emulator, it runs just fine. I can process stuff along time (hours). Our app stays running indefinitely. But when I automate this using Rapise with Appium after a while our app just disappears. It doesnt appear to be crashing. What appears to be happening is that (without there being any failures triggered in the script, Appium is simply closing our application. Is there some sort of built-in time limit to how long a Rapise script can run? Appium continues running and connected to the device or emulator. I can restart the test if I want to. I have tried adjusting every wait and every delay and it doesnt seem to help. Thoughts? I had a different test, for a different android application where I discovered that eventually Appium was running out of memory and the test was aborting. But it was easy to tell this was happening by looking at the output in the Appium Console window. Thats not what is happening in this scenario. Appium keeps running and no specific Appium errors. I also tried saving a screenshot on failure, but that doesnt help. I just get a screenshot of my blank Android Desktop screen after the application was closed. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/rapise/issues-questions/2705.aspxthreadId=2705Kevin Miller (kmiller@raf.com)rapise android java appium memory timelimits Hello, I am running a long running test on an android device. It takes a long time because our android application runs a long time... processing a lot of stuff. This is as designed. When I manually run this test on either a physical device or emulator, it runs just fine. I can process stuff along time (hours). Our app stays running indefinitely. But when I automate this using Rapise with Appium after a while our app just disappears. It doesnt appear to be crashing. What appears to be happening is that (without there being any failures triggered in the script, Appium is simply closing our application. Is there some sort of built-in time limit to how long a Rapise script can run? Appium continues running and connected to the device or emulator. I can restart the test if I want to. I have tried adjusting every wait and every delay and it doesnt seem to help. Thoughts? I had a different test, for a different android application where I discovered that eventually Appium was running out of memory and the test was aborting. But it was easy to tell this was happening by looking at the output in the Appium Console window. Thats not what is happening in this scenario. Appium keeps running and no specific Appium errors. I also tried saving a screenshot on failure, but that doesnt help. I just get a screenshot of my blank Android Desktop screen after the application was closed. Mon, 07 Nov 2022 19:12:24 -05002024-01-15T06:44:30-05:00/Support/Forum/rapise/issues-questions/2705.aspxmessageId=5800David J (adam.sandman+support@inflectra.com) Hi Kevin Please could you log a support ticket. Thanks David Tue, 08 Nov 2022 01:13:14 -05002022-11-08T01:13:14-05:00/Support/Forum/rapise/issues-questions/2705.aspx#reply5800