android studio 2.3 instant run not working on some devices [37137335]

Fixed

Bug

[AOSP] duplicate

Migrated-Tools-intellij

Migrated-Tools-Instant Run

[AOSP] assigned

[AOSP] Version-Studio-2.3

[AOSP] Released

[AOSP] win8.1

NeedsInfo

Migrated-Tools-Studio

Status Update

No update yet.

Description

ki...@gmail.com

created issue #1

Mar 3, 2017 10:30AM

Build: 2.3
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.

Comments

gh...@gmail.com <gh...@gmail.com> #2Mar 4, 2017 12:20AM

Thanks for reporting, would you be able to provide a reproducible case for when this incremental error occurs? The task for merging java resources has multiple incremental inputs depending on where the java resource originates - providing a sample project where this issue can be triggered will help the team narrow what task input is impacted. A longer stacktrace of the issue from #1 might also be useful.

go...@gmail.com <go...@gmail.com> #3Mar 4, 2017 02:54PM

Unfortunately I cannot reproduce it consistently. In fact I don't even know what triggers it (it seems to be some combination of changes).

Like I mentioned above, my hunch is that this is due to having several modules with the same name (impl). The resource in question (impl_debug.kotlin_module) contains the name of the Gradle module and it likely means that there will be conflicts since there are several modules with the same name.

The stack trace looks like this:

org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:mergeDebugJavaResource'.	
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:149)	
	at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)	
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:147)	
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:135)	
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)	
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)	
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)	
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:74)	
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)	
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)	
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:42)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:337)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:324)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:317)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:303)	
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:463)	
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:380)	
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)	
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:49)	
Caused by: org.gradle.workers.internal.DefaultWorkerExecutor$WorkExecutionException: A failure occurred while executing com.android.build.gradle.internal.tasks.MergeJavaResWorkAction	
	at org.gradle.workers.internal.DefaultWorkerExecutor$WorkItemExecution.waitForCompletion(DefaultWorkerExecutor.java:283)	
	at org.gradle.internal.work.DefaultAsyncWorkTracker.lambda$waitForItemsAndGatherFailures$2(DefaultAsyncWorkTracker.java:130)	
	at org.gradle.internal.Factories$1.create(Factories.java:31)	
	at org.gradle.internal.work.DefaultWorkerLeaseService.withoutLocks(DefaultWorkerLeaseService.java:321)	
	at org.gradle.internal.work.DefaultWorkerLeaseService.withoutLocks(DefaultWorkerLeaseService.java:304)	
	at org.gradle.internal.work.DefaultWorkerLeaseService.withoutLock(DefaultWorkerLeaseService.java:309)	
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForItemsAndGatherFailures(DefaultAsyncWorkTracker.java:126)	
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForItemsAndGatherFailures(DefaultAsyncWorkTracker.java:92)	
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForAll(DefaultAsyncWorkTracker.java:78)	
	at org.gradle.internal.work.DefaultAsyncWorkTracker.waitForCompletion(DefaultAsyncWorkTracker.java:66)	
	at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:250)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)	
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)	
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:227)	
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:210)	
	at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:193)	
	at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:166)	
	at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:105)	
	at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:44)	
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:59)	
	at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:56)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)	
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)	
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:56)	
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:44)	
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:67)	
	at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:37)	
	at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:41)	
	at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:74)	
	at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)	
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:50)	
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:28)	
	at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.executeDelegateBroadcastingChanges(CaptureStateAfterExecutionStep.java:100)	
	at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:72)	
	at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:50)	
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:40)	
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:29)	
	at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:166)	
	at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:70)	
	at org.gradle.internal.Either$Right.fold(Either.java:175)	
	at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:59)	
	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:68)	
	at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:46)	
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:36)	
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:25)	
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:36)	
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:22)	
	at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:91)	
	at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:55)	
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)	
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:37)	
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:65)	
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:36)	
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)	
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)	
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:76)	
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:37)	
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:94)	
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:49)	
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:71)	
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:45)	
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.executeWithNonEmptySources(SkipEmptyWorkStep.java:177)	
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:81)	
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:53)	
	at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:32)	
	at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:21)	
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)	
	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:36)	
	at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:23)	
	at org.gradle.internal.execution.steps.CleanupStaleOutputsStep.execute(CleanupStaleOutputsStep.java:75)	
	at org.gradle.internal.execution.steps.CleanupStaleOutputsStep.execute(CleanupStaleOutputsStep.java:41)	
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:32)	
	at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:287)	
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)	
	at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:21)	
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)	
	at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)	
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:47)	
	at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:34)	
	at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:64)	
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:146)	
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:135)	
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)	
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)	
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)	
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:74)	
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)	
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)	
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)	
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:42)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:337)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:324)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:317)	
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:303)	
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:463)	
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:380)	
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)	
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:49)	
Caused by: java.lang.IllegalStateException: Unexpected combination of states CHANGED, REMOVED for file /path/to/module/build/intermediates/java_res/debug/out/META-INF/impl_debug.kotlin_module	
	at com.android.build.gradle.internal.tasks.IncrementalFileMergerTaskUtils.collectChanges(IncrementalFileMergerTaskUtils.kt:275)	
	at com.android.build.gradle.internal.tasks.IncrementalFileMergerTaskUtils.toInputs(IncrementalFileMergerTaskUtils.kt:229)	
	at com.android.build.gradle.internal.tasks.MergeJavaResWorkAction.run(MergeJavaResWorkAction.kt:68)	
	at com.android.build.gradle.internal.profile.ProfileAwareWorkAction.execute(ProfileAwareWorkAction.kt:74)	
	at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:63)	
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:66)	
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:62)	
	at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:100)	
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1.lambda$execute$0(NoIsolationWorkerFactory.java:62)	
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:44)	
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:41)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)	
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)	
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)	
	at org.gradle.workers.internal.AbstractWorker.executeWrappedInBuildOperation(AbstractWorker.java:41)	
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1.execute(NoIsolationWorkerFactory.java:59)	
	at org.gradle.workers.internal.DefaultWorkerExecutor.lambda$submitWork$0(DefaultWorkerExecutor.java:169)	
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runExecution(DefaultConditionalExecutionQueue.java:187)	
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.access$700(DefaultConditionalExecutionQueue.java:120)	
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner$1.run(DefaultConditionalExecutionQueue.java:162)	
	at org.gradle.internal.Factories$1.create(Factories.java:31)	
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:249)	
	at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:109)	
	at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:114)	
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runBatch(DefaultConditionalExecutionQueue.java:157)	
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.run(DefaultConditionalExecutionQueue.java:126)	
	... 2 more

so...@gmail.com <so...@gmail.com> #4Mar 4, 2017 09:49PM

Thanks for the additional information. I have refactored the Java Resource merging incremental handling to better handle source file path roots - so hopefully this is enough to eliminate the possibility of collisions between java resources. However, it would be great to test these changes resolve your issue. My current assumption is that the issue occurs when there is a library structure where there are two modules of the same name nested within two differently named modules such as:

app
foo_lib
  foo
bar_lib
  foo

Could you confirm that this setup is similar in your project or if not, can you please provide your project structure or even a project if possible?

ru...@gmail.com <ru...@gmail.com> #5Mar 5, 2017 11:51AM

Yes, our setup looks like this:

:features
  :feature1
    :public
    :impl
  :feature2
    :public
    :impl
...

The modules mentioned in the error would always be one of these impl or public modules.

Unfortunately I cannot share our project and even if I could, I don't know how to replicate the issue.

I will say though that since upgrading to the latest AGP 8.2 alpha I have not seen the issue so it's possible that it's already been fixed as a part of another change.

ch...@gmail.com <ch...@gmail.com> #6Mar 6, 2017 01:00AM

Oops, spoke too soon. It just happened.

Once it happens ever run will trigger it so if you need me to log or try something let me know. Removing the app level build directory fixes the issue.

ki...@gmail.com <ki...@gmail.com> #7Mar 6, 2017 05:50AM

BTW, what is the target release for this fix?

ki...@gmail.com <ki...@gmail.com> #8Mar 6, 2017 05:51AM

For now, we've worked around this by adding this to our Kotlin convention plugin:

tasks.withType<KotlinCompile>().configureEach {
    compilerOptions {
        moduleName.set(path.removePrefix(":").replace(":", "_"))
    }
}

la...@gmail.com <la...@gmail.com> #9Mar 6, 2017 11:06AM

Thanks for sharing the workaround. I needed to slightly adapt it to work for us, otherwise kapt and ksp would fail because they'd expect different names for internal symbols.

tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompilationTask.class).configureEach {
    if (!name.containsIgnoreCase("ksp") && !name.containsIgnoreCase("kapt")) {
       compilerOptions {
       moduleName.set(path.substring(1).replace(":", "_"))
    }
}

a....@gmail.com <a....@gmail.com> #10Mar 6, 2017 01:44PM

Actually, I found a better way to solve this. The default module name is based on the base plugin's archivesName property. So you can do this instead:

base {
    archivesName.set(path.removePrefix(":").replace(":", "_"))
}

uc...@google.com <uc...@google.com> #11Mar 6, 2017 07:25PM

It seems AGP is not correctly excluding kotlin_module files during java resource merging, so we'd expect a collision - although this error message isn't clear.

Until we release we have a fix for the issue, a workaround may be to add packagingOptions { exclude 'META-INF/*.kotlin_module' } to the build.gradle conflicting libraries, so AGP doesn't attempt to merge them.

uc...@google.com <uc...@google.com> #17Mar 6, 2017 08:59PM

I have same issue again after Comment #14
I'm not sure, but I'm guessing that error was raised again after applied AGP 8.2

mi...@gmail.com <mi...@gmail.com> #18Mar 6, 2017 09:01PM

In my case, module A and module B have implementations of interface Xxx which can be loaded by AutoService.

and MergeJavaResourcesTask was failed of app C while merge META-INF/services/Xxx from module A and module B

gh...@gmail.com <gh...@gmail.com> #19Mar 6, 2017 09:58PM

I had previously applied the workaround from #10 to our build, however it caused packaging issues that manifested as runtime crashes. I'll be taking a second look at the workaround to see if I can fix our previous issues with it since we are starting to see this problem happen a lot more frequently. An issue with Anvil has been causing our developers to use --rerun and --rerun-tasks more frequently than usual, which masks the issue here. With the latest beta release of anvil, those options are no longer needed and this bug pops up a lot more frequently. We are using AGP 8.2.2 currently

je...@google.com <je...@google.com> #21Mar 6, 2017 11:49PM

Have been having the same issue in recent builds, rm -rf app/build is what helped in my case.

gh...@gmail.com <gh...@gmail.com> #23Mar 7, 2017 12:23AM

This is mitigated in 22ea772c902a9891a6023ed1ebdc832871775ba6 but I am suspicious there are other lurking issues by inspection and from #comment19

1.PNG

46 KB

View

Download

2.PNG

161 KB

View

Download

pr...@gmail.com <pr...@gmail.com> #24Mar 7, 2017 02:03AM

Filed issue 327603250 to follow up, marking this as closed as the initial issue should no longer directly bite.

do...@gmail.com <do...@gmail.com> #25Mar 7, 2017 07:50AM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Jellyfish | 2023.3.1 Canary 12
Android Gradle Plugin 8.4.0-alpha12

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

ya...@gmail.com <ya...@gmail.com> #26Mar 7, 2017 09:24AM

AGP 8.3 final version was released at today.
Could this fix be applied to AGP 8.3.x patch version?
Or is there another solution that can alleviate this issue?

an...@gmail.com <an...@gmail.com> #27Mar 7, 2017 11:07AM

Re #comment19 - are you using merge or pickFirst in packagingOptions?

lo...@gmail.com <lo...@gmail.com> #28Mar 7, 2017 04:15PM

No, we have some exclude rules but don't use either merge or pickFirst

ja...@google.com <ja...@google.com> #29Mar 7, 2017 05:26PM

The fixes for this issue are now also available in:

Android Studio Iguana | 2023.2.1 Patch 1
Android Gradle Plugin 8.3.1

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

ch...@gmail.com <ch...@gmail.com> #30Mar 7, 2017 05:32PM

I'm facing this on a One Plus 3T.

ni...@gmail.com <ni...@gmail.com> #31Mar 7, 2017 05:39PM

I'm using ASUS_Z00AD with Android 5.0 (API 21)

mi...@gmail.com <mi...@gmail.com> #32Mar 7, 2017 05:41PM

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.

ja...@gmail.com <ja...@gmail.com> #33Mar 7, 2017 06:12PM

I'm having the same issue on ASUS_Z011D with Android 6.0.1

ja...@gmail.com <ja...@gmail.com> #34Mar 7, 2017 06:20PM

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> #35Mar 7, 2017 06:42PM

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>:

vs...@google.com <vs...@google.com> #37Mar 7, 2017 08:35PM

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.

ru...@gmail.com <ru...@gmail.com> #38Mar 7, 2017 10:32PM

Instant Run doesnt work on Meizu M1 Metal. Doesnt launch app.

sf...@gmail.com <sf...@gmail.com> #39Mar 8, 2017 02:10AM

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

sf...@gmail.com <sf...@gmail.com> #40Mar 8, 2017 02:34AM

[Comment deleted]

sf...@gmail.com <sf...@gmail.com> #41Mar 8, 2017 02:53AM

gradle version:gradle-3.3-all
buildToolsVersion '25.0.0'
minSdkVersion 16
targetSdkVersion 25

ki...@gmail.com <ki...@gmail.com> #42Mar 8, 2017 05:24AM

package: com.kishan.testproject
Device: ASUS_Z008
Android Studio 2.3
Windows 8

logcat.txt

973 KB

View

Download

ya...@gmail.com <ya...@gmail.com> #43Mar 8, 2017 05:47AM

here is my log and phone info

as2.3.txt

430 B

View

Download

as2.3.png

87 KB

View

Download

ee...@gmail.com <ee...@gmail.com> #44Mar 8, 2017 05:56AM

Can't use instant run on android device with Android version > 5.0.
Uncheck the instant run in settings solved my problems.

ja...@gmail.com <ja...@gmail.com> #45Mar 8, 2017 05:57AM

Here's the logcat.txt as requested in update #38

logcat.txt

928 KB

View

Download

an...@gmail.com <an...@gmail.com> #46Mar 8, 2017 07:00AM

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

logcat.txt

4.5 MB

View

Download

ja...@google.com <ja...@google.com> #47Mar 8, 2017 08:12AM

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!

qq...@gmail.com <qq...@gmail.com> #48Mar 8, 2017 08:17AM

hey，James，my device is MeiZu note3 with Flyme6。thx。

et...@gmail.com <et...@gmail.com> #49Mar 8, 2017 08:46AM

MeiZu MX5 with Flyme6 thx.

et...@gmail.com <et...@gmail.com> #50Mar 8, 2017 08:50AM

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.

lo...@gmail.com <lo...@gmail.com> #51Mar 8, 2017 08:53AM

[Comment deleted]

logcat.txt

135 KB

View

Download

do...@gmail.com <do...@gmail.com> #52Mar 8, 2017 01:08PM

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> #53Mar 8, 2017 03:18PM

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

la...@gmail.com <la...@gmail.com> #54Mar 8, 2017 08:04PM

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.

log.txt

417 KB

View

Download

log2.txt

103 KB

View

Download

an...@gmail.com <an...@gmail.com> #55Mar 8, 2017 08:44PM

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

ee...@gmail.com <ee...@gmail.com> #56Mar 9, 2017 03:12AM

device: HUAWEI TAG-AL00
android version: 5.1

ca...@gmail.com <ca...@gmail.com> #57Mar 9, 2017 04:03AM

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

solved.png

23 KB

View

Download

la...@gmail.com <la...@gmail.com> #58Mar 9, 2017 07:06AM

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.

[Deleted User] <[Deleted User]> #59Mar 9, 2017 02:35PM

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.

me...@outlook.com <me...@outlook.com> #60Mar 9, 2017 03:38PM

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

ja...@google.com <ja...@google.com> #61Mar 9, 2017 07:22PM

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> #62Mar 9, 2017 07:27PM

The issue is present when using my physical device (a OnePlus 3T).

I can't reproduce it on an API 24 emulator.

la...@gmail.com <la...@gmail.com> #63Mar 9, 2017 08:03PM

The issue does not reproduce on emulator (API 25 emulator).

ja...@google.com <ja...@google.com> #64Mar 10, 2017 12:02AM

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.

ni...@gmail.com <ni...@gmail.com> #66Mar 10, 2017 02:33AM

Instant run now working on ASUS_Z00AD. Thank you James.

am...@gmail.com <am...@gmail.com> #67Mar 10, 2017 03:24AM

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> #68Mar 10, 2017 04:33AM

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> #69Mar 10, 2017 05:06AM

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?

se...@gmail.com <se...@gmail.com> #70Mar 10, 2017 05:29AM

Same issue with Studio 2.3 (Win8.1 Pro) on Nexus5 and Nexus5x.
Also sometimes in debug Studio freezes and not responding.

la...@gmail.com <la...@gmail.com> #71Mar 10, 2017 07:30AM

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?

la...@gmail.com <la...@gmail.com> #72Mar 10, 2017 07:34AM

Also here is my new logcat after applying your solution (ASUS Z380KNL).

android_monitor_logcat.txt

11 KB

View

Download

ADM_logcat.txt

587 KB

View

Download

mi...@gmail.com <mi...@gmail.com> #73Mar 10, 2017 07:55AM

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.

la...@gmail.com <la...@gmail.com> #74Mar 10, 2017 12:52PM

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.

et...@gmail.com <et...@gmail.com> #75Mar 10, 2017 03:17PM

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.

et...@gmail.com <et...@gmail.com> #76Mar 10, 2017 03:17PM

[Comment deleted]

ja...@google.com <ja...@google.com> #77Mar 10, 2017 04:15PM

Assigned to ja...@google.com.

Thanks for verifying everyone. I am downgrading this issue because of the workaround.

le...@gmail.com <le...@gmail.com> #78Mar 10, 2017 05:13PM

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> #79Mar 10, 2017 06:06PM

Fooking askewhand developers. Don't downgrading this issue!! Fix this bug!! Уебаны криворукие...

vs...@google.com <vs...@google.com> #80Mar 10, 2017 09:23PM

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.

gh...@gmail.com <gh...@gmail.com> #81Mar 10, 2017 09:29PM

How long will we wait for the 2.4 update??

la...@gmail.com <la...@gmail.com> #84Mar 11, 2017 07:30AM

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]> #85Mar 11, 2017 02:17PM

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)

je...@gmail.com <je...@gmail.com> #86Mar 13, 2017 04:12AM

@ #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> #87Mar 13, 2017 08:17AM

In HTC Desire EYE or General Mobile GM5 Where is that auto-launch ? Thanks for sharing.

yy...@gmail.com <yy...@gmail.com> #88Mar 13, 2017 09:15AM

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 .....

vs...@google.com <vs...@google.com> #89Mar 13, 2017 06:22PM

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.

[Deleted User] <[Deleted User]> #90Mar 14, 2017 03:50PM

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> #91Mar 15, 2017 08:15PM

[Comment deleted]

an...@gmail.com <an...@gmail.com> #92Mar 15, 2017 08:18PM

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

ma...@gmail.com <ma...@gmail.com> #93Mar 16, 2017 11:45AM

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

sa...@gmail.com <sa...@gmail.com> #94Mar 16, 2017 12:35PM

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 {}

ja...@google.com <ja...@google.com> #95Mar 16, 2017 07:05PM

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

sh...@gmail.com <sh...@gmail.com> #96Mar 16, 2017 07:19PM

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?

ki...@gmail.com <ki...@gmail.com> #97Mar 17, 2017 04:35AM

Is it released in Stable channel?

gs...@gmail.com <gs...@gmail.com> #98Mar 17, 2017 08:39AM

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.

la...@gmail.com <la...@gmail.com> #99Mar 17, 2017 09:35AM

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.

logcat_2.3.txt

1 MB

View

Download

logcat_2.3_second_attempt.txt

1 MB

View

Download

logcat_2.4_preview_2.txt

1 MB

View

Download

la...@gmail.com <la...@gmail.com> #100Mar 17, 2017 09:42AM

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

AS_2.3.png

30 KB

View

Download

la...@gmail.com <la...@gmail.com> #101Mar 17, 2017 10:00AM

[Comment deleted]

logcat_app1.txt

1 MB

View

Download

logcat_app2.txt

4.7 KB

View

Download

ja...@google.com <ja...@google.com> #102Mar 17, 2017 04:51PM

@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/

la...@gmail.com <la...@gmail.com> #103Mar 17, 2017 05:39PM

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.

an...@gmail.com <an...@gmail.com> #104Mar 17, 2017 08:40PM

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

ge...@zukinimobile.com <ge...@zukinimobile.com> #105Mar 17, 2017 10:23PM

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

je...@google.com <je...@google.com> Mar 20, 2017 06:57PM

Reassigned to vs...@google.com.

vs...@google.com <vs...@google.com> #106Mar 20, 2017 07:29PM

Reassigned to je...@google.com.

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> #107Mar 20, 2017 07:48PM

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> #108Mar 20, 2017 08:24PM

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> #109Mar 21, 2017 04:49AM

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> #110Mar 21, 2017 06:42AM

[Comment deleted]

gs...@gmail.com <gs...@gmail.com> #111Mar 21, 2017 08:55AM

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

ja...@google.com <ja...@google.com> #112Mar 21, 2017 11:45PM

@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> #113Mar 22, 2017 06:43AM

AS does not apply Instant Run but builds and pushes a new apk every time.

c9...@gmail.com <c9...@gmail.com> #114Mar 23, 2017 05:38PM

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

ja...@google.com <ja...@google.com> #115Mar 27, 2017 04:50PM

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.

da...@gmail.com <da...@gmail.com> #117Apr 4, 2017 02:52AM

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> #118Apr 5, 2017 12:14AM

Marked as fixed.

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.

ch...@gmail.com <ch...@gmail.com> #119Apr 5, 2017 05:23AM

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

ki...@gmail.com <ki...@gmail.com> #120Apr 5, 2017 05:50AM

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> #121Apr 5, 2017 06:08AM

one more issue is app installed every time for instance run option

ja...@google.com <ja...@google.com> #122Apr 5, 2017 03:24PM

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.

ya...@gmail.com <ya...@gmail.com> #123Apr 6, 2017 01:57AM

after update to as 2.3.1,this problem is no longer happen.

ki...@gmail.com <ki...@gmail.com> #124Apr 6, 2017 04:57AM

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.

[Deleted User] <[Deleted User]> #125Apr 7, 2017 01:58PM

same here. using emulator. AS 2.3

db...@gmail.com <db...@gmail.com> #126Apr 10, 2017 10:07PM

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]]

gh...@gmail.com <gh...@gmail.com> #127Apr 22, 2017 06:24AM

Мудозвоны, вы когда почините свою хуйню?! Дайте людям работать нормально, кретины криворукие.

az...@gmail.com <az...@gmail.com> #128Apr 22, 2017 06:17PM

Fixed my problem!

sa...@gmail.com <sa...@gmail.com> #129Apr 25, 2017 12:38AM

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!

pr...@gmail.com <pr...@gmail.com> #130Apr 26, 2017 06:23AM

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> #131May 1, 2017 08:27AM

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> #132May 4, 2017 02:46PM

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

st...@gmail.com <st...@gmail.com> #133May 8, 2017 03:49PM

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> #134May 11, 2017 04:33AM

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.

li...@gmail.com <li...@gmail.com> #135Jun 27, 2017 01:05AM

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.

as...@gmail.com <as...@gmail.com> #136Jul 24, 2017 05:46PM

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> #137Aug 6, 2017 08:47AM

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.

Issue 37137335

Description

Issue summary

Comments

gh...@gmail.com <gh...@gmail.com> #2Mar 4, 2017 12:20AM

go...@gmail.com <go...@gmail.com> #3Mar 4, 2017 02:54PM

so...@gmail.com <so...@gmail.com> #4Mar 4, 2017 09:49PM

ru...@gmail.com <ru...@gmail.com> #5Mar 5, 2017 11:51AM

ch...@gmail.com <ch...@gmail.com> #6Mar 6, 2017 01:00AM

ki...@gmail.com <ki...@gmail.com> #7Mar 6, 2017 05:50AM

ki...@gmail.com <ki...@gmail.com> #8Mar 6, 2017 05:51AM

la...@gmail.com <la...@gmail.com> #9Mar 6, 2017 11:06AM

a....@gmail.com <a....@gmail.com> #10Mar 6, 2017 01:44PM

uc...@google.com <uc...@google.com> #11Mar 6, 2017 07:25PM

uc...@google.com <uc...@google.com> #17Mar 6, 2017 08:59PM

mi...@gmail.com <mi...@gmail.com> #18Mar 6, 2017 09:01PM

gh...@gmail.com <gh...@gmail.com> #19Mar 6, 2017 09:58PM

je...@google.com <je...@google.com> #21Mar 6, 2017 11:49PM

gh...@gmail.com <gh...@gmail.com> #23Mar 7, 2017 12:23AM

pr...@gmail.com <pr...@gmail.com> #24Mar 7, 2017 02:03AM

do...@gmail.com <do...@gmail.com> #25Mar 7, 2017 07:50AM

ya...@gmail.com <ya...@gmail.com> #26Mar 7, 2017 09:24AM

an...@gmail.com <an...@gmail.com> #27Mar 7, 2017 11:07AM

lo...@gmail.com <lo...@gmail.com> #28Mar 7, 2017 04:15PM

ja...@google.com <ja...@google.com> #29Mar 7, 2017 05:26PM

ch...@gmail.com <ch...@gmail.com> #30Mar 7, 2017 05:32PM

ni...@gmail.com <ni...@gmail.com> #31Mar 7, 2017 05:39PM

mi...@gmail.com <mi...@gmail.com> #32Mar 7, 2017 05:41PM

ja...@gmail.com <ja...@gmail.com> #33Mar 7, 2017 06:12PM

ja...@gmail.com <ja...@gmail.com> #34Mar 7, 2017 06:20PM

an...@gmail.com <an...@gmail.com> #35Mar 7, 2017 06:42PM

vs...@google.com <vs...@google.com> #37Mar 7, 2017 08:35PM

ru...@gmail.com <ru...@gmail.com> #38Mar 7, 2017 10:32PM

sf...@gmail.com <sf...@gmail.com> #39Mar 8, 2017 02:10AM

sf...@gmail.com <sf...@gmail.com> #40Mar 8, 2017 02:34AM

sf...@gmail.com <sf...@gmail.com> #41Mar 8, 2017 02:53AM

ki...@gmail.com <ki...@gmail.com> #42Mar 8, 2017 05:24AM

ya...@gmail.com <ya...@gmail.com> #43Mar 8, 2017 05:47AM

ee...@gmail.com <ee...@gmail.com> #44Mar 8, 2017 05:56AM

ja...@gmail.com <ja...@gmail.com> #45Mar 8, 2017 05:57AM

an...@gmail.com <an...@gmail.com> #46Mar 8, 2017 07:00AM

ja...@google.com <ja...@google.com> #47Mar 8, 2017 08:12AM

qq...@gmail.com <qq...@gmail.com> #48Mar 8, 2017 08:17AM

et...@gmail.com <et...@gmail.com> #49Mar 8, 2017 08:46AM

et...@gmail.com <et...@gmail.com> #50Mar 8, 2017 08:50AM

lo...@gmail.com <lo...@gmail.com> #51Mar 8, 2017 08:53AM

do...@gmail.com <do...@gmail.com> #52Mar 8, 2017 01:08PM

pa...@gmail.com <pa...@gmail.com> #53Mar 8, 2017 03:18PM

la...@gmail.com <la...@gmail.com> #54Mar 8, 2017 08:04PM

an...@gmail.com <an...@gmail.com> #55Mar 8, 2017 08:44PM

ee...@gmail.com <ee...@gmail.com> #56Mar 9, 2017 03:12AM

ca...@gmail.com <ca...@gmail.com> #57Mar 9, 2017 04:03AM

la...@gmail.com <la...@gmail.com> #58Mar 9, 2017 07:06AM

[Deleted User] <[Deleted User]> #59Mar 9, 2017 02:35PM

me...@outlook.com <me...@outlook.com> #60Mar 9, 2017 03:38PM

ja...@google.com <ja...@google.com> #61Mar 9, 2017 07:22PM

ch...@gmail.com <ch...@gmail.com> #62Mar 9, 2017 07:27PM

la...@gmail.com <la...@gmail.com> #63Mar 9, 2017 08:03PM

ja...@google.com <ja...@google.com> #64Mar 10, 2017 12:02AM

ni...@gmail.com <ni...@gmail.com> #66Mar 10, 2017 02:33AM

am...@gmail.com <am...@gmail.com> #67Mar 10, 2017 03:24AM

ar...@gmail.com <ar...@gmail.com> #68Mar 10, 2017 04:33AM

ki...@gmail.com <ki...@gmail.com> #69Mar 10, 2017 05:06AM

se...@gmail.com <se...@gmail.com> #70Mar 10, 2017 05:29AM

la...@gmail.com <la...@gmail.com> #71Mar 10, 2017 07:30AM

la...@gmail.com <la...@gmail.com> #72Mar 10, 2017 07:34AM

mi...@gmail.com <mi...@gmail.com> #73Mar 10, 2017 07:55AM

la...@gmail.com <la...@gmail.com> #74Mar 10, 2017 12:52PM

et...@gmail.com <et...@gmail.com> #75Mar 10, 2017 03:17PM

et...@gmail.com <et...@gmail.com> #76Mar 10, 2017 03:17PM

ja...@google.com <ja...@google.com> #77Mar 10, 2017 04:15PM

le...@gmail.com <le...@gmail.com> #78Mar 10, 2017 05:13PM

gh...@gmail.com <gh...@gmail.com> #79Mar 10, 2017 06:06PM

vs...@google.com <vs...@google.com> #80Mar 10, 2017 09:23PM

gh...@gmail.com <gh...@gmail.com> #81Mar 10, 2017 09:29PM

la...@gmail.com <la...@gmail.com> #84Mar 11, 2017 07:30AM

[Deleted User] <[Deleted User]> #85Mar 11, 2017 02:17PM

je...@gmail.com <je...@gmail.com> #86Mar 13, 2017 04:12AM

do...@gmail.com <do...@gmail.com> #87Mar 13, 2017 08:17AM

yy...@gmail.com <yy...@gmail.com> #88Mar 13, 2017 09:15AM