Espresso 3.0.2 / Rules 1.0.2: RuntimeException: Could not launch activity [113560556]

Obsolete

Bug

Status Update

No update yet.

Description

to...@googlemail.com

created issue #1

Aug 30, 2018 11:01AM

Artifact used:
- com.android.support.test.espresso:espresso-core:3.0.2
- com.android.support.test:rules:1.0.2

Build tools used: 27.0.3, 28.0.2
Devices/Android versions reproduced on:
- Nexus 5, Android 6.0.1
- Pixel 2, Android 9

- Relevant code to trigger the issue.
-- Dependency change:

https://github.com/johnjohndoe/Umweltzone/commit/ea84d0facc7a88f0a7b3f2f65b873ab7777a175f
-- NoCitySelectedFragmentTest:

https://github.com/johnjohndoe/Umweltzone/blob/ea84d0facc7a88f0a7b3f2f65b873ab7777a175f/Umweltzone/src/androidTest/java/de/avpptr/umweltzone/city/NoCitySelectedFragmentTest.java
-- build.gradle files:

https://github.com/johnjohndoe/Umweltzone/blob/ea84d0facc7a88f0a7b3f2f65b873ab7777a175f/build.gradle

https://github.com/johnjohndoe/Umweltzone/blob/ea84d0facc7a88f0a7b3f2f65b873ab7777a175f/Umweltzone/build.gradle

I noticed that the instrumentation tests I set up in my project stopped working once I update Espresso from v.2.2.2 to v.3.0.2 (while add test:rules v.1.0.2). The following error message is output:

---
de.avpptr.umweltzone.city.NoCitySelectedFragmentTest > renderCityInfo[Pixel 2 - 9]
FAILED java.lang.RuntimeException: Could not launch activity
at android.support.test.runner.MonitoringInstrumentation
.startActivitySync(MonitoringInstrumentation.java:460)
---

Related:
- This seems to be related to

https://issuetracker.google.com/issues/68273799 but the solution there did not solve my issue.

Workaround:
- Do not use Espresso v.3.0.2 Use Espresso v.2.2.2 without the Rules instead.

Comments

vi...@google.com <vi...@google.com> Aug 31, 2018 11:19AM

Assigned to vi...@google.com.

ad...@google.com <ad...@google.com> #2Aug 31, 2018 11:40AM

Reassigned to ad...@google.com.

We have passed this to the development team and will update this issue with more information as it becomes available.

to...@googlemail.com <to...@googlemail.com> #3Sep 20, 2018 07:32AM

I recently executed the tests on a Nexus 9, Android 7.1.1. To my surprise, on this device all tests successfully run. I hope this gives you an idea to resolve the issue.

to...@googlemail.com <to...@googlemail.com> #4Oct 29, 2018 12:09AM

Could you find any pattern? Can I help with any further information?

to...@googlemail.com <to...@googlemail.com> #5Feb 8, 2019 10:55AM

Any news on this issue? Can I help somehow?

to...@googlemail.com <to...@googlemail.com> #6Feb 17, 2019 05:47PM

Here is an updated branch which shows how Espresso 2.2.2 successfully executes the instrumentation tests:

https://github.com/johnjohndoe/Umweltzone/commits/travis-ci

The build log on Travis CI can be found here:

https://travis-ci.org/johnjohndoe/Umweltzone/builds/494553442

sa...@google.com <sa...@google.com> #7Nov 13, 2019 09:15AM

We will be closing this bug as Obsolete. If you still think this issue is reproducible and relevant in the latest Android release (Android Q), please attach a new bug report along with reproduction details. If a reply is not received within the next 14 days, this issue will be closed. Thank you for your understanding.

to...@googlemail.com <to...@googlemail.com> #8Nov 13, 2019 09:30AM

I did not have time to migrate the project to androidx yet. Therefore, I cannot tell about whether a newer testing library version has the same issue. Right now I have to use the old Espresso version. I will let you know if the new version works for me once I get there.

ad...@google.com <ad...@google.com> #9Nov 21, 2019 04:44AM

Can you please address

comment #8

to...@googlemail.com <to...@googlemail.com> #10Nov 21, 2019 07:43AM

I believe you are addressing someone in your team, not me. Is that right?

ad...@google.com <ad...@google.com> #11Nov 25, 2019 12:45PM

Are you able to check and reproduce this issue with the latest version?

to...@googlemail.com <to...@googlemail.com> #12Nov 25, 2019 02:21PM

Not at the moment. You can see in the linked project (

comment #1

comment #6

) that I did not have time to migrate the project to androidx yet.

cc...@google.com <cc...@google.com> Aug 11, 2020 07:34AM

Reassigned to ni...@google.com.

cc...@google.com <cc...@google.com> Aug 11, 2020 04:25PM

Reassigned to an...@google.com.

al...@google.com <al...@google.com> #13Feb 8, 2023 06:46PM

Status: Won't Fix (Obsolete)

This issue was filed against the top-level component, which is not monitored, and has exceeded the age limit for triage to the appropriate sub-component.

If this issue is still relevant, please re-file it against the appropriate sub-component.

to...@googlemail.com <to...@googlemail.com> #14Feb 9, 2023 07:40AM

This issue was filed against the top-level component, which is not monitored, and has exceeded the age limit for triage to the appropriate sub-component.

What does that mean?