Google Espresso java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN

Question

I am new to Espresso UI testing.

I am getting this error while running tests (ADT Eclipse IDE ).

The app is already developed and there are lots of request going on while launching the app. it is not possible to rewrite the app. but i need to find the way to test this UI even if there is any delay in the loading of the components.

        java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN flg=0x14000000 cmp=com.xx.android/com.yy.core.android.map.MapActivity } 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 1390913271702 and and now the last time the queue went idle was: 1390913271767. If these numbers are the same your activity might be hogging the event queue.
        at com.google.android.apps.common.testing.testrunner.GoogleInstrumentation.startActivitySync(GoogleInstrumentation.java:277)
        at android.test.InstrumentationTestCase.launchActivityWithIntent(InstrumentationTestCase.java:119)
        at android.test.InstrumentationTestCase.launchActivity(InstrumentationTestCase.java:97)
        at android.test.ActivityInstrumentationTestCase2.getActivity(ActivityInstrumentationTestCase2.java:104)
        at com.gulesider.android.test.UItest.setUp(UItest.java:25)
        at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:190)
        at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:175)
        at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:555)
        at com.google.android.apps.common.testing.testrunner.GoogleInstrumentationTestRunner.onStart(GoogleInstrumentationTestRunner.java:167)
        at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1799)

I have one library project called “Core” - it will not generate any .apk
Also i have one Android project called “AA” which will access “Core”. - This is AA.apk
Now i have created a test project called “UItest”

Manifest:

    <?xml version="1.0" encoding="utf-8"?>
    <manifest xmlns:android="http://schemas.android.com/apk/res/android"
        package="com.AA.android.test"
        android:versionCode="1"
        android:versionName="1.0" >
    <uses-sdk android:minSdkVersion="8" 
            android:targetSdkVersion="18" />
    <instrumentation
      android:name="com.google.android.apps.common.testing.testrunner.GoogleInstrumentationTestRunner"
      android:targetPackage="com.AA.android"/>
    <application
            android:allowBackup="true"
            android:icon="@drawable/ic_launcher"
            android:label="@string/app_name" >
    <activity
                android:name="com.core.android.map.MapActivity"
                android:label="@string/app_name" >
                <intent-filter>
                    <action android:name="android.intent.action.MAIN" />
                    <category android:name="android.intent.category.LAUNCHER" />
                </intent-filter>
            </activity>
            <uses-library android:name="android.test.runner" />
        </application>
    </manifest>

My test:

    public class UItest extends ActivityInstrumentationTestCase2<MapActivity> {
        public UItest() {
            super(MapActivity.class);
        }

        @Override
        public void setUp() throws Exception {
            super.setUp();

            getActivity();

        }

        public void testSearchBox() {

            Espresso.onView(ViewMatchers.withId(R.id.menu_button_logo)).perform(ViewActions.click());

        }

    }

post your code what you did.. – Shailendra Madda Jan 28 '14 at 13:03 — Shailendra Madda, Jan 28 '14 at 13:03

score 12 · Answer 1 · answered Apr 08 '15 at 20:13

12

For Espresso Testing it is highly recommend that you turn off system animations on the virtual or physical device(s) used for testing. So you can follow the steps below to manually turn off the animations:

Under: Settings->
Developer options-> Drawing

Window Animations scale to OFF
Transition animation scale to OFF
Animator duration scale to OFF

answered Apr 08 '15 at 20:13

Testing Singh

1,347
1
15
26

2

I'm wondering if there if a description of why this is happens and how to resolve this w/o turning off animation – Roger Alien Oct 12 '17 at 20:54
12

I am facing the same issue. Animations already OFF in developer options. – Inderdeep Singh Aug 31 '18 at 08:41

score 5 · Answer 2 · answered Nov 21 '15 at 13:11

5

If there is a progress bar running when you create the activity, you get an error like this. You should cause a stop for the progress bar in order to continue running the test.

answered Nov 21 '15 at 13:11

Murat

3,084
37
55

Yes, this is correct - visible `ProgressBar` maybe the reason of this exception. Check that your activity/fragment has no visible `ProgressBar`s (and be careful when using alpha with ProgressBar) – xCh3Dx Apr 19 '16 at 13:04

Jeffery Ma · Answer 3 · 2019-10-07T07:23:39.600

4

I have stuck into this problem for several hours. Finally, I got the reason.

This works for me.

Here are some different reasons, according to the phenomenon.

Activity can't be launched
Activity launched, but UI perform actions not work

The first scenario: activity can't be launched

Because of your target Activity maybe already in the activity stack. Add a CLEAR flag and NEW_TASK flag

    @get:Rule
    val activityRule = ActivityTestRule<MainActivity>(MainActivity::class.java)

    private lateinit var launchedActivity: MainActivity

    @Before
    fun setUp() {
        val intent = Intent(Intent.ACTION_PICK)
        //this is the key part
        intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TASK)
        //this is the key part
        intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK)
        launchedActivity = activityRule.launchActivity(intent)
    }

The second scenario: activity launched but UI perform actions not work

In this scenario may be because of

Your code is executing some animation in a long time
Your code is doing a UI logic that you don't notice
- (like Handler post event or runnable)
- (register a listener in ViewTreeObserver like OnPreDrawListener and didn't unregister in a proper timing)

These actions may lead to UI thread busy, so the espresso can not do the test.

edited Oct 07 '19 at 07:23

answered Sep 16 '19 at 22:00

Jeffery Ma

3,051
1
23
26

1

Any tips on how to debug the second scenario, beyond breakpoints and println()? ;) i.e. blocking UI logic.... – xavierdominguez Nov 06 '20 at 12:42
Actually, it was because the activity could not be launched and your first trick worked, i.e. adding the CLEAR_TASK and NEW TASK flags. Thanks so much! Been struggling for months with this. Although, I was getting the error below, which led me to think it was more along the lines of your second explanation. Posting below should it help others. – xavierdominguez Nov 06 '20 at 13:08
`java.lang.RuntimeException(Could not launch intent { flg=0x10000000 cmp=com.fake.package.id.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. ... The last time the event queue was idle before your activity launch request was 1604665354699 and now the last time the queue went idle was: 1604665354766. If these numbers are the same your activity might be hogging the event queue.)` – xavierdominguez Nov 06 '20 at 13:08

score 3 · Answer 4 · edited Nov 02 '17 at 10:58

3

I experienced this error while running Espresso tests on 6.0 devices but not on 5.1.1 or 7.0 devices. I tracked the cause down to using android:fadeScrollbars within a style. Removing this item from my style resolved the issue.

edited Nov 02 '17 at 10:58

Albert Vila Calvo

15,298
6
62
73

answered Feb 24 '17 at 02:40

dev5678

31
1

denys · Answer 5 · 2019-01-09T12:42:18.347

2

Probably you have animation inside your activity, which blocks espresso execution. You have to disable it - see https://github.com/googlesamples/android-testing/tree/master/ui/espresso/BasicSample

edited Jan 09 '19 at 12:42

answered Jan 28 '14 at 17:56

denys

6,834
3
37
36

When i followed the above solution, i got this error " Cannot disable animations due to lack of permission " – user3241003 Jan 29 '14 at 12:00
Try adding the request permission, as state in the above link's comments – Bolhoso Feb 14 '14 at 17:23

score 2 · Answer 6 · answered Jan 21 '22 at 07:47

2

If you are performing this test in MI or XIOMI phone then maybe it will not work so you can change device or you can use bluestack emulator. It will be work

answered Jan 21 '22 at 07:47

Tech Projects

21
3

score 1 · Answer 7 · answered Sep 12 '16 at 13:27

1

In my case a custom view caused this behaviour. It contained a Scroller which was constantly scrolling. Unfortunately, I didn't find a solution for this issue until now except disabling it for the tests...

answered Sep 12 '16 at 13:27

luckyhandler

10,651
3
47
64

How did you disable it? – anuja jain Jan 12 '17 at 10:30
I told the View which was a custom one, not to scroll when a test was running. To determine if it was running I used the following solution: http://stackoverflow.com/a/28701836/3734116 – luckyhandler Jan 12 '17 at 10:47

score 0 · Answer 8 · answered Jan 28 '14 at 13:21

At the very first page you will be calling too many request which will be taking time more than 15 seconds, the first page should be very lightwieght. Just try by creating one new welcome page and then calling your original welcome page. Hope this work for you.

score 0 · Answer 9 · answered Apr 15 '19 at 10:41

Well, in my case it was caused by a strange thing.

One of my UI tests opened the external intent "android.app.action.CONFIRM_DEVICE_CREDENTIAL" so I decided to stub it. From now on, the MAIN intent didnt launch again until I manually closed the screen oipened by "android.app.action.CONFIRM_DEVICE_CREDENTIAL" from the recent tasks.

No idea why this happened, and have no time now for research. Maybe later I will update this thread.

score 0 · Answer 10 · answered May 28 '19 at 16:12

I faced this error when I trying to test the opening of another activity when the user clicked on a given view. What I was doing wrong was not replacing:

@Rule
public ActivityTestRule<MyActivity> myActivityActivityTestRule = new ActivityTestRule<>(MyActivity.class);

Per:

@Rule
public IntentsTestRule<MyActivity> myActivityActivityTestRule =
            new IntentsTestRule<>(MyActivity.class);

score 0 · Answer 11 · answered Jan 29 '21 at 09:29

0

I had this problem too, and in the moment I changed physical device to other Android phone the tests were working. Just try to use other device. And use @rule for launching activity

answered Jan 29 '21 at 09:29

Pesa

241
1
3
8

score 0 · Answer 12 · answered Mar 13 '23 at 01:48

0

In my case an authorization request returned 401 error. Thats's why a login activity continued to show, while MainActivity didn't start. It cannot be repaired by tests.

answered Mar 13 '23 at 01:48

CoolMind

26,736
15
188
224

Google Espresso java.lang.RuntimeException: Could not launch intent Intent { act=android.intent.action.MAIN

12 Answers12

Linked