Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Android Studio 2.3 Update not opening app [Instant Run Service]

I recently updated the Android Studio to 2.3. When I hit the instant run button, It compiles the app but doesn't open the app on the Android device. Even 'Hot Swap' is not enabled after that, it shows "No active 'app' launch". Any idea what I might be doing wrong. I tried creating a new project, but this error exists in that also.

I am getting below error:

 Error while executing: am startservice
 com.example/com.android.tools.fd.runtime.InstantRunService Starting
 service: Intent { act=android.intent.action.MAIN
 cat=[android.intent.category.LAUNCHER]
 cmp=com.example/com.android.tools.fd.runtime.InstantRunService }
 Error: Not found; no service started.
like image 402
user1590595 Avatar asked Mar 03 '17 03:03

user1590595


People also ask

Why my app is not opening in Android Studio?

It is because you are running it as a 'test' and not as an 'Android Application'. Open the "Edit Configurations" pane and click the '+' button. Select the option to create a new 'Android Application' and then select the correct module.

Does Android Studio still have instant run?

We Want Your Feedback! Instant Run is currently available only in Android Studio 2.0, and higher. We will continue to improve the feature in subsequent releases. If you run into any additional issues, please help by logging bugs in our public Issues Tracker.

What is Android instant run?

It's a feature in Android Studio that uses magic to significantly reduce the build and deploy times for incremental code changes during your coding/testing/debugging lifecycle. This is normal and is part of the Instant Run feature.


1 Answers

Got the same error after updating. As already noted, there's an open discussion on this topic. So far, the only work-around is that you actually disable instant run, that's the only thing that worked for me. You can do so in Preferences -> Build, Execution, Deployment -> Instant Run:enter image description here

Turn it off and run the app again and it's going to work. That's the best we can do at this point.

like image 72
Vucko Avatar answered Oct 02 '22 13:10

Vucko