java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=com.godaddy.gdm.SettingsActivity } 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 1486944041826 and now the last time the queue went idle was: 1486944049404. If these numbers are the same your activity might be hogging the event queue.

Stack Overflow | satyajit | 1 month ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    GitHub comment 760#183976813

    GitHub | 1 year 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. at > android.support.test.runner.MonitoringInstrumentation.startActivitySync(MonitoringInstrumentation.java:362) at > android.support.test.rule.ActivityTestRule.launchActivity(ActivityTestRule.java:219) at > android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:255)
  2. 0

    Google firebase showing Chrome first UI that is blocking other tests

    Stack Overflow | 1 month ago | satyajit
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=com.godaddy.gdm.SettingsActivity } 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 1486944041826 and now the last time the queue went idle was: 1486944049404. If these numbers are the same your activity might be hogging the event queue.
  3. 0

    Jenkins - Test run failed to complete

    Stack Overflow | 2 years ago | zec
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=com.example.simpletest/.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 1438954385239 and now the last time the queue went idle was: 1438954385249. 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 6635#252540941

    GitHub | 5 months ago | tobrun
    java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=com.mapbox.mapboxsdk.testapp/.activity.fragment.MultiMapActivity } 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 1475867001489 and now the last time the queue went idle was: 1475867001506. If these numbers are the same your activity might be hogging the event queue.
  6. 0

    Android/Espresso Intent error on running tests

    Stack Overflow | 8 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.

    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=0x10000000 cmp=com.godaddy.gdm.SettingsActivity } 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 1486944041826 and now the last time the queue went idle was: 1486944049404. 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:1932)
      1 frame