Activity never becomes requested state "[DESTROYED, RESUMED, STARTED, CREATED]" (last lifecycle transition = "PRE_ON_CREATE")

Question

This is not a duplicate question.
I have already looked at similar questions. I have added the questions I have referred to at the last.

My problem is that the test executes, but I have to open the app manually for every test.

You can see that I had been waiting for 18 seconds before opening the app. It waits till I open the app manually or it shows this error after a timeout.

Activity never becomes requested state "[DESTROYED, RESUMED, STARTED, CREATED]" (last lifecycle transition = "PRE_ON_CREATE")

From this post, I assume the issue is with the device as I am using Redmi Note 5.
I have disabled animations as well as the MIUI optimization option.

Any help is appreciated to run the tests on Xiaomi devices automatically.

No point in running automated UI tests manually.

Update 1
It executes only for launcher / main activity.
It is not working for other activities.

Update 2
I also happen to have a Redmi 4. The tests work on that device as expected without any code changes.

Referred SO questions

And related issues,

Adding code snippets and dependencies for anyone who wants to have a look,

Test code

import androidx.test.core.app.ActivityScenario
import androidx.test.espresso.Espresso.onView
import androidx.test.espresso.assertion.ViewAssertions.matches
import androidx.test.espresso.matcher.ViewMatchers.*
import androidx.test.internal.runner.junit4.AndroidJUnit4ClassRunner
import org.junit.Test
import org.junit.runner.RunWith

@RunWith(AndroidJUnit4ClassRunner::class)
class MainActivityTest {
    @Test
    fun test_isActivityInView() {
        val activityScenario = ActivityScenario.launch(MainActivity::class.java)
        onView(withId(R.id.layout_activity_main)).check(matches(isDisplayed()))
    }
}

Dependencies

testImplementation "junit:junit:4.13.2"
androidTestImplementation "androidx.test:core:1.4.0"
androidTestImplementation "androidx.test:runner:1.4.0"
androidTestImplementation "androidx.test:rules:1.4.0"
androidTestImplementation "androidx.test.ext:junit-ktx:1.1.3"
androidTestImplementation "androidx.test.espresso:espresso-core:3.4.0"

@HarisDautović, I have a Redmi 4 as well and it works on that device for me. — Abhimanyu, Jul 27 '21 at 04:04
Faced similar issue in Jetpack Compose testing as well - This helped for that - https://github.com/android/android-test/issues/1199#issuecomment-1003197518 — Abhimanyu, Jul 09 '22 at 08:54

score 23 · Answer 1 · edited Dec 08 '22 at 13:30

23

This is a problem of permissions. Just allow autostart and pop-up window for this app on your android phone settings.

Then start USB debugging and allow chain-start for the test app.

It worked for me on XiaoMi 11 青春版.

You can find these settings on Settings->Apps->Manage Apps ->Your-Application->Permissions

edited Dec 08 '22 at 13:30

DoubleYellowIce

3
2

answered Sep 04 '21 at 08:53

zmx0142857

331
1
5

It worked for me! Although the test that manually passed now automatically don't. hahahaha – Miguel Isla Nov 01 '21 at 21:02
Wasted 2 hours on this, really glad this worked. – Praveen Nov 12 '21 at 13:01
wasted 4 hours on this, really glad this worked, thanks mate :) – Tehleel Mir Nov 17 '21 at 10:35
Wasted my entire life on this. Really glad this worked... Thanks mate! – Richard Onslow Roper May 14 '22 at 03:33
2

Still wasting time and can not fix this... What is Autostart and Popup Window? – George Shalvashvili May 23 '22 at 19:39
2

Legend says that time is still being wasted on this. – Kochez Jul 28 '22 at 12:28

score 8 · Answer 2 · answered Oct 07 '21 at 06:04

8

I had the same problem. The problem sometimes arises because of using

androidTestImplementation 'androidx.fragment:fragment-testing:1.3.6'

instead of

debugImplementation 'androidx.fragment:fragment-testing:1.3.6'

If you have fragments in your test scenarios add this dependency with debugImplementation and check it again. Thanks to this post for the answer.

answered Oct 07 '21 at 06:04

Mansour

445
1
4
14

1

Changing to debugImplementation , Worked for me thank you – Nikhil Raut Aug 25 '22 at 05:12

score 5 · Answer 3 · answered Feb 09 '22 at 06:53

I was getting following error on my Android 11 device

java.lang.AssertionError: Activity never becomes requested state "[STARTED, RESUMED, CREATED, DESTROYED]" (last lifecycle transition = "PRE_ON_CREATE")

I wasted a good amount of time on it and found the solution when I switched my device to Android 10.

If anybody facing such issue, please do following things to resolve it,

Enable autostart in app setting
Grant the permission to "Display pop_up windows while running in the background" from app permission settings

score 1 · Answer 4 · answered Feb 16 '22 at 15:14

I was testing in a virtual Pixel 2 with API 30. No option for "autostart" or "pop-up" in Settings. In short, what this message says is that can't open the activity, so if you open manually your app, either in virtual device or real one, the test will run.

score 0 · Answer 5 · answered Mar 08 '22 at 16:11

0

My problem was that I had an update awaiting me on my Android 11 Redmi Note 10s, after updating and doing the other suggested answers it worked!

answered Mar 08 '22 at 16:11

MercifulSory

337
1
14

score 0 · Answer 6 · edited Oct 19 '22 at 12:31

0

Check whether you call getIntent().setAction() on the onCreate method and remove it if so.

That's how I "solved" it in my case.

edited Oct 19 '22 at 12:31

Donald Duck

8,409
22
75
99

answered Oct 12 '22 at 15:07

kandrit

44
4

Activity never becomes requested state "[DESTROYED, RESUMED, STARTED, CREATED]" (last lifecycle transition = "PRE_ON_CREATE")

6 Answers6

Linked