The item inside RecyclerView can't be clicked right after scrolling [66996774]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ki...@gmail.com

created issue #1

Sep 27, 2017 05:06PM

Library used (support-v4, appcompat-v7, ...):support-v4, appcompat-v7, design, cardview-v7, recyclerview-v7, customtabs
Version used: 26.0.2
Theme used: Theme.AppCompat.NoActionBar
Devices/Android versions reproduced on: AVD API 25

I just upgraded to API 26 and support library 26.0.2. But I found that my RecyclerView items is not clickable right after the scrolling. If you wait for a second, it will work. But if you click the item immediately, it won't. Even if the RecyclerView is not scrolling at all(e.g. has scrolled to the top).

When I downgraded to support library 25.4.0 everything goes fine again. The key point is that my RecyclerView is in a CoordinatorLayout and has a SCROLL_FLAG_SCROLL flag on my Toolbar of the AppBarLayout. If I don't use this flag, then this problem will disappear.

I've tried to add focusable="false" to the CoordinatorLayout but still had no luck.
Is there any way to disable this behavior? Because it's really annoying to click twice to trigger the click event.

I think the problem is the scrollState of the RecyclerView. When it's stopped scrolling, it's not changed to SCROLL_STATE_IDLE immediately. Looking into the source code of RecyclerView, I found there's a ViewFlinger controlling the scroll state. When I fling down to scroll to the top, it's not calling setScrollState(SCROLL_STATE_IDLE) immediately. Instead, it wait for a while to trigger this method. The more fast I fling, the more time I need to wait. It just like the RecyclerView is still scrolling in the background. Because the scroller.isFinished() doesn't return true right after the RecyclerView stop scrolling when it touched the top. Maybe it's a bug of the RecyclerView when it's in a CoordinatorLayout.

The attachment is a screen recording of this behavior.

<android.support.design.widget.CoordinatorLayout
android:id="@+id/coordinateLayout"
android:layout_width="match_parent"
android:layout_height="match_parent">

<android.support.design.widget.AppBarLayout
android:id="@+id/fragmentAppBar"
android:layout_width="match_parent"
android:layout_height="wrap_content"
app:elevation="0dp"
android:background="@null">
<include
android:id="@+id/dynamicActionBarHolder"
layout="@layout/dynamic_action_bar"/>
</android.support.design.widget.AppBarLayout>

<android.support.v4.widget.SwipeRefreshLayout
android:id="@+id/pullToRefreshMailRecycler"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:layout_behavior="@string/appbar_scrolling_view_behavior">

<android.support.v7.widget.RecyclerView
android:id="@+id/mailRecyclerView"
android:layout_width="match_parent"
android:layout_height="match_parent"/>

</android.support.v4.widget.SwipeRefreshLayout>

</android.support.design.widget.CoordinatorLayout>

layout/dynamic_action_bar.xml

<FrameLayout xmlns:android="

http://schemas.android.com/apk/res/android"
xmlns:app="

http://schemas.android.com/apk/res-auto"
android:layout_width="match_parent"
android:layout_height="?attr/actionBarSize"
app:layout_scrollFlags="scroll"
android:clickable="true"
android:background="?theme.dynamicActionBarBackground">

<ImageButton
android:id="@+id/dynamicAcbMenuIcon"
android:layout_width="?attr/actionBarSize"
android:layout_height="?attr/actionBarSize"
android:background="@drawable/article_explicit_button_background"
android:src="?theme.menuIcon"/>

<RelativeLayout
android:id="@+id/dynamicAcbTitleHolder"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_marginStart="?attr/actionBarSize"
android:paddingTop="5dp"
android:paddingBottom="5dp"
android:paddingEnd="5dp"
android:layout_gravity="center_vertical">

<TextView
android:id="@+id/dynamicAcbTitle"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:singleLine="true"
android:textSize="@dimen/action_bar_title_portrait_size"
android:textColor="?theme.listItemTitleColor"
android:ellipsize="end"
android:text="ActionBar"/>

<TextView
android:id="@+id/dynamicAcbSubtitle"
android:layout_below="@+id/dynamicAcbTitle"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:singleLine="true"
android:textSize="@dimen/action_bar_subtitle_portrait_size"
android:textColor="?theme.listItemTitleColor"
android:ellipsize="end"
android:text="If you say so"/>

</RelativeLayout>

</FrameLayout>

demo.mov

20 MB

Download

Comments

am...@google.com <am...@google.com> Sep 28, 2017 03:49AM

Assigned to am...@google.com.

am...@google.com <am...@google.com> #2Sep 28, 2017 10:41AM

I have this issue as well.
Same issue:

https://issuetracker.google.com/issues/134627083

ca...@gmail.com <ca...@gmail.com> #3Sep 29, 2017 12:58AM

Josh, can you please look at this? This is affecting a large number of Windows users especially those on Windows versions before 10.

ki...@gmail.com <ki...@gmail.com> #4Sep 30, 2017 07:16AM

Same on my Windows 10 computer.

TestApplication.zip

34 MB

Download

am...@google.com <am...@google.com> #5Oct 3, 2017 09:40AM

Same seen on Windows 10. Rolled back to 28.0.2 and issue is gone. Seems to be specific to 29.0.0

[Deleted User] <[Deleted User]> #6Oct 4, 2017 02:50AM

29.0.1, which rolls back the change that triggered this issue, has been released.

lo...@gmail.com <lo...@gmail.com> #7Oct 4, 2017 02:51AM

I installed 29.0.1 via the SDK Manager. This problem feels fixed to me.

t....@gmail.com <t....@gmail.com> #8Oct 10, 2017 03:58AM

I have update android studio 3.4.2 , build tools version 29.0.1 ,gradle version 5.1.1 and build the project app:mergereDebugResources failed shows message 'Process unexpectedly exit.'
I cant find the solution
The log is
org.gradle.execution.MultipleBuildFailures: Build completed with 1 failures.
at org.gradle.initialization.DefaultGradleLauncher$ExecuteTasks.run(DefaultGradleLauncher.java:386)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:301)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:293)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
at org.gradle.initialization.DefaultGradleLauncher.runTasks(DefaultGradleLauncher.java:247)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:159)
at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:134)
at org.gradle.internal.invocation.GradleBuildController$1.execute(GradleBuildController.java:58)
at org.gradle.internal.invocation.GradleBuildController$1.execute(GradleBuildController.java:55)
at org.gradle.internal.invocation.GradleBuildController$3.create(GradleBuildController.java:82)
at org.gradle.internal.invocation.GradleBuildController$3.create(GradleBuildController.java:75)
at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:183)
at org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks(StopShieldingWorkerLeaseService.java:40)
at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:75)
at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:55)
at org.gradle.tooling.internal.provider.runner.BuildModelActionRunner.run(BuildModelActionRunner.java:54)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.BuildOutcomeReportingBuildActionRunner.run(BuildOutcomeReportingBuildActionRunner.java:58)
at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
at org.gradle.launcher.exec.BuildCompletionNotifyingBuildActionRunner.run(BuildCompletionNotifyingBuildActionRunner.java:39)
at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:49)
at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.call(RunAsBuildOperationBuildActionRunner.java:44)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:315)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:305)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:101)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:44)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:49)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:46)
at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:78)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:46)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:31)
at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:42)
at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:28)
at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:78)
at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:52)
at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:59)
at org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:36)
at org.gradle.tooling.internal.provider.SessionScopeBuildActionExecuter.execute(SessionScopeBuildActionExecuter.java:68)
at org.gradle.tooling.internal.provider.SessionScopeBuildActionExecuter.execute(SessionScopeBuildActionExecuter.java:38)
at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:37)
at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:26)
at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43)
at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29)
at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:60)
at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:32)
at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:55)
at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:41)
at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:48)
at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:32)
at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
at org.gradle.util.Swapper.swap(Swapper.java:38)
at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:81)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:mergeDebugResources'.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:95)
at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:91)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:57)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:119)
at org.gradle.api.internal.tasks.execution.ResolvePreviousStateExecuter.execute(ResolvePreviousStateExecuter.java:43)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:93)
at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:45)
at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:94)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:56)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:55)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:67)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:49)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:315)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:305)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:101)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:49)
at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:43)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:355)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:343)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:336)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:322)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$1.execute(DefaultPlanExecutor.java:134)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker$1.execute(DefaultPlanExecutor.java:129)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:202)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:193)
at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:129)
... 6 more
Caused by: com.android.ide.common.workers.WorkerExecutorException: 8 exceptions were raised by workers:
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #0: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #2: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #1: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #3: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #4: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #5: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #6: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #7: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.

at com.android.ide.common.workers.ExecutorServiceAdapter.await(ExecutorServiceAdapter.kt:62)
at com.android.ide.common.workers.ExecutorServiceAdapter.close(ExecutorServiceAdapter.kt:69)
at com.android.build.gradle.internal.aapt.WorkerExecutorResourceCompilationService.close(WorkerExecutorResourceCompilationService.kt:67)
at com.android.build.gradle.tasks.MergeResources.doFullTaskAction(MergeResources.java:268)
at com.android.build.gradle.internal.tasks.IncrementalTask.taskAction(IncrementalTask.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:47)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:41)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:28)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$2.run(ExecuteActionsTaskExecuter.java:284)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:301)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:293)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:273)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:258)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$200(ExecuteActionsTaskExecuter.java:67)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:145)
at org.gradle.internal.execution.impl.steps.ExecuteStep.execute(ExecuteStep.java:49)
at org.gradle.internal.execution.impl.steps.CancelExecutionStep.execute(CancelExecutionStep.java:34)
at org.gradle.internal.execution.impl.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:69)
at org.gradle.internal.execution.impl.steps.TimeoutStep.execute(TimeoutStep.java:49)
at org.gradle.internal.execution.impl.steps.CatchExceptionStep.execute(CatchExceptionStep.java:33)
at org.gradle.internal.execution.impl.steps.CreateOutputsStep.execute(CreateOutputsStep.java:50)
at org.gradle.internal.execution.impl.steps.SnapshotOutputStep.execute(SnapshotOutputStep.java:43)
at org.gradle.internal.execution.impl.steps.SnapshotOutputStep.execute(SnapshotOutputStep.java:29)
at org.gradle.internal.execution.impl.steps.CacheStep.executeWithoutCache(CacheStep.java:134)
at org.gradle.internal.execution.impl.steps.CacheStep.lambda$execute$3(CacheStep.java:83)
at java.util.Optional.orElseGet(Optional.java:267)
at org.gradle.internal.execution.impl.steps.CacheStep.execute(CacheStep.java:82)
at org.gradle.internal.execution.impl.steps.CacheStep.execute(CacheStep.java:36)
at org.gradle.internal.execution.impl.steps.PrepareCachingStep.execute(PrepareCachingStep.java:33)
at org.gradle.internal.execution.impl.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:38)
at org.gradle.internal.execution.impl.steps.StoreSnapshotsStep.execute(StoreSnapshotsStep.java:23)
at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:96)
at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:89)
at java.util.Optional.map(Optional.java:215)
at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:52)
at org.gradle.internal.execution.impl.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:36)
at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:34)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:91)
... 35 more
Caused by: java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #0: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1006)
at com.android.ide.common.workers.ExecutorServiceAdapter.await(ExecutorServiceAdapter.kt:56)
... 80 more
Caused by: com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.2-5326820-windows Daemon #0: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
at com.android.builder.internal.aapt.v2.Aapt2Daemon.handleError(Aapt2Daemon.kt:148)
at com.android.builder.internal.aapt.v2.Aapt2Daemon.checkStarted(Aapt2Daemon.kt:57)
at com.android.builder.internal.aapt.v2.Aapt2Daemon.compile(Aapt2Daemon.kt:79)
at com.android.builder.internal.aapt.v2.Aapt2DaemonManager$LeasedAaptDaemon.compile(Aapt2DaemonManager.kt:170)
at com.android.build.gradle.internal.res.Aapt2CompileWithBlameRunnable$run$1.invoke(Aapt2CompileWithBlameRunnable.kt:37)
at com.android.build.gradle.internal.res.Aapt2CompileWithBlameRunnable$run$1.invoke(Aapt2CompileWithBlameRunnable.kt:28)
at com.android.build.gradle.internal.res.namespaced.Aapt2DaemonManagerService.useAaptDaemon(Aapt2DaemonManagerService.kt:71)
at com.android.build.gradle.internal.res.namespaced.Aapt2DaemonManagerService.useAaptDaemon$default(Aapt2DaemonManagerService.kt:69)
at com.android.build.gradle.internal.res.Aapt2CompileWithBlameRunnable.run(Aapt2CompileWithBlameRunnable.kt:34)
at com.android.ide.common.workers.ExecutorServiceAdapter$submit$submission$1.run(ExecutorServiceAdapter.kt:40)
at java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(ForkJoinTask.java:1386)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Caused by: com.android.builder.internal.aapt.v2.Aapt2InternalException: Failed to start AAPT2 process.
at com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.stopQuietly(Aapt2DaemonImpl.kt:127)
at com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.startProcess(Aapt2DaemonImpl.kt:114)
at com.android.builder.internal.aapt.v2.Aapt2Daemon.checkStarted(Aapt2Daemon.kt:53)
... 13 more
Caused by: java.io.IOException: Process unexpectedly exit.
at com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.startProcess(Aapt2DaemonImpl.kt:115)
... 14 more

[Deleted User] <[Deleted User]> #9Oct 21, 2017 02:18PM

That's not related to adb, please file a separate bug.

ad...@gmail.com <ad...@gmail.com> #10Oct 30, 2017 12:35PM

Hello,

I close a virtual device and after a while my notebook's cpu goes to 100% then my windows 10 system crash.

Android Studio 3.4.2
Build #AI-183.6156.11.34.5692245, built on June 27, 2019
JRE: 1.8.0_152-release-1343-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

Nome do Log: System
Fonte: Microsoft-Windows-Kernel-Power
Data: 15/07/2019 17:10:22
Identificação do Evento:41
Categoria da Tarefa:(63)
Nível: Nível Crítico
Palavras-chave:(70368744177664),(2)
Usuário: SISTEMA
Computador: LAPTOP-56J1L2VC
Descrição:
O sistema foi reiniciado sem um desligamento correto primeiro. Esse erro pode ser causado quando o sistema para de responder, trava ou fica sem energia inesperadamente.
XML de Evento:
<Event xmlns="

http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2019-07-15T20:10:22.180468100Z" />
<EventRecordID>7466</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>LAPTOP-56J1L2VC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">159</Data>
<Data Name="BugcheckParameter1">0x3</Data>
<Data Name="BugcheckParameter2">0xffff8c837a293060</Data>
<Data Name="BugcheckParameter3">0xfffff8051d7f3c00</Data>
<Data Name="BugcheckParameter4">0xffff8c83808e7010</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">41</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">1</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

[Deleted User] <[Deleted User]> #11Nov 2, 2017 07:35AM

SDK Platform Tools release notes:

https://developer.android.com/studio/releases/platform-tools

Revisions
29.0.1 (June 2019)
adb
Hotfix for Windows crashes (

https://issuetracker.google.com/134613180)

My Windows 10 system still crashes.

ch...@google.com <ch...@google.com> #12Nov 6, 2017 11:41AM

i seem to have a different issue. i downloaded the tools and unpack it on my desktop. i can run sqlite3.exe, but i can't run any of the other .exe files. i found an app that needs a root permission to change my screen in one click to grayscale. and i need the adb.exe file to put a command into my phone.

when i click it, it briefly shows a window and then it disapears again.

i've tried a restart, compability to windows 8,7 and xp and the windows troubleshooter. i run windows 10 on a asus rog

https://www.asus.com/nl/ROG-Republic-Of-Gamers/ROG-GL502VS/specifications/

did i do something wrong?

[Deleted User] <[Deleted User]> #13Nov 6, 2017 12:43PM

okay don't worry guys. you shouldn't be clicking the adb.exe directly. you should open a comand prompt. then you can use this via the comand prompt or something. you'll find a better explanation here

https://www.xda-developers.com/install-adb-windows-macos-linux/

i can now turn my phone to grayscale with a simple click :)

ja...@gmail.com <ja...@gmail.com> #14Nov 7, 2017 11:21PM

i have the same problem as the other , what is the solution ?

my mail is: 3loumwm3arif@gmail.com

ch...@google.com <ch...@google.com> #15Nov 8, 2017 09:46AM

Nothing really fix the problem. I can't run the adb at all. "unable to connect to adb. check the event log"
What should we do now? go back to older versions of Android studio?

[Deleted User] <[Deleted User]> #16Nov 9, 2017 07:48AM

I guess Im in wrong place it's 2 am now that;s why :)

ch...@google.com <ch...@google.com> #17Nov 9, 2017 10:00AM

Delete

am...@google.com <am...@google.com> #18Nov 10, 2017 11:10AM

Marked as fixed.

Hmmm

ar...@google.com <ar...@google.com> #19Nov 13, 2017 08:59AM

az...@gmail.com <az...@gmail.com> #20Nov 16, 2017 10:25AM

https://drive.google.com/file/d/0BznXwGnKYif_c3RhcnRlcl9maWxl/view?usp=drive_web (Getting started)

dg...@gmail.com <dg...@gmail.com> #21Nov 16, 2017 06:27PM

#20

https://drive.google.com/file/d/0BznXwGnKYif_c3RhcnRlcl9maWxl/view?usp=drive_web

[Deleted User] <[Deleted User]> #22Nov 17, 2017 07:54AM

jo...@gmail.com <jo...@gmail.com> #23Nov 19, 2017 03:09PM

https://drive.google.com/file/d/1g37Tb8uNajo8ARz-t0vnMhDZKZxLfLhn/view?usp=drive_web (Printed from Android.pdf)

dr...@gmail.com <dr...@gmail.com> #24Nov 23, 2017 08:58AM

fa...@gmail.com <fa...@gmail.com> #25Nov 23, 2017 09:05AM

Thanks

ps...@gmail.com <ps...@gmail.com> #26Nov 23, 2017 09:12AM

testing

dr...@gmail.com <dr...@gmail.com> #27Nov 23, 2017 03:22PM

-hotlist Google domain
+hotlist 2367385

dr...@gmail.com <dr...@gmail.com> #28Nov 28, 2017 08:45AM

---------- ထပ်ဆင့်ပေးပို့သည့်မက်ဆေ့ချ် ----------
From: <buganizer-system@google.com>
Date: 24 ဧပြီ 2020 6:50 AM
Subject: Re:

Issue 134613180

: Updating to platform tools 29.0.0 results in
continuous stream of adb.exe crash dialogs, at least on Windows 8.1
To: <b-system+591006804@google.com>
မိတ္တူ: <kok129873@gmail.com>

Replying to this email means your email address will be shared with the
team that works on this product.

https://issuetracker.google.com/issues/134613180

*Changed*

*da...@gmail.com <da...@gmail.com> added

comment #27

https://issuetracker.google.com/issues/134613180#comment27>:*

-hotlist Google domain +hotlist 2367385

_______________________________

*Reference Info: 134613180 Updating to platform tools 29.0.0 results in
continuous stream of adb.exe crash dialogs, at least on Windows 8.1*
component: Android Public Tracker > App Development > Android Studio >
Emulator <

https://issuetracker.google.com/components/192727>
status: Fixed
reporter: le...@gmail.com
assignee: jm...@google.com
cc: bo...@google.com, jm...@google.com, le...@gmail.com
type: Bug
priority: P1
severity: S2
duplicate issue: 134627083
<

https://issuetracker.google.com/issues/134627083>
hotlist: Reviewed (L1) <

https://issuetracker.google.com/hotlists/712415>
retention: Component default

Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google
IssueTracker

issue 134613180

https://issuetracker.google.com/issues/134613180> where you have the role:
starred.
Unsubscribe from this issue.
<

https://issuetracker.google.com/issues/134613180?unsubscribe=true>

al...@google.com <al...@google.com> #29Nov 28, 2017 06:52PM

Status: Assigned (reopened)

29 ေဖ 2020 11:12 PM တွင် <buganizer-system@google.com> ရေးခဲ့သည်မှာ။ ။

- Show quoted text -

am...@google.com <am...@google.com> #30Nov 29, 2017 07:05AM

Marked as fixed.

Mmmank

ps...@gmail.com <ps...@gmail.com> #31Dec 3, 2017 10:45AM

TITsovneMakara@gmail.com

de...@gmail.com <de...@gmail.com> #32Dec 6, 2017 12:40PM

Feedback

de...@gmail.com <de...@gmail.com> #33Dec 12, 2017 04:06AM

aaireill111@gmail.com

pr...@gmail.com <pr...@gmail.com> #34Dec 14, 2017 12:07PM

انتهاك خصوصية

[Deleted User] <[Deleted User]> #35Dec 15, 2017 09:09AM

My privacy was violated by an unidentified person, opening several web pages with all my personal data, and I have a forged and incorrect user agreement for my account. I ask you to block the unknown person and help me update my data.

Please help me to modify the privacy of my account to private privacy and not to participate categorically and the presence of security for privacy and not tampering with it.

ay...@gmail.com <ay...@gmail.com> #36Dec 24, 2017 03:26PM

On Wed, Nov 18, 2020, 6:50 PM <buganizer-system@google.com> wrote:

- Show quoted text -

9g...@gmail.com <9g...@gmail.com> #37Dec 29, 2017 07:22AM

What is this and why am I in this can someone please explain

On Tue, Dec 15, 2020, 2:06 AM <buganizer-system@google.com> wrote:

- Show quoted text -

[Deleted User] <[Deleted User]> #38Jan 2, 2018 06:29AM

https://console.aws.amazon.com/support/home?#/case/?caseId=7795210011&displayId=7795210011&language=en

za...@gmail.com <za...@gmail.com> #39Jan 2, 2018 06:32AM

حلم 95458 من مصر 🇪🇬 201551145918كرم محمد عبد العزيز عبد العال حلم حلم حلم حلم حلم حلم حلم 2021

sh...@gmail.com <sh...@gmail.com> #40Jan 11, 2018 08:09AM

حلم حلم حلم حلم حلم حلم حلم 95458 مصر 🇪🇬 محافظة الاسكندرية كرم محمد عبد العزيز عبد العال 201551145918 حلم حلم حلم حلم يارب شيك يارب mbc 2021

ja...@gmail.com <ja...@gmail.com> #41Jan 14, 2018 08:28PM

I installed 29.0.1 via the SDK Manager. This problem feels fixed to me.

de...@gmail.com <de...@gmail.com> #42Jan 14, 2018 08:38PM

https://drive.google.com/file/d/0B8TBbCbAQEhJVDJYWmtpMm1GSkU/view?usp=drive_web (225)

pe...@gmail.com <pe...@gmail.com> #43Jan 17, 2018 01:41PM

hi my name abdulrahman afghan
help me japan tool

pe...@gmail.com <pe...@gmail.com> #44Jan 17, 2018 01:57PM

On Sat, Sep 11, 2021, 8:11 AM <buganizer-system@google.com> wrote:

- Show quoted text -

hu...@gmail.com <hu...@gmail.com> #45Feb 1, 2018 02:46AM

good bay!

1381662341mohamadsalmanpor

در تاریخ شنبه ۱۱ سپتامبر ۲۰۲۱،‏ ۱۶:۴۱ <buganizer-system@google.com> نوشت:

- Show quoted text -

[Deleted User] <[Deleted User]> #46Feb 7, 2018 01:22AM

https://drive.google.com/file/d/1IdB9_C-qvVKHshc-xekJws6oo-FScA15/view?usp=drive_web (Backup-codes-miwavaso.txt)

an...@gmail.com <an...@gmail.com> #47Feb 7, 2018 03:09AM

1381662341:issu

1381662341mohamadsalmanpor

در تاریخ شنبه ۲ اکتبر ۲۰۲۱،‏ ۲:۲۰ بعدازظهر <buganizer-system@google.com>
نوشت:

- Show quoted text -

hi...@gmail.com <hi...@gmail.com> #48Feb 7, 2018 03:21AM

Hjh

[Deleted User] <[Deleted User]> #49Feb 13, 2018 11:35AM

My device esim update 13 on drive

ha...@gmail.com <ha...@gmail.com> #50Feb 15, 2018 05:10PM

ri...@gmail.com <ri...@gmail.com> #51Feb 17, 2018 06:16AM

El sáb., 11 de septiembre de 2021 8:11 p. m., <buganizer-system@google.com>
escribió:

- Show quoted text -

fa...@gmail.com <fa...@gmail.com> #52Feb 20, 2018 12:18PM

Are you ever gonna fix this? 5 months and still no fix

de...@gmail.com <de...@gmail.com> #53Feb 20, 2018 12:31PM

+1k!

au...@google.com <au...@google.com> #54Feb 22, 2018 06:18PM

Status: Assigned (reopened)

shepshapard@ can you take a look at this?

sh...@google.com <sh...@google.com> #55Feb 22, 2018 07:12PM

Yes, I've already looked into this and believe I've found the issue.

The issue is that after a fling event, the nested scrolling api has no way of informing the RecyclerView that a fling animation has reached the end of the scroll distance, and thus sometimes, the scroll animation is continuing in the background such that when the first tap occurs, it is interpreted as an interruption to the fling, which puts the RV back into its scrolling state as if the user started scrolling, and thus, the touch events don't propagate down to the child to cause a click to occur.

Some larger changes are needed to fix this (and at least one other) issue, and I'm in the midst of that work.

Sorry for the inconvenience.

za...@gmail.com <za...@gmail.com> #56Feb 22, 2018 07:51PM

The issue is that the material components team has seemingly abandoned the design support library and won't release new versions

dr...@gmail.com <dr...@gmail.com> #57Feb 28, 2018 03:23AM

Have seen Support Library update to version 27.1.0.

May I ask in this version, fix this issue?

sh...@google.com <sh...@google.com> #58Feb 28, 2018 05:55PM

Unfortunately, this issue won't be fixed in the 27.1 release. I am actively working on it and will notify this thread when it is submitted (which means it will be in the following release). Sorry for the inconvenience!

sp...@gmail.com <sp...@gmail.com> #59Mar 5, 2018 02:35PM

The same problem while I use RecyclerView in CoordinatorLayout.

sh...@google.com <sh...@google.com> #60Mar 5, 2018 04:43PM

Yes. Sorry. The issue is actually caused by a lack of functionality in nested scrolling so you will see this issue when RV is nested in any other NestedScrollingParent.

When RecyclerView is flung, and it hits the bounds of it's scrollable distance and has a NestedScrollingParent, it continues to animate the fling so that the NestedScrollingParent might receive the events and scroll. RV has no way of knowing if any NestedScrollingParents have hit their bounds, and thus it continues the fling even if nothing is moving.

On top of that, when RV is flinging and is touched, it stops it's fling and prevents the touch event from causing a click, so that a touch meant to stop a fling doesn't cause a click.

Put those two things together and you get the perceived behavior that when an RV is flung, and stops, the next touch event doesn't click.

I'm pursuing a but can't make any promises as to when it will be available. Sorry for the inconvenience.

ha...@gmail.com <ha...@gmail.com> #61Mar 23, 2018 03:47PM

How come that the problem does not occur when I select older support library version? like the 25.3.1

je...@gmail.com <je...@gmail.com> #62Apr 12, 2018 07:54AM

not fixed with version 27.1.0

https://gist.github.com/chrisbanes/8391b5adb9ee42180893300850ed02f2 works

pr...@gmail.com <pr...@gmail.com> #63Apr 23, 2018 07:52PM

Not fix as in the newer versions. Can we bump up the priority of the issue because from the user's point of view clicking twice to is a bad experience?

su...@gmail.com <su...@gmail.com> #64May 7, 2018 06:10PM

I have a similar issue but with the BottomNavigationView, is the fix proposed applicable to Views?

sh...@google.com <sh...@google.com> #65May 7, 2018 07:27PM

I'm not absolutely sure that the proposed fix will also fix the issue you are having with BottomNavigationView, but it seems very likely that the root issue is still the same. I'm still trying to carve out time to address the issue but some work is in flight.

ny...@gmail.com <ny...@gmail.com> #66Jun 5, 2018 05:17AM

27.0.2 do not fix the issue.

fa...@gmail.com <fa...@gmail.com> #67Jun 5, 2018 10:33AM

this issue is still there in 27.1.1

le...@gmail.com <le...@gmail.com> #68Jun 12, 2018 05:18PM

Also having this issue with 27.1.1

pi...@gmail.com <pi...@gmail.com> #69Jun 17, 2018 08:35AM

The same

yi...@gmail.com <yi...@gmail.com> #70Jun 21, 2018 07:31AM

same issue

de...@gmail.com <de...@gmail.com> #71Jun 21, 2018 07:51AM

How is it possible that this bug is STILL not fixed??? It affect so many apps/developers/users. Crazy

t....@gmail.com <t....@gmail.com> #72Jun 21, 2018 10:09AM

How is it possible that there are #71 'me too' comments? If you have nothing constructive to contribute, shut the fuck up and stop blowing up everyone's emails with your god damn complaints.

cn...@gmail.com <cn...@gmail.com> #73Jul 5, 2018 07:31PM

Please fix it... It has been 6 months.

za...@gmail.com <za...@gmail.com> #74Jul 5, 2018 07:38PM

This is fixed in material components, which is the successor to the design support library and currently released at 'com.google.android.material:material:1.0.0-beta01' and has been available for two months since Google I/O. Migrate to that if you want the fix:

https://material.io/develop/android/

da...@gmail.com <da...@gmail.com> #75Jul 6, 2018 11:59AM

Also having this issue with 27.1.1

[Deleted User] <[Deleted User]> #76Jul 24, 2018 02:04PM

Using the version 27.1.1 but the issue is still there. Please fix it. Wait time is over.

ro...@gmail.com <ro...@gmail.com> #77Aug 18, 2018 02:25AM

Just tried 28.0.0-rc01 and the problem is still there.

an...@googlemail.com <an...@googlemail.com> #78Aug 27, 2018 09:15AM

#72 if there is no reaction from any google developer to this ridiculous situation.

sh...@google.com <sh...@google.com> #79Aug 27, 2018 03:59PM

Sorry I have been unresponsive.

I am actively solving this issue. In fact, the CL that makes the necessary changes in RecyclerView has been submitted to aosp (as AndroidX is now developed there):

https://android-review.googlesource.com/c/platform/frameworks/support/+/723649

The fix is coming by way of an update to nested scrolling and thus need to be implemented across multiple classes. For example, for the issue to be fixed when a RecyclerView is in a CoordinatorLayout with the AppBarLayout.Behavior, implementation has to be done in each of those classes.

Unfortunately the rollout of these changes is also going to take some time, but do know that we are taking as seriously as we can.

fr...@gmail.com <fr...@gmail.com> #80Aug 31, 2018 11:19AM

Please give me the solution

sh...@google.com <sh...@google.com> #81Sep 4, 2018 05:43PM

Unfortunately, the solution is not something you can easily implement on your own and instead really must be implemented in the libraries themselves. But like I said the solution is known and the work is actually nearly complete. Unfortunately, even when it is complete, we will have to wait for it to actually be released. Sorry for the delay!

zz...@gmail.com <zz...@gmail.com> #82Sep 7, 2018 02:53AM

That's my solution

https://gist.github.com/AlexSmille/1168720fdb99f76d0f3e96ff4246c9ad 。

sh...@gmail.com <sh...@gmail.com> #83Sep 23, 2018 09:03AM

Not working for me on V27.1.1
I've tried both java and xml ways but in vain.
Checked on emulator running on 5.0 and physical device running on 7.1.1
Any ideas ?

sh...@gmail.com <sh...@gmail.com> #84Sep 27, 2018 06:23PM

It is weird that this bug is a year old and has not been addressed properly by Google yet.

ss...@gmail.com <ss...@gmail.com> #85Sep 28, 2018 07:51PM

Still an issue in 28.0.0. Are there any reliable workarounds for this issue?

lo...@gmail.com <lo...@gmail.com> #86Sep 28, 2018 08:08PM

comment#85

, yes there are. Here is mine:

https://github.com/LouisCAD/Splitties/blob/3a2e75d7342028bff21008cdf77cf68ff1efae00/viewdsl-design/src/main/java/splitties/viewdsl/design/fixedimpls/FixedAppBarLayoutBehavior.kt

am...@gmail.com <am...@gmail.com> #87Oct 9, 2018 02:26AM

I'm migrated to AndroidX and seem that this issue are fixed

am...@google.com <am...@google.com> Oct 9, 2018 06:05AM

Reassigned to ku...@google.com.

pa...@gmail.com <pa...@gmail.com> #88Oct 13, 2018 04:41PM

I do not know why I am not getting any callback on time. I am hiding some view on scroll-start of recycler view. But the problem is I am not getting it on time and my implementation causes few bugs.

Dear Google developers, can you please take it on priority?

we...@gmail.com <we...@gmail.com> #89Nov 16, 2018 09:46AM

Still seeing this issue in androidx.core 1.1.0-alpha01 with BottomNavigationView.

kp...@gmail.com <kp...@gmail.com> #90Jan 10, 2019 08:27AM

This issue was fixed for me when started using recyclerview:1.1.0-alpha01 with coordinatorlayout:1.1.0-alpha01.
I think it is related with NestedScrollingChild3 and NestedScrollingParent3 and since 1.1.0-alpha01 RecyclerView and CoordinatorLayout implements those.

sh...@google.com <sh...@google.com> #91Jan 10, 2019 06:37PM

I'm glad to hear it given that NestedScrollingChild3 and NestedScrollingParent3 were created and are implemented to solve this very issue! There is one thing that isn't implemented yet due to some complexity: updating AppBarLayout.Behavior... so even if you use recyclerview:1.1.0-alpha01 with coordinatorlayout:1.1.0-alpha01 right now, if you also use AppBarLayout.Behavior to collapse the AppBar, then the underlying issue will return and this bug will present itself.

sh...@google.com <sh...@google.com> #92Jan 18, 2019 08:32PM

Marked as fixed.

Via the new Nested Scrolling 3 API, and it's implementation across various libraries:

androidx.core 1.1.0-alpha01
androidx.appcompat 1.1.0-alpha01
androidx.coordinatorlayout 1.1.0-alpha01
androidx.recyclerview 1.1.0-alpha01
androidx.swiperefreshlayout 1.1.0-alpha01
(and an upcoming release of the android material design library)

This issue should be fixed!

I'm closing it, but do let me know if it seems to still be happening!

pa...@outlook.com <pa...@outlook.com> #93Mar 14, 2019 08:17PM

It is still happening under this specific scenario:

This is a BottomSheet with a NestedScrollView, it does not contain any RecyclerView:

<?xml version="1.0" encoding="utf-8"?>
<androidx.coordinatorlayout.widget.CoordinatorLayout
xmlns:android="

http://schemas.android.com/apk/res/android"
xmlns:app="

http://schemas.android.com/apk/res-auto"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:clipChildren="false">

<com.google.android.material.appbar.AppBarLayout
android:layout_width="match_parent"
android:layout_height="wrap_content">



</com.google.android.material.appbar.AppBarLayout>

<androidx.core.widget.NestedScrollView
android:layout_width="match_parent"
android:layout_height="match_parent"
android:background="@color/white"
app:layout_behavior="@string/appbar_scrolling_view_behavior">

<LinearLayout
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:orientation="vertical"
android:paddingBottom="8dp"
android:paddingTop="8dp">



</LinearLayout>

</androidx.core.widget.NestedScrollView>

</androidx.coordinatorlayout.widget.CoordinatorLayout>

In this scenario (with or without a Toolbar view in the AppBarLayout parent) whenever you scroll the NestedScrollView to the top or to the bottom and try to tap on any items inside the LinearLayout the first tap will always fail to initiate the expected action, forcing you to do a second tap since after the first one the taps start working. This happens whenever you scroll to the top or bottom of the NestedScrollView every single time, even after you tap for a second or n times.

I am using the library versions or most up to date (a couple were already updated since then) the Assignee listed in his last reply.

sh...@google.com <sh...@google.com> #94Mar 14, 2019 08:51PM

We actually just noticed this issue ourselves and it is actually getting addressed right now in the BottomSheet code. Sorry about that. I have also communicated with the Android Material Design team to make sure other code doesn't need to be updated as well.

There isn't a public bug that I'm aware of that is tracking that precise work, but know that your specific issue will be fixed in an upcoming release of the Android Material Design library.

pa...@outlook.com <pa...@outlook.com> #95Mar 15, 2019 01:51PM

I appreciate the update. Please let us know when it is fixed in this thread since there isn't a dedicated thread for that specific bug.

me...@google.com <me...@google.com> #96Mar 15, 2019 09:44PM

Material Design Library is actively updating this for BSB, you may track the progress here:

b/128698671

yq...@gmail.com <yq...@gmail.com> #97Mar 20, 2019 04:22AM

I'm having the same problem with a RecyclerView in MotionLayout, so I created issue for it.

https://issuetracker.google.com/issues/128914828

pv...@gmail.com <pv...@gmail.com> #98Nov 6, 2019 11:03AM

I'm using recycler view in bottom sheet and this issue is not fixed.
recyclerview-v7:28.0.0

vz...@gmail.com <vz...@gmail.com> #99Nov 19, 2019 10:24AM

we are using 28.0.0, the problem is still there.

sh...@google.com <sh...@google.com> #100Nov 19, 2019 10:19PM

28.0 was the last release of RecyclerView in the support library packages and should be considered deprecated:

https://developer.android.com/reference/android/support/v7/widget/RecyclerView

The AndroidX version of RecyclerView picks up where that version left off and is currently supported:

https://developer.android.com/jetpack/androidx/releases/recyclerview

sh...@google.com <sh...@google.com> #101Nov 19, 2019 10:20PM

See

comment #92

sa...@gmail.com <sa...@gmail.com> #102Dec 5, 2019 12:03AM

For those having problems with bottom sheet, you need to bump your material version to at least 1.1.0-alpha05

[Deleted User] <[Deleted User]> #103Jan 24, 2020 06:30AM

I am getting same issue with androidx.recyclerview:recyclerview:1.1.0.

[Deleted User] <[Deleted User]> #104May 4, 2020 10:35AM

Bump, same issue on androix.recyclerview:recyclerview:1.1.0.

sh...@google.com <sh...@google.com> #105May 4, 2020 04:09PM

I will need a minimal repro case for me to be able to look into this any further. Thanks.

te...@gmail.com <te...@gmail.com> #106May 4, 2020 04:15PM

One was given to you in the first post almost 2 and a half years ago. *facepalm*. I wonder why us developers even bother logging bugs with Google anymore...

sh...@google.com <sh...@google.com> #107May 4, 2020 06:37PM

What I meant was that I believe this bug to be fixed given all of the changes that have been done to fix it. In making the changes, I looked for a holistic solution and thus think it was indeed holistic, but if some still find that it does not work, it would be very helpful for me to see a demonstration.

ma...@gmail.com <ma...@gmail.com> #108May 11, 2020 03:52AM

Also reproed while using MotionLayout :(

ma...@gmail.com <ma...@gmail.com> #109May 11, 2020 03:53AM

Also reproed while using MotionLayout :(

but it's working fine if I double tap it quickly

sh...@google.com <sh...@google.com> #110May 11, 2020 04:22PM

I would need more information about an issue with MotionLayout. Can you please file a separate bug with details including a minimal repro case?

bo...@gmail.com <bo...@gmail.com> #111Nov 6, 2020 09:21AM

Updated my AndroidX dependencies and fixed the issue with appbarlayout/bottomnav/recyclerview. Did not try out MotionLayout

Issue 66996774

Description

Issue summary

Comments

am...@google.com <am...@google.com> Sep 28, 2017 03:49AM

am...@google.com <am...@google.com> #2Sep 28, 2017 10:41AM

ca...@gmail.com <ca...@gmail.com> #3Sep 29, 2017 12:58AM

ki...@gmail.com <ki...@gmail.com> #4Sep 30, 2017 07:16AM

am...@google.com <am...@google.com> #5Oct 3, 2017 09:40AM

[Deleted User] <[Deleted User]> #6Oct 4, 2017 02:50AM

lo...@gmail.com <lo...@gmail.com> #7Oct 4, 2017 02:51AM

t....@gmail.com <t....@gmail.com> #8Oct 10, 2017 03:58AM

[Deleted User] <[Deleted User]> #9Oct 21, 2017 02:18PM

ad...@gmail.com <ad...@gmail.com> #10Oct 30, 2017 12:35PM

[Deleted User] <[Deleted User]> #11Nov 2, 2017 07:35AM

ch...@google.com <ch...@google.com> #12Nov 6, 2017 11:41AM

[Deleted User] <[Deleted User]> #13Nov 6, 2017 12:43PM

ja...@gmail.com <ja...@gmail.com> #14Nov 7, 2017 11:21PM

ch...@google.com <ch...@google.com> #15Nov 8, 2017 09:46AM

[Deleted User] <[Deleted User]> #16Nov 9, 2017 07:48AM

ch...@google.com <ch...@google.com> #17Nov 9, 2017 10:00AM

am...@google.com <am...@google.com> #18Nov 10, 2017 11:10AM

ar...@google.com <ar...@google.com> #19Nov 13, 2017 08:59AM

az...@gmail.com <az...@gmail.com> #20Nov 16, 2017 10:25AM

dg...@gmail.com <dg...@gmail.com> #21Nov 16, 2017 06:27PM

[Deleted User] <[Deleted User]> #22Nov 17, 2017 07:54AM

jo...@gmail.com <jo...@gmail.com> #23Nov 19, 2017 03:09PM

dr...@gmail.com <dr...@gmail.com> #24Nov 23, 2017 08:58AM

fa...@gmail.com <fa...@gmail.com> #25Nov 23, 2017 09:05AM

ps...@gmail.com <ps...@gmail.com> #26Nov 23, 2017 09:12AM

dr...@gmail.com <dr...@gmail.com> #27Nov 23, 2017 03:22PM

dr...@gmail.com <dr...@gmail.com> #28Nov 28, 2017 08:45AM

al...@google.com <al...@google.com> #29Nov 28, 2017 06:52PM

am...@google.com <am...@google.com> #30Nov 29, 2017 07:05AM

ps...@gmail.com <ps...@gmail.com> #31Dec 3, 2017 10:45AM

de...@gmail.com <de...@gmail.com> #32Dec 6, 2017 12:40PM

de...@gmail.com <de...@gmail.com> #33Dec 12, 2017 04:06AM

pr...@gmail.com <pr...@gmail.com> #34Dec 14, 2017 12:07PM

[Deleted User] <[Deleted User]> #35Dec 15, 2017 09:09AM

ay...@gmail.com <ay...@gmail.com> #36Dec 24, 2017 03:26PM

9g...@gmail.com <9g...@gmail.com> #37Dec 29, 2017 07:22AM

[Deleted User] <[Deleted User]> #38Jan 2, 2018 06:29AM

za...@gmail.com <za...@gmail.com> #39Jan 2, 2018 06:32AM

sh...@gmail.com <sh...@gmail.com> #40Jan 11, 2018 08:09AM

ja...@gmail.com <ja...@gmail.com> #41Jan 14, 2018 08:28PM

de...@gmail.com <de...@gmail.com> #42Jan 14, 2018 08:38PM

pe...@gmail.com <pe...@gmail.com> #43Jan 17, 2018 01:41PM

pe...@gmail.com <pe...@gmail.com> #44Jan 17, 2018 01:57PM

hu...@gmail.com <hu...@gmail.com> #45Feb 1, 2018 02:46AM

[Deleted User] <[Deleted User]> #46Feb 7, 2018 01:22AM

an...@gmail.com <an...@gmail.com> #47Feb 7, 2018 03:09AM

hi...@gmail.com <hi...@gmail.com> #48Feb 7, 2018 03:21AM

[Deleted User] <[Deleted User]> #49Feb 13, 2018 11:35AM

ha...@gmail.com <ha...@gmail.com> #50Feb 15, 2018 05:10PM

ri...@gmail.com <ri...@gmail.com> #51Feb 17, 2018 06:16AM

fa...@gmail.com <fa...@gmail.com> #52Feb 20, 2018 12:18PM

de...@gmail.com <de...@gmail.com> #53Feb 20, 2018 12:31PM

au...@google.com <au...@google.com> #54Feb 22, 2018 06:18PM

sh...@google.com <sh...@google.com> #55Feb 22, 2018 07:12PM

za...@gmail.com <za...@gmail.com> #56Feb 22, 2018 07:51PM

dr...@gmail.com <dr...@gmail.com> #57Feb 28, 2018 03:23AM

sh...@google.com <sh...@google.com> #58Feb 28, 2018 05:55PM

sp...@gmail.com <sp...@gmail.com> #59Mar 5, 2018 02:35PM

sh...@google.com <sh...@google.com> #60Mar 5, 2018 04:43PM

ha...@gmail.com <ha...@gmail.com> #61Mar 23, 2018 03:47PM

je...@gmail.com <je...@gmail.com> #62Apr 12, 2018 07:54AM

pr...@gmail.com <pr...@gmail.com> #63Apr 23, 2018 07:52PM

su...@gmail.com <su...@gmail.com> #64May 7, 2018 06:10PM

sh...@google.com <sh...@google.com> #65May 7, 2018 07:27PM

ny...@gmail.com <ny...@gmail.com> #66Jun 5, 2018 05:17AM

fa...@gmail.com <fa...@gmail.com> #67Jun 5, 2018 10:33AM

le...@gmail.com <le...@gmail.com> #68Jun 12, 2018 05:18PM

pi...@gmail.com <pi...@gmail.com> #69Jun 17, 2018 08:35AM

yi...@gmail.com <yi...@gmail.com> #70Jun 21, 2018 07:31AM

de...@gmail.com <de...@gmail.com> #71Jun 21, 2018 07:51AM

t....@gmail.com <t....@gmail.com> #72Jun 21, 2018 10:09AM

cn...@gmail.com <cn...@gmail.com> #73Jul 5, 2018 07:31PM

za...@gmail.com <za...@gmail.com> #74Jul 5, 2018 07:38PM

da...@gmail.com <da...@gmail.com> #75Jul 6, 2018 11:59AM

[Deleted User] <[Deleted User]> #76Jul 24, 2018 02:04PM