java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x14000000 cmp=com.COMPANY.espresso/com.COMPANY.activity.LauncherActivity } within 45 seconds. 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. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1469050322683 and now the last time the queue went idle was: 1469050322683. If these numbers are the same your activity might be hogging the event queue.

  1. 0

    Android/Espresso Intent error on running tests

    Stack Overflow | 5 months ago | Skycamefalling
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x14000000 cmp=com.COMPANY.espresso/com.COMPANY.activity.LauncherActivity } within 45 seconds. 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. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1469050322683 and now the last time the queue went idle was: 1469050322683. If these numbers are the same your activity might be hogging the event queue.
  2. 0

    Could not launch intent Intent

    GitHub | 1 year ago | charbgr
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x14000000 cmp=com.example.android.testing.espresso.BasicSample/.MainActivity } within 45 seconds. 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. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1442838884986 and now the last time the queue went idle was: 1442838884986. If these numbers are the same your activity might be hogging the event queue.
  3. 0

    GitHub comment 760#183938845

    GitHub | 10 months ago | ifoche
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=org.eyeseetea.malariacare.hnqispull/org.eyeseetea.malariacare.LoginActivity } within 45 seconds. 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. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1455469811840 and now the last time the queue went idle was: 1455469819094. If these numbers are the same your activity might be hogging the event queue.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 760#183948959

    GitHub | 10 months ago | ifoche
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=org.eyeseetea.malariacare.hnqispull/org.eyeseetea.malariacare.LoginActivity } within 45 seconds. 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. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1455475206572 and now the last time the queue went idle was: 1455475213092. If these numbers are the same your activity might be hogging the event queue.
  6. 0

    Application choosers - Android Espresso unit tests breaking after opening external URL

    Stack Overflow | 8 months ago | Combuster
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=nl.test.example/.ui.activity.login.LoginActivity_ } within 45 seconds. 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. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1461252979050 and now the last time the queue went idle was: 1461252979050. If these numbers are the same your activity might be hogging the event queue.

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.RuntimeException

      Could not launch intent Intent { act=android.intent.action.MAIN flg=0x14000000 cmp=com.COMPANY.espresso/com.COMPANY.activity.LauncherActivity } within 45 seconds. 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. Or the activity is doing network calls on creation? See the threaddump logs. For your reference the last time the event queue was idle before your activity launch request was 1469050322683 and now the last time the queue went idle was: 1469050322683. If these numbers are the same your activity might be hogging the event queue.

      at android.support.test.runner.MonitoringInstrumentation.startActivitySync()
    2. android.support.test
      ActivityTestRule$ActivityStatement.evaluate
      1. android.support.test.runner.MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:360)
      2. android.support.test.rule.ActivityTestRule.launchActivity(ActivityTestRule.java:219)
      3. android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:268)
      3 frames
    3. JUnit
      JUnitCore.run
      1. org.junit.rules.RunRules.evaluate(RunRules.java:20)
      2. org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
      3. org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
      4. org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
      5. org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
      6. org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
      7. org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
      8. org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
      9. org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
      10. org.junit.runners.ParentRunner.run(ParentRunner.java:363)
      11. org.junit.runners.Suite.runChild(Suite.java:128)
      12. org.junit.runners.Suite.runChild(Suite.java:27)
      13. org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
      14. org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
      15. org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
      16. org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
      17. org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
      18. org.junit.runners.ParentRunner.run(ParentRunner.java:363)
      19. org.junit.runner.JUnitCore.run(JUnitCore.java:137)
      20. org.junit.runner.JUnitCore.run(JUnitCore.java:115)
      20 frames
    4. android.support.test
      AndroidJUnitRunner.onStart
      1. android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
      2. android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262)
      2 frames
    5. Android Platform
      Instrumentation$InstrumentationThread.run
      1. android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1862)
      1 frame