Fixed
Status Update
Comments
gh...@gmail.com <gh...@gmail.com> #2
Та же проблема.
Google, я твой рот шатал, хватит косячить!!
Google, я твой рот шатал, хватит косячить!!
go...@gmail.com <go...@gmail.com> #3
Same issue and same log.
I can't launch my app on some physical devices with Android Studio 2.3 and Instant Run on .
Disabling instant run can fix the problem for me, but this's not cool..
I can't launch my app on some physical devices with Android Studio 2.3 and Instant Run on .
Disabling instant run can fix the problem for me, but this's not cool..
so...@gmail.com <so...@gmail.com> #4
Faced the same problem, turning off Instant Run helped
ru...@gmail.com <ru...@gmail.com> #5
After updated i can't launch my app.
ch...@gmail.com <ch...@gmail.com> #6
Seeing the same here after upgrade to 2.3
ki...@gmail.com <ki...@gmail.com> #7
[Comment deleted]
ki...@gmail.com <ki...@gmail.com> #8
turning off instant run will not show debug messages in Run need to see in Android Monitor with filter that's slow down debugging.
la...@gmail.com <la...@gmail.com> #9
solve it pls
a....@gmail.com <a....@gmail.com> #10
facing the same issue.. Disabling instant run launches the app.
uc...@google.com <uc...@google.com> #11
is this issue with specific device ? reproducible on emulator ?.
please share gradle version and build tools version and min/max sdk versions to triage this issue.
please share gradle version and build tools version and min/max sdk versions to triage this issue.
uc...@google.com <uc...@google.com> #17
please read release notes if target requirement is lower that 21
"Instant Run is supported only when deploying your app to a target device running Android 5.0 (API level 21) or higher"
https://developer.android.com/studio/releases/index.html
"Instant Run is supported only when deploying your app to a target device running Android 5.0 (API level 21) or higher"
mi...@gmail.com <mi...@gmail.com> #18
I'm having this problem on both Android 6.0 and 7.0 devices, isn't it 21+?
gh...@gmail.com <gh...@gmail.com> #19
"Instant Run is supported only when deploying your app to a target device running Android 5.0 (API level 21) or higher"
My device have Android 5.0 (API21) and my App not runnig on this device and Emulator with API22.
This bug is appear after update to Android Studio 2.3 and Gradle 3.3.
My device have Android 5.0 (API21) and my App not runnig on this device and Emulator with API22.
This bug is appear after update to Android Studio 2.3 and Gradle 3.3.
je...@google.com <je...@google.com> #21
can any of you share a sample project reproducing the issue ?
gh...@gmail.com <gh...@gmail.com> #23
The project when reproducing this issue on SUS-ASUS_Z00RD with Android 5.0 (API21).
http://pavelzinovev.ru/test_project_235879.zip
pr...@gmail.com <pr...@gmail.com> #24
Any update here?
the same problem.
the same problem.
do...@gmail.com <do...@gmail.com> #25
I have Android 6.0.1 device. I restarted Android studio, I restarted my computer (Mac mini) but nothing changed. I keep seeing this error. If I disable Instant Run, Android studio works so slow. My work is harder since 2.3 Update. Please fix it.
ya...@gmail.com <ya...@gmail.com> #26
I have the same problem,after update to 2.3 ,i can not luanch my appp.
an...@gmail.com <an...@gmail.com> #27
not launching on real device (Marshmallow) after update to 2.3 :
03/07 15:14:36: Launching app
$ adb install-multiple -r D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\outputs\apk\app-debug.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_4.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_9.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_3.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_8.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_5.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_6.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_7.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_1.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_2.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_0.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\dep\dependencies.apk
Split APKs installed
$ adb shell am startservice ag.footway.haircutslunarcalendar/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice ag.footway.haircutslunarcalendar/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=ag.footway.haircutslunarcalendar/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
03/07 15:14:36: Launching app
$ adb install-multiple -r D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\outputs\apk\app-debug.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_4.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_9.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_3.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_8.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_5.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_6.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_7.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_1.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_2.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\slices\slice_0.apk D:\HaircutsLunarCalendar\HaircutsLunarCalendar\app\build\intermediates\split-apk\debug\dep\dependencies.apk
Split APKs installed
$ adb shell am startservice ag.footway.haircutslunarcalendar/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice ag.footway.haircutslunarcalendar/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=ag.footway.haircutslunarcalendar/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
lo...@gmail.com <lo...@gmail.com> #28
I have also the same problem. I tried to reinstall android studio but it does not have any effect...
API 21 (asus tablet)
API 21 (asus tablet)
ja...@google.com <ja...@google.com> #29
For folks who are running into this issue, can you please post the device that you are using? We suspect that this might be a device-specific issue. Letting us know will help us track this down. Thanks!
ch...@gmail.com <ch...@gmail.com> #30
I'm facing this on a One Plus 3T.
ni...@gmail.com <ni...@gmail.com> #31
I'm using ASUS_Z00AD with Android 5.0 (API 21)
mi...@gmail.com <mi...@gmail.com> #32
Hi James,
My device is LeEco Le 1S ( Android 6.0 ). It has the issue.
Amazon Fire 7 with Fire OS 5 ( Android 5.1.1 ) and all my other 6 test devices are working fine with various Android versions from 4.1 to 7.1
I also had the exact same issue on Samsung Galaxy S2 with a custom ROM ( Android 7.1 ), until I flashed the latest LineageOS.
My device is LeEco Le 1S ( Android 6.0 ). It has the issue.
Amazon Fire 7 with Fire OS 5 ( Android 5.1.1 ) and all my other 6 test devices are working fine with various Android versions from 4.1 to 7.1
I also had the exact same issue on Samsung Galaxy S2 with a custom ROM ( Android 7.1 ), until I flashed the latest LineageOS.
ja...@gmail.com <ja...@gmail.com> #33
I'm having the same issue on ASUS_Z011D with Android 6.0.1
ja...@gmail.com <ja...@gmail.com> #34
This issue has been open for 4 days now. No resolution yet. Google must be serious about testing Android Studio well enough before advertising. It is frustrating that developers need to spend cycles in debugging Android Studio issues instead of leveraging the new features and moving on with their development.
an...@gmail.com <an...@gmail.com> #35
model number: BQS-5020
android version: 6.0
android security patch level: june 1, 2016
baseband version: MOLY.WR8.W1449.MD.WG.MP.V57.P4, 2016/04/20 10:28
kernel version: 3.18.19+ android@ubuntu #2 Mon Aug 8 15:30:29 CST 2016
build number: MRA58K release-keys
custom build version: BQS-5020_6.0_10
device never rooted
Thanks!
2017-03-07 22:26 GMT+05:00 <android@googlecode.com>:
android version: 6.0
android security patch level: june 1, 2016
baseband version: MOLY.WR8.W1449.MD.WG.MP.V57.P4, 2016/04/20 10:28
kernel version: 3.18.19+ android@ubuntu #2 Mon Aug 8 15:30:29 CST 2016
build number: MRA58K release-keys
custom build version: BQS-5020_6.0_10
device never rooted
Thanks!
2017-03-07 22:26 GMT+05:00 <android@googlecode.com>:
vs...@google.com <vs...@google.com> #37
Could any of you perform the following steps and provide some more information?
1. From a terminal, issue the following command:
$ adb shell setprop log.tag.InstantRun VERBOSE
2. Then press "Run" and reproduce your problem.
3. Finally, attach the logcat from your device:
$ adb logcat > logcat.txt
(press Ctrl+C after a few seconds once all the logcat is captured)
4. Then attach the logcat.txt file to this bug.
Thank you for your help. This issue seems specific to a set of devices. We are looking into obtaining one of those devices to reproduce this problem.
1. From a terminal, issue the following command:
$ adb shell setprop log.tag.InstantRun VERBOSE
2. Then press "Run" and reproduce your problem.
3. Finally, attach the logcat from your device:
$ adb logcat > logcat.txt
(press Ctrl+C after a few seconds once all the logcat is captured)
4. Then attach the logcat.txt file to this bug.
Thank you for your help. This issue seems specific to a set of devices. We are looking into obtaining one of those devices to reproduce this problem.
ru...@gmail.com <ru...@gmail.com> #38
Instant Run doesnt work on Meizu M1 Metal. Doesnt launch app.
sf...@gmail.com <sf...@gmail.com> #39
My device is Meizu Note 3 with Flyme 6.0;
------------------ Original ------------------
From: "android";<android@googlecode.com>;
Date: Wed, Mar 8, 2017 01:26 AM
To: "sflietrain"<sflietrain@gmail.com>;
Subject: Re: Issue 36949180 in android: android studio 2.3 instant run not working
------------------ Original ------------------
From: "android";<android@googlecode.com>;
Date: Wed, Mar 8, 2017 01:26 AM
To: "sflietrain"<sflietrain@gmail.com>;
Subject: Re:
sf...@gmail.com <sf...@gmail.com> #40
[Comment deleted]
sf...@gmail.com <sf...@gmail.com> #41
gradle version:gradle-3.3-all
buildToolsVersion '25.0.0'
minSdkVersion 16
targetSdkVersion 25
buildToolsVersion '25.0.0'
minSdkVersion 16
targetSdkVersion 25
ki...@gmail.com <ki...@gmail.com> #42
package: com.kishan.testproject
Device: ASUS_Z008
Android Studio 2.3
Windows 8
Device: ASUS_Z008
Android Studio 2.3
Windows 8
ya...@gmail.com <ya...@gmail.com> #43
here is my log and phone info
ee...@gmail.com <ee...@gmail.com> #44
Can't use instant run on android device with Android version > 5.0.
Uncheck the instant run in settings solved my problems.
Uncheck the instant run in settings solved my problems.
ja...@gmail.com <ja...@gmail.com> #45
Here's the logcat.txt as requested in update #38
an...@gmail.com <an...@gmail.com> #46
logcat.txt attached. About device:
model number: BQS-5020
android version: 6.0
android security patch level: june 1, 2016
baseband version: MOLY.WR8.W1449.MD.WG.MP.V57.P4, 2016/04/20 10:28
kernel version: 3.18.19+ android@ubuntu #2 Mon Aug 8 15:30:29 CST 2016
build number: MRA58K release-keys
custom build version: BQS-5020_6.0_10
model number: BQS-5020
android version: 6.0
android security patch level: june 1, 2016
baseband version: MOLY.WR8.W1449.MD.WG.MP.V57.P4, 2016/04/20 10:28
kernel version: 3.18.19+ android@ubuntu #2 Mon Aug 8 15:30:29 CST 2016
build number: MRA58K release-keys
custom build version: BQS-5020_6.0_10
ja...@google.com <ja...@google.com> #47
Thanks to all of you who have provided us with the info. Right now, we suspect that this is a device specific issue. We have ordered some of these devices so we can reproduce them locally to investigate the issue.
We are sorry for the inconvenience, but we will report back on this thread once the devices arrive and we are able to reproduce them. We may come back and ask for your help with this issue. Rest assured we are working on it. Thanks again!
We are sorry for the inconvenience, but we will report back on this thread once the devices arrive and we are able to reproduce them. We may come back and ask for your help with this issue. Rest assured we are working on it. Thanks again!
qq...@gmail.com <qq...@gmail.com> #48
hey,James,my device is MeiZu note3 with Flyme6。thx。
et...@gmail.com <et...@gmail.com> #49
MeiZu MX5 with Flyme6 thx.
et...@gmail.com <et...@gmail.com> #50
03/08 16:49:21: Launching app
$ adb shell am startservice com.ethan.myclub/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.ethan.myclub/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.ethan.myclub/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
$ adb shell am startservice com.ethan.myclub/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.ethan.myclub/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.ethan.myclub/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
lo...@gmail.com <lo...@gmail.com> #51
[Comment deleted]
do...@gmail.com <do...@gmail.com> #52
I uninstalled and reinstalled Android Studio with all settings and projects. I used HTC Desire EYE (Android 6.0.1) And General Mobile GM5 (Android 7.1.1) Problem still exist. Instant Run not working and my project runs in 5 minutes. Every time I hit Run button, I wait 5 minutes to see what is changed. Please fix this. Or I want to revert back Android 2.2. Is there any way to do that?
pa...@gmail.com <pa...@gmail.com> #53
Hey hi i update my android studio and facing the similar issue . Previously it was working fine on 2.3.0 now with 3.0 version its not working... Please note that this is not device specific bug . Bug is in patch or android studio upgrade..
any comments please let me know
$ adb shell am startservice ch.hepia.iti.opencvnativeandroidstudio/com.android.tools.fd.runtime.InstantRunService
Unexpected error while executing: am startservice ch.hepia.iti.opencvnativeandroidstudio/com.android.tools.fd.runtime.InstantRunService
any comments please let me know
$ adb shell am startservice ch.hepia.iti.opencvnativeandroidstudio/com.android.tools.fd.runtime.InstantRunService
Unexpected error while executing: am startservice ch.hepia.iti.opencvnativeandroidstudio/com.android.tools.fd.runtime.InstantRunService
la...@gmail.com <la...@gmail.com> #54
I have an ASUS Z380KNL running Android 6.0.1 and I face the same issue:
Error while executing: am startservice com.example.android.pets/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.android.pets/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
All these lines you can find in my logcat continue for as long as the device is connected, like in an infinite loop. I disconnect the device, the logcat stops, I connect it again, it starts all over again.
On my Samsung J5 running Android 5.1.1 everything seems to work fine.
Android Studio and the Gradle are updated to the latest version and I have Windows 8.1 on my computer.
Also, there is a really nagging problem with aapt.exe files. I have about 20 hanging on my RAM (I can see them in the Task manager) every time I change the testing device.
I hope you guys can solve it.
Error while executing: am startservice com.example.android.pets/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.android.pets/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
All these lines you can find in my logcat continue for as long as the device is connected, like in an infinite loop. I disconnect the device, the logcat stops, I connect it again, it starts all over again.
On my Samsung J5 running Android 5.1.1 everything seems to work fine.
Android Studio and the Gradle are updated to the latest version and I have Windows 8.1 on my computer.
Also, there is a really nagging problem with aapt.exe files. I have about 20 hanging on my RAM (I can see them in the Task manager) every time I change the testing device.
I hope you guys can solve it.
an...@gmail.com <an...@gmail.com> #55
Same with me:
- Android Studio 2.3
- Instant Run enabled
- every time I hit Run -> Apply Changes, the gradle console output tells me "Instant Run applied code changes and restarted the app."
- this really seemed to change with this update; the days before the update the instant run worked;
my current environment:
- Android 2.3
- Compile SDK Version: API 25: Android 7.1.1 (Nougat)
- Build Tools Version: 25.0.2
- Gradle 3.3
Mac Os 10.12.3
- Android Studio 2.3
- Instant Run enabled
- every time I hit Run -> Apply Changes, the gradle console output tells me "Instant Run applied code changes and restarted the app."
- this really seemed to change with this update; the days before the update the instant run worked;
my current environment:
- Android 2.3
- Compile SDK Version: API 25: Android 7.1.1 (Nougat)
- Build Tools Version: 25.0.2
- Gradle 3.3
Mac Os 10.12.3
ee...@gmail.com <ee...@gmail.com> #56
device: HUAWEI TAG-AL00
android version: 5.1
android version: 5.1
ca...@gmail.com <ca...@gmail.com> #57
I solved this problem.
1. Do not debug with 'Debug app' button
2. Debug with 'Run app' button (see attached file)
3. Finally Use for Instant Run with 'Apply change' button
It seems a bug in Android Studio 2.3
1. Do not debug with 'Debug app' button
2. Debug with 'Run app' button (see attached file)
3. Finally Use for Instant Run with 'Apply change' button
It seems a bug in Android Studio 2.3
la...@gmail.com <la...@gmail.com> #58
Sorry, that solution is not working for me.
I get the same error:
03/09 09:01:52: Launching app
$ adb install-multiple -r -p com.example.android.pets C:\Users\MyPC\AndroidStudioProjects\Pets\app\build\intermediates\split-apk\debug\slices\slice_2.apk C:\Users\MyPC\AndroidStudioProjects\Pets\app\build\intermediates\split-apk\debug\slices\slice_0.apk C:\Users\MyPC\AndroidStudioProjects\Pets\app\build\outputs\apk\app-debug.apk
Split APKs installed
$ adb shell am startservice com.example.android.pets/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.example.android.pets/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.android.pets/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
Asus Zenpad Z380KNL Android 6.0.1.
- Android 2.3
- Build Tools Version: 25.0.2
- Gradle 3.3
- Windows 8.1 64-bit.
I get the same error:
03/09 09:01:52: Launching app
$ adb install-multiple -r -p com.example.android.pets C:\Users\MyPC\AndroidStudioProjects\Pets\app\build\intermediates\split-apk\debug\slices\slice_2.apk C:\Users\MyPC\AndroidStudioProjects\Pets\app\build\intermediates\split-apk\debug\slices\slice_0.apk C:\Users\MyPC\AndroidStudioProjects\Pets\app\build\outputs\apk\app-debug.apk
Split APKs installed
$ adb shell am startservice com.example.android.pets/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.example.android.pets/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.android.pets/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
Asus Zenpad Z380KNL Android 6.0.1.
- Android 2.3
- Build Tools Version: 25.0.2
- Gradle 3.3
- Windows 8.1 64-bit.
[Deleted User] <[Deleted User]> #59
Same problem here.
Using:
Android Studio 2.3
Gradle 3.3
CompileSdkVersion 25
BuildToolsVersion 25.0.0
MinSdkVersion 16
TargetSdkVersion 22
I have a lenovo 7' tab running android 5 and instant run works perfectly there.
I aslo have an asus_z00LD running android 6 and this is where instant run does not work. It builds the app perfectly, but instant run app launch does not work. I have to manually launch the app all the time.
Using:
Android Studio 2.3
Gradle 3.3
CompileSdkVersion 25
BuildToolsVersion 25.0.0
MinSdkVersion 16
TargetSdkVersion 22
I have a lenovo 7' tab running android 5 and instant run works perfectly there.
I aslo have an asus_z00LD running android 6 and this is where instant run does not work. It builds the app perfectly, but instant run app launch does not work. I have to manually launch the app all the time.
me...@outlook.com <me...@outlook.com> #60
Same problem here.
Using:
Android Studio 2.3
Gradle 3.3
CompileSdkVersion 25
BuildToolVersion 25.0.2
MinSdkVersion 19
TargetSdkVersion 25
I too am running a Asus Zenpad C 7.0 running Android 5.0.2
Using:
Android Studio 2.3
Gradle 3.3
CompileSdkVersion 25
BuildToolVersion 25.0.2
MinSdkVersion 19
TargetSdkVersion 25
I too am running a Asus Zenpad C 7.0 running Android 5.0.2
ja...@google.com <ja...@google.com> #61
Thanks for continuing to report devices impacted by this issue. Can you try using the emulator and confirm that this issue does not reproduce there? Thanks.
ch...@gmail.com <ch...@gmail.com> #62
The issue is present when using my physical device (a OnePlus 3T).
I can't reproduce it on an API 24 emulator.
I can't reproduce it on an API 24 emulator.
la...@gmail.com <la...@gmail.com> #63
The issue does not reproduce on emulator (API 25 emulator).
ja...@google.com <ja...@google.com> #64
Thank you for your patience while we investigated this issue. The problem seems to be that some manufacturers have customized their devices and added some sort of "Auto-start" blocker. For affected Asus devices, for example, you can fix this issue by enabling Auto-start for your app with Asus's Auto-start Manager. See this page for details: https://www.asus.com/support/faq/1013752
But different manufacturer seems to do this differently. For example, for LeEco devices, you can allow "auto-launch" under settings. See this issue (https://github.com/openstf/stf/issues/407#issuecomment-247852532 ) for info on how to enable auto-launch for your app.
It would be great if you can try to enable auto-start or auto-launch on your device for your app, and let us know if that resolves the issue for you.
But different manufacturer seems to do this differently. For example, for LeEco devices, you can allow "auto-launch" under settings. See this issue (
It would be great if you can try to enable auto-start or auto-launch on your device for your app, and let us know if that resolves the issue for you.
ni...@gmail.com <ni...@gmail.com> #66
Instant run now working on ASUS_Z00AD. Thank you James.
am...@gmail.com <am...@gmail.com> #67
I can't find a similar "auto-start" option for the OnePlus 3T. Running oxygenOS 4.0.3, API 24.
ar...@gmail.com <ar...@gmail.com> #68
Thank you, James. Instant run is now working after removing the app from auto-start/auto-kill blocklist (in Purify app /w rooted device).
ki...@gmail.com <ki...@gmail.com> #69
After allow application in Auto-start manager, it's able to launch but in Run window Log messages are showing.
To check Log messages need to switch to Android Monitor Window.
Is this permanent solution?
To check Log messages need to switch to Android Monitor Window.
Is this permanent solution?
se...@gmail.com <se...@gmail.com> #70
Same issue with Studio 2.3 (Win8.1 Pro) on Nexus5 and Nexus5x.
Also sometimes in debug Studio freezes and not responding.
Also sometimes in debug Studio freezes and not responding.
la...@gmail.com <la...@gmail.com> #71
On Asus Zenpad Z380KNL Instant Run works if I allow Auto-Start. However this means in every app I install I have to allow Auto Start.
This was not an issue in previous Android Studio versions.
Is this a permanent solution?
This was not an issue in previous Android Studio versions.
Is this a permanent solution?
la...@gmail.com <la...@gmail.com> #72
Also here is my new logcat after applying your solution (ASUS Z380KNL).
mi...@gmail.com <mi...@gmail.com> #73
Hi James,
Auto-launch resolved the issue for me on my LeEco Le 1S!
Hope it's just a workaround and not the final solution, because it's really annoying to enable it for my every app. Also when I want to do a clean install and uninstall the app, I have to enable auto-launch again.
Auto-launch resolved the issue for me on my LeEco Le 1S!
Hope it's just a workaround and not the final solution, because it's really annoying to enable it for my every app. Also when I want to do a clean install and uninstall the app, I have to enable auto-launch again.
la...@gmail.com <la...@gmail.com> #74
For OnePlus/Oxygen OS user, you find auto-launch in setting > Apps > advanced (top right gear button ) > App auto-launch ( on the bottom list , advanced category ).
It works fine if you turn on the auto-launch for the app you wish to run fro.
Thanks.
It works fine if you turn on the auto-launch for the app you wish to run fro.
Thanks.
et...@gmail.com <et...@gmail.com> #75
Thanks James! It works for me!
My device is Meizu Mx5 and I just allow my application "stay in background" in the permission management.
I guess most of people here are Chinese. So just find your "手机管家" or something like that and allow your app auto-run.
My device is Meizu Mx5 and I just allow my application "stay in background" in the permission management.
I guess most of people here are Chinese. So just find your "手机管家" or something like that and allow your app auto-run.
et...@gmail.com <et...@gmail.com> #76
[Comment deleted]
ja...@google.com <ja...@google.com> #77
Thanks for verifying everyone. I am downgrading this issue because of the workaround.
le...@gmail.com <le...@gmail.com> #78
This seems to be just a hack to get it to work. What's the permanent fix for this?
gh...@gmail.com <gh...@gmail.com> #79
Fooking askewhand developers. Don't downgrading this issue!! Fix this bug!! Уебаны криворукие...
vs...@google.com <vs...@google.com> #80
This is fixed properly without requiring any user intervention in our 2.4 builds.
We are looking into a possible fixes for 2.3, but we don't have a good one as yet.
We are looking into a possible fixes for 2.3, but we don't have a good one as yet.
gh...@gmail.com <gh...@gmail.com> #81
How long will we wait for the 2.4 update??
la...@gmail.com <la...@gmail.com> #84
Glad to know this is not the permanent solution because i don't think IDEs should be device dependant. Keeping my fingers crossed for you guys to figure out a way to fix this issue as fast and as good as possible. Happy coding ;)
[Deleted User] <[Deleted User]> #85
Allowing auto-start for my app in auto-start manager in Asus solved the instant-run problem in android-studio 2.3, but the apk file does not open after downloading and installing manually. Below is the description of the problem.
After allowing auto-start in auto-start manager, instant-run after build in studio works and the app opens normally. Now when i send that same apk from
/build/outputs/apk directory as an attachment in a mail to someone, it doesn't work.
The apk downloads and installs correctly but when opening the app, it crashes.
The crash report says:
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.package.project.MyApplication" on path: DexPathList[[zip file "/data/app/com.package.project-1/base.apk"],nativeLibraryDirectories=[/data/app/com.package.project-1/lib/arm, /vendor/lib, /system/lib]]
This problem happens only when the instant-run is enabled in android studio. Disabling instant-run and building the apk works fine.
Checked in devices Lenovo-Tab2A7-10F(android 5), Asus_Z00LD(android 6), MOTO XT1092(android 6)
After allowing auto-start in auto-start manager, instant-run after build in studio works and the app opens normally. Now when i send that same apk from
/build/outputs/apk directory as an attachment in a mail to someone, it doesn't work.
The apk downloads and installs correctly but when opening the app, it crashes.
The crash report says:
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.package.project.MyApplication" on path: DexPathList[[zip file "/data/app/com.package.project-1/base.apk"],nativeLibraryDirectories=[/data/app/com.package.project-1/lib/arm, /vendor/lib, /system/lib]]
This problem happens only when the instant-run is enabled in android studio. Disabling instant-run and building the apk works fine.
Checked in devices Lenovo-Tab2A7-10F(android 5), Asus_Z00LD(android 6), MOTO XT1092(android 6)
je...@gmail.com <je...@gmail.com> #86
@ #88 aniru...@fitblink.com
You need to build the apk again from "Build/Build APK". to get a non instant run build, which will work in other devices.
do...@gmail.com <do...@gmail.com> #87
In HTC Desire EYE or General Mobile GM5 Where is that auto-launch ? Thanks for sharing.
yy...@gmail.com <yy...@gmail.com> #88
my device are MeiZu U20/android 6.0 and OnePlus 3T/7.0
my project config :
minSDK 18,
targetSDK 25,
instant run was ok In as2.2.3.
In as2.3 ,it's not working by the similar run log:not found .....
my project config :
minSDK 18,
targetSDK 25,
instant run was ok In as2.2.3.
In as2.3 ,it's not working by the similar run log:not found .....
vs...@google.com <vs...@google.com> #89
anirudha@: please do the following:
1. Go to preferences | Instant Run | "Enable extra logging"
2. Reproduce the issue again.
3. Help | Submit Instant Run Feedback
4. File a new bug and reference the instant run issue report number.
1. Go to preferences | Instant Run | "Enable extra logging"
2. Reproduce the issue again.
3. Help | Submit Instant Run Feedback
4. File a new bug and reference the instant run issue report number.
[Deleted User] <[Deleted User]> #90
I am using an ASUS tablet 7 inch and the suggestion above (#65) regarding adding my app to the auto-start manager resolved my issue
an...@gmail.com <an...@gmail.com> #91
[Comment deleted]
an...@gmail.com <an...@gmail.com> #92
After many hours of debugging and comparing Android Studio 2.2 and 2.3.
Android Studio 2.3
Instant Run is WORKING if I use Run -> Run app; change small things; Run -> Apply Changes;
in this configuration I can make quick iterations (great!!) but I have no breakpoints;
---
Instant Run is NOT WORKING if I use Run -> Debug app; change small things; Run -> Apply Changes;
in this configutaration I have breakpoints; the IDE tells me that it uses instant run, but the activity doesn't get "patched"; the app is getting restarted;
This worked with Android Studio 2.2
My OS:
- Mac OS Sierra 10.12.3
I tested this with Devices, all of these istant run not working
- Emulator with 7.1 Image
- real device: Nexus 7: Android 6.0.1
- real device: Nexus 5 (not the 5X)
- real device: Xiaomi Mi Pad 2 with Android 5.1
Although there is an option on the XIAOMI to enable "autostart" -> did not get it working with instant run; On the other devices I don't have this "magic option";
I recommend others for further bug-reports to tell If you really used Run-> Debug;
Thanks for your investigation
Regards from Austria
Anil
Android Studio 2.3
Instant Run is WORKING if I use Run -> Run app; change small things; Run -> Apply Changes;
in this configuration I can make quick iterations (great!!) but I have no breakpoints;
---
Instant Run is NOT WORKING if I use Run -> Debug app; change small things; Run -> Apply Changes;
in this configutaration I have breakpoints; the IDE tells me that it uses instant run, but the activity doesn't get "patched"; the app is getting restarted;
This worked with Android Studio 2.2
My OS:
- Mac OS Sierra 10.12.3
I tested this with Devices, all of these istant run not working
- Emulator with 7.1 Image
- real device: Nexus 7: Android 6.0.1
- real device: Nexus 5 (not the 5X)
- real device: Xiaomi Mi Pad 2 with Android 5.1
Although there is an option on the XIAOMI to enable "autostart" -> did not get it working with instant run; On the other devices I don't have this "magic option";
I recommend others for further bug-reports to tell If you really used Run-> Debug;
Thanks for your investigation
Regards from Austria
Anil
ma...@gmail.com <ma...@gmail.com> #93
To all facing the problem,
As per the documentation given in the changes made by Android Studio 2.3 "Error: Not found; no service started." is shown when the application is not in the white list or the device is not permitting it to run. As I have an ASUS device, I gave the permission to my application to run in background by changing its state in "Auto-start Manager" as it was stopping it from running in background automatically and the error was gone.
Now I don't have any problems while running the application with "Instant Run" turned on. It should be noted that Instant Run supports devices running 5.0 or above only.
Hope it helped...
Regards
Kavindra Makwana
As per the documentation given in the changes made by Android Studio 2.3 "Error: Not found; no service started." is shown when the application is not in the white list or the device is not permitting it to run. As I have an ASUS device, I gave the permission to my application to run in background by changing its state in "Auto-start Manager" as it was stopping it from running in background automatically and the error was gone.
Now I don't have any problems while running the application with "Instant Run" turned on. It should be noted that Instant Run supports devices running 5.0 or above only.
Hope it helped...
Regards
Kavindra Makwana
sa...@gmail.com <sa...@gmail.com> #94
Solution is here!!
edit build.gradle
write this
android {
compileSdkVersion 24
buildToolsVersion '25.0.0'
defaultConfig {
applicationId "com.salmanshabbir.healthpartnerapp"
minSdkVersion 15
targetSdkVersion 24
multiDexEnabled true
}
remove other thing in android {}
edit build.gradle
write this
android {
compileSdkVersion 24
buildToolsVersion '25.0.0'
defaultConfig {
applicationId "com.salmanshabbir.healthpartnerapp"
minSdkVersion 15
targetSdkVersion 24
multiDexEnabled true
}
remove other thing in android {}
ja...@google.com <ja...@google.com> #95
Hi folks,
We have just published Android Studio 2.4 Preview 2. This issue should be addressed in that build and you no longer need to manually unblock your app from autostart.
We need your help in confirming that it's fixed. If you can try it and let us know, that would be great. We are considering releasing version 2.3.1 to patch this issue.
Thanks!
James
We have just published Android Studio 2.4 Preview 2. This issue should be addressed in that build and you no longer need to manually unblock your app from autostart.
We need your help in confirming that it's fixed. If you can try it and let us know, that would be great. We are considering releasing version 2.3.1 to patch this issue.
Thanks!
James
sh...@gmail.com <sh...@gmail.com> #96
That's cool and will we even get 2.2 run feature back
I. E when we run the app we get the log of app which is running in run tab?
I. E when we run the app we get the log of app which is running in run tab?
ki...@gmail.com <ki...@gmail.com> #97
Is it released in Stable channel?
gs...@gmail.com <gs...@gmail.com> #98
Hello,
Can someone previously experiencing the problem please confirm that AS build 2.4 preview 2 solved their problem?
After the last "stable" update I'm really reluctant to install a preview version.
Can someone previously experiencing the problem please confirm that AS build 2.4 preview 2 solved their problem?
After the last "stable" update I'm really reluctant to install a preview version.
la...@gmail.com <la...@gmail.com> #99
Hi guys,
It worked for me (Asus z380knl, android 6.0.1, windows 8.1). The installation from canary channel just takes me to the download page. Just wanted you to let you know that my antivirus and my windows firewall did not have a friendly reaction to this preview. I have denied auto-start to the tested apps on my device and tested the instant run which worked as expected. The app was started and restarted after implementing changes and the instant run worked fine, but I did not test for anything else.
I'm also attaching my logcat in case you want to have a look (logcat_2.4...).
However, returning to my 2.3 version, your work around does not function anymore. I just updated the SDK and repository to the latest versions released in stable channel, allowed auto-start for the tested apps, restarted my device and the instant run gives the same error:
$ adb shell am startservice com.example.android.justjava/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.example.android.justjava/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.android.justjava/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
So I am also attaching my logcat for 2.3 (first and second attempt to run the app). What do I do now?
Any idea when the stable version for 2.3.1 will be released?
Thanks.
It worked for me (Asus z380knl, android 6.0.1, windows 8.1). The installation from canary channel just takes me to the download page. Just wanted you to let you know that my antivirus and my windows firewall did not have a friendly reaction to this preview. I have denied auto-start to the tested apps on my device and tested the instant run which worked as expected. The app was started and restarted after implementing changes and the instant run worked fine, but I did not test for anything else.
I'm also attaching my logcat in case you want to have a look (logcat_2.4...).
However, returning to my 2.3 version, your work around does not function anymore. I just updated the SDK and repository to the latest versions released in stable channel, allowed auto-start for the tested apps, restarted my device and the instant run gives the same error:
$ adb shell am startservice com.example.android.justjava/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.example.android.justjava/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.android.justjava/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.
So I am also attaching my logcat for 2.3 (first and second attempt to run the app). What do I do now?
Any idea when the stable version for 2.3.1 will be released?
Thanks.
la...@gmail.com <la...@gmail.com> #100
By the way, here are the details of my android studio config and attached you can find a snapshot of the SDK tools I am using.
Android Studio 2.3
Build #AI-162.3764568, built on February 24, 2017
JRE: 1.8.0_112-release-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Android Studio 2.3
Build #AI-162.3764568, built on February 24, 2017
JRE: 1.8.0_112-release-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
la...@gmail.com <la...@gmail.com> #101
[Comment deleted]
ja...@google.com <ja...@google.com> #102
@Laura1805te, I can't think of any reason why the workaround would not work anymore in 2.3. Only thing I can think of is to make sure that your app is completely uninstalled and to make sure you are unblocking the right app.
Thank you very much for verifying that it's working in 2.4 Preview 2. For other folks who may want to try, you can get the latest 2.4 Preview version here:tools.android.com/download/studio/canary/latest/
Thank you very much for verifying that it's working in 2.4 Preview 2. For other folks who may want to try, you can get the latest 2.4 Preview version here:
la...@gmail.com <la...@gmail.com> #103
Hi James,
I've tried that. The app updates, but it is not being relaunched by the instant run. Anyway, it's alright, I disabled the Instant Run and I'll be developing like this until your next release on Android Studio.
Thanks.
I've tried that. The app updates, but it is not being relaunched by the instant run. Anyway, it's alright, I disabled the Instant Run and I'll be developing like this until your next release on Android Studio.
Thanks.
an...@gmail.com <an...@gmail.com> #104
Hello Community,
I am really very happy with the new Preview build 2.4 Preview 2 on Mac OS:
Instant Run is working for BOTH configurations:
1# only run without breakpoints
Run -> Run 'app' -> make small changes -> Run Apply Changes
2# debug with breakpoints
Run -> Debug app, make small changes, Run -> Apply Changes
Tested on
- emulator
- nexus 5 real device
- without setting any magic "autostart" options
Thank you for your hard work
and best Regards from Austria
Anil
I am really very happy with the new Preview build 2.4 Preview 2 on Mac OS:
Instant Run is working for BOTH configurations:
1# only run without breakpoints
Run -> Run 'app' -> make small changes -> Run Apply Changes
2# debug with breakpoints
Run -> Debug app, make small changes, Run -> Apply Changes
Tested on
- emulator
- nexus 5 real device
- without setting any magic "autostart" options
Thank you for your hard work
and best Regards from Austria
Anil
ge...@zukinimobile.com <ge...@zukinimobile.com> #105
Had this issue with Galaxy S7 (6.0.1), BlackBerry Priv (6.0.1), and Galaxy Tab N5 (4.4.2)
AS 2.4 Canary build worked for me
George
AS 2.4 Canary build worked for me
George
je...@google.com <je...@google.com>
vs...@google.com <vs...@google.com> #106
The only thing left now is to decide whether the content provider solution needs to be cherry picked into 2.3.
mi...@gmail.com <mi...@gmail.com> #107
Please cherry pick it if you are not going to release 2.4 in the coming weeks. As 2.3 slowed down our development process.
la...@gmail.com <la...@gmail.com> #108
Yep, totally slowed it down, this is not ok considering there is no alternative to developing Android but Android Studio (or at least I don't know any).
bu...@gmail.com <bu...@gmail.com> #109
Please cherry pick it if you are not going to release 2.4 in the coming weeks. As 2.3 slowed down our development process.
gs...@gmail.com <gs...@gmail.com> #110
[Comment deleted]
gs...@gmail.com <gs...@gmail.com> #111
Sorry, bad news. Instant Run still seems to be broken on AS 2.4 Preview 2.
- Using ASUS Z00LD Android 5.0.2 API 21
- Auto-start Manager is disabled on the phone.
- "Skip installation if APK has not changed" is ENABLED in Run configuration
- "Force stop running application before launching activity" is DISABLED in Run configuration
After either Run or Apply Changes;
Application terminated.
Launching app
$ adb install-multiple -r -p com.forplay.app.debug C:\Dev\xxx\xxx\app\build\intermediates\split-apk\debug\slices\slice_3.apk C:\Dev\xxx\xxx\app\build\outputs\apk\app-debug.apk
Split APKs installed
$ adb shell am start -n "com.xxx.app.debug/com.xxx.app.activity.SplashActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Connected to process 28978 on device asus-asus_z00ld-F8AZCY11J975
- Using ASUS Z00LD Android 5.0.2 API 21
- Auto-start Manager is disabled on the phone.
- "Skip installation if APK has not changed" is ENABLED in Run configuration
- "Force stop running application before launching activity" is DISABLED in Run configuration
After either Run or Apply Changes;
Application terminated.
Launching app
$ adb install-multiple -r -p com.forplay.app.debug C:\Dev\xxx\xxx\app\build\intermediates\split-apk\debug\slices\slice_3.apk C:\Dev\xxx\xxx\app\build\outputs\apk\app-debug.apk
Split APKs installed
$ adb shell am start -n "com.xxx.app.debug/com.xxx.app.activity.SplashActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Connected to process 28978 on device asus-asus_z00ld-F8AZCY11J975
ja...@google.com <ja...@google.com> #112
@gsalgun: can you explain what is not working in your last comment? What is the error or erroneous behavior that you are seeing?
gs...@gmail.com <gs...@gmail.com> #113
AS does not apply Instant Run but builds and pushes a new apk every time.
c9...@gmail.com <c9...@gmail.com> #114
Instant Run not working on AS 2.4 P2
After I upgraded my gradle plugin myself, and tried to run my project, it gave me a warning saying I needed to update my project and offered it could upgrade it itself
then the result was it just put 2.3.0-beta1 to my plugin version line
and after that it all goes on a cycle of what I described
I tried AS 2.4 P2 because instant run is broken on AS 2.3
And build times have gone up now, 1 minute and 40 seconds is too long for me
Hope a fix is coming soon
After I upgraded my gradle plugin myself, and tried to run my project, it gave me a warning saying I needed to update my project and offered it could upgrade it itself
then the result was it just put 2.3.0-beta1 to my plugin version line
and after that it all goes on a cycle of what I described
I tried AS 2.4 P2 because instant run is broken on AS 2.3
And build times have gone up now, 1 minute and 40 seconds is too long for me
Hope a fix is coming soon
ja...@google.com <ja...@google.com> #115
gsalgun: are you using multi-process in your app? If so, it is expected that Instant Run will only do cold swaps.
c9177021859: it's strange that it updated your plugin version to 2.3.0-beta1. Can you try changing it to 2.4.0-alpha1 and see if that works? There is not 2.4.0-alpha2 plugin.
c9177021859: it's strange that it updated your plugin version to 2.3.0-beta1. Can you try changing it to 2.4.0-alpha1 and see if that works? There is not 2.4.0-alpha2 plugin.
da...@gmail.com <da...@gmail.com> #117
Hi, most likely these are related to the 64-bit processor libraries. Our team tested on various with devices which have those processors such as Samsung edge, LG V10, OnePlue 3T with apk built using Android Studio 2.3 and they crashed.
ja...@google.com <ja...@google.com> #118
Hi everyone, we just released Android Studio 2.3.1 to address this problem. Please either update to this release from inside Android Studio via the stable channel, or you can download it directly from here: https://developer.android.com/studio/index.html
The button says 2.3 but it will download 2.3.1.
The button says 2.3 but it will download 2.3.1.
ch...@gmail.com <ch...@gmail.com> #119
I updated android studio to 2.3.1 also updated gradle version 2.3.1 in project but still when my instant run enable it's not work on my device.
Device : Xiomi Readmi note 3
OS Version : 6.0.1
Device : Xiomi Readmi note 3
OS Version : 6.0.1
ki...@gmail.com <ki...@gmail.com> #120
It's working for Asus device now but only issue is i am not able see log messages in Run window i need to check in Android Monitor Window.
ki...@gmail.com <ki...@gmail.com> #121
one more issue is app installed every time for instance run option
ja...@google.com <ja...@google.com> #122
chavdasagar27, can you please let us know what specifically isn't working? Any details would be helpful.
kishangohel23, does your app use multiple process? If so, this behavior is expected. I don't think the log message issue is related to Instant Run.
kishangohel23, does your app use multiple process? If so, this behavior is expected. I don't think the log message issue is related to Instant Run.
ya...@gmail.com <ya...@gmail.com> #123
after update to as 2.3.1,this problem is no longer happen.
ki...@gmail.com <ki...@gmail.com> #124
In studio 2.2.2 we can see log messages in Run but after instance run change in 2.3 i am not able to see in Run window.
Currently i am using 2.2.2 as i have that installer, may be i will switch to latest version if i can find fully stable version.
Thanks for your information.
Currently i am using 2.2.2 as i have that installer, may be i will switch to latest version if i can find fully stable version.
Thanks for your information.
[Deleted User] <[Deleted User]> #125
same here. using emulator. AS 2.3
db...@gmail.com <db...@gmail.com> #126
Still suffering from this problem in both 2.3.1 stable & 2.4 Preview 5.
Physical Nougat & 'O' devices run my app fine, but physical (6.0.1) Marshmallow devices fail (Can't test Emulator as I'm currently stuck with an AMD CPU on Windows which is terrible for emulation solutions).
Tested classpaths:
classpath 'com.android.tools.build:gradle:2.4.0-alpha5' (in both versions of the IDE)
classpath 'com.android.tools.build:gradle:2.3.1' (in just 2.3.1 IDE)
Error from logcat:
Caused by: java.lang.ClassNotFoundException: Didn't find class "package.name.MainActivity" on path: DexPathList[[zip file "/data/app/package.name-2/base.apk", zip file "/data/app/package.name-2/split_lib_dependencies_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_0_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_1_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_2_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_3_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_4_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_5_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_6_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_7_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_8_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_9_apk.apk"],nativeLibraryDirectories=[/data/app/package.name-2/lib/arm, /vendor/lib, /system/lib]]
Physical Nougat & 'O' devices run my app fine, but physical (6.0.1) Marshmallow devices fail (Can't test Emulator as I'm currently stuck with an AMD CPU on Windows which is terrible for emulation solutions).
Tested classpaths:
classpath 'com.android.tools.build:gradle:2.4.0-alpha5' (in both versions of the IDE)
classpath 'com.android.tools.build:gradle:2.3.1' (in just 2.3.1 IDE)
Error from logcat:
Caused by: java.lang.ClassNotFoundException: Didn't find class "package.name.MainActivity" on path: DexPathList[[zip file "/data/app/package.name-2/base.apk", zip file "/data/app/package.name-2/split_lib_dependencies_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_0_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_1_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_2_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_3_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_4_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_5_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_6_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_7_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_8_apk.apk", zip file "/data/app/package.name-2/split_lib_slice_9_apk.apk"],nativeLibraryDirectories=[/data/app/package.name-2/lib/arm, /vendor/lib, /system/lib]]
gh...@gmail.com <gh...@gmail.com> #127
Мудозвоны, вы когда почините свою хуйню?! Дайте людям работать нормально, кретины криворукие.
az...@gmail.com <az...@gmail.com> #128
Fixed my problem!
sa...@gmail.com <sa...@gmail.com> #129
This problem affected me when I used my Sony Xperia M running AOSP 7.1.1 (https://forum.xda-developers.com/xperia-m/orig-development/rom-aosp-nougat-7-0-t3448481 ).
I tried to do a manual update in Android Studio to get 2.3.1, but it said it didn't find any updates, so I had to do a full install.
2.3.1 fixed the problem. Thanks!
I tried to do a manual update in Android Studio to get 2.3.1, but it said it didn't find any updates, so I had to do a full install.
2.3.1 fixed the problem. Thanks!
pr...@gmail.com <pr...@gmail.com> #130
I'm working on a Unity project and unable to Build and Run my application for Android 7.0 (Google Pixel). It appears the problem is still not fixed for Android 7. Can you please update how to fix this? I'm unable to debug my application.
ta...@gmail.com <ta...@gmail.com> #131
Hello, I have the same problem with AS 2.3.1. I am using the Genymotion emulator with a 5.1.0 system image
sc...@gmail.com <sc...@gmail.com> #132
Hello, I have the same problem using
Android Studio 2.3.1
Build #AI-162.3871768, built on April 1, 2017
JRE: 1.8.0_112-release-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
on Genymotion emulator with 5.1.0 system image with Google Play Services
Android Studio 2.3.1
Build #AI-162.3871768, built on April 1, 2017
JRE: 1.8.0_112-release-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
on Genymotion emulator with 5.1.0 system image with Google Play Services
st...@gmail.com <st...@gmail.com> #133
I'm having the same problem with Android Studio 2.3.1 and my device (Nexus 6P) using Instant Run -> Debug
je...@google.com <je...@google.com> #134
can you make sure you use the android gradle plugin 2.3.1 in your build.gradle.
can you please attach the logcat once you verified.
can you please attach the logcat once you verified.
li...@gmail.com <li...@gmail.com> #135
Hey there. I'm having the same problem:
Error while executing: am startservice com.example.userupt.sistemas/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.userupt.sistemas/com.android.tools.fd.runtime.InstantRunService }
Error: app is in background uid null
I already tried turning off Instant Run but didn't work.
Error while executing: am startservice com.example.userupt.sistemas/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.userupt.sistemas/com.android.tools.fd.runtime.InstantRunService }
Error: app is in background uid null
I already tried turning off Instant Run but didn't work.
as...@gmail.com <as...@gmail.com> #136
I'm having this same issue on my emulators, would you expect that to happen? Even with the Pixel running API 23.
jo...@drachenschloss.org <jo...@drachenschloss.org> #137
It seems that InstantRun was fine in emulators up until 2.3.0 of the android gradle plugin, but with 2.3.1 something went wrong. I was able to get InstantRun back to working in an API 22 emulator by backing down to 2.3.0. One report on Jetbrains youtrack seems to indicate this has some API sensitivity (his emulator worked fine under Android 4.X, but not 5.0 or later)
https://youtrack.jetbrains.com/issue/IDEA-156185
buildscript {
...
dependencies {
classpath 'com.android.tools.build:gradle:2.3.0'
}
}
The irony here is that 2.3.1, 2.3.2, and 2.3.3 were intended to fix this sort of problem when running on certain physical devices, so it appears to be a pick-your-poison situation at the moment.
buildscript {
...
dependencies {
classpath 'com.android.tools.build:gradle:2.3.0'
}
}
The irony here is that 2.3.1, 2.3.2, and 2.3.3 were intended to fix this sort of problem when running on certain physical devices, so it appears to be a pick-your-poison situation at the moment.
Description
Instant Run Report: f498257620000000
03/03 15:58:18: Launching app
$ adb shell am startservice com.kishan.photogallery/com.android.tools.fd.runtime.InstantRunService
Error while executing: am startservice com.kishan.photogallery/com.android.tools.fd.runtime.InstantRunService
Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.kishan.photogallery/com.android.tools.fd.runtime.InstantRunService }
Error: Not found; no service started.