So maybe you will have ability to take a look (if you will have time) at this configuration and start it from Studio itself, because I am not sure what is wrong there. Just do not click Stop button because this will remove temporary java class that is using in recording. Also you will be able to take a look at it, maybe you will find something wrong. So you will have ability to select this run configuration and start it again. So after clicking Record button you are receiving the error. If you will check it plugin will save RunConfiguration that is used to start recording in the list of your run configurations (each time when you click Record button). There is a checkbox 'leave Run Configuration used for recording'. If you open File > Settings menu, you can find 'Android Test Recorder' configuration under 'Other Settings'. If these numbers are the same your activity might be hogging the event queue.Īt .MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:362)Īt (InstrumentationTestCase.java:119)Īt (InstrumentationTestCase.java:97)Īt (ActivityInstrumentationTestCase2.java:104)Īt co.go.(AndrTestRec.java:19)Īt (TestCase.java:132)Īt $1.protect(TestResult.java:115)Īt .(AndroidTestResult.java:77)Īt (TestResult.java:118)Īt .(AndroidTestResult.java:55)Īt (TestCase.java:124)Īt .$n(NonLeakyTestSuite.java:63)Īt (TestSuite.java:243)Īt (TestSuite.java:238)Īt .(DelegatingTestSuite.java:103)Īt .(AndroidTestSuite.java:69)Īt .(JUnit38ClassRunner.java:90)Īt .runChild(Suite.java:128)Īt .runChild(Suite.java:27)Īt $3.run(ParentRunner.java:290)Īt $1.schedule(ParentRunner.java:71)Īt .runChildren(ParentRunner.java:288)Īt .access$000(ParentRunner.java:58)Īt $2.evaluate(ParentRunner.java:268)Īt .run(ParentRunner.java:363)Īt .run(JUnitCore.java:137)Īt .run(JUnitCore.java:115)Īt .(TestExecutor.java:54)Īt .AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:240)Īt I've upload new version of plugin to the site - There is a new feature. For your reference the last time the event queue was idle before your activity launch request was 1457688912786 and now the last time the queue went idle was: 1457688912786. Or the activity is doing network calls on creation? See the threaddump logs. Perhaps the main thread has not gone idle within a reasonable amount of time? There could be an animation or something constantly repainting the screen.

Class AndrTestRec extends ActivityInstrumentationTestCase2 within 45 seconds.

Error installing apk android studio 2.4