Fixed

Bug

Status Update

No update yet.

Description

al...@ifit.com

created issue #1

Feb 22, 2023 07:17PM

I use ADB alot for my work and recently updated my platform tools version to the latest using brew as that is what I use to manage android-platform-tools. When I updated to the latest version, I noticed the adb install command over USB wasn't working anymore. I checked it with adb over WiFi and it is still working, but it won't work over USB. It just sits and hangs on the performing streamed install. I downloaded the previous platform tools version, 33.0.3, and ran the adb tool from there and the adb install over usb was working. So something in the new platform tools version broke it. Please fix.

Comments

en...@google.com <en...@google.com> #2Feb 22, 2023 09:48PM

Status: Won't Fix (Infeasible)

I have this issue as well.
Same issue:

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

al...@ifit.com <al...@ifit.com> #3Feb 22, 2023 09:55PM

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

al...@ifit.com <al...@ifit.com> #4Feb 22, 2023 10:01PM

Same on my Windows 10 computer.

en...@google.com <en...@google.com> #5Feb 22, 2023 10:02PM

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

al...@ifit.com <al...@ifit.com> #6Feb 22, 2023 10:08PM

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

al...@ifit.com <al...@ifit.com> #7Feb 22, 2023 10:08PM

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

al...@ifit.com <al...@ifit.com> #8Feb 23, 2023 10:12PM

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

en...@google.com <en...@google.com> #9Feb 24, 2023 05:37PM

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

al...@ifit.com <al...@ifit.com> #10Feb 24, 2023 08:47PM

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>

al...@ifit.com <al...@ifit.com> #11Feb 24, 2023 08:50PM

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.

en...@google.com <en...@google.com> #12Feb 24, 2023 11:42PM

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?

al...@ifit.com <al...@ifit.com> #13Feb 25, 2023 12:33AM

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

en...@google.com <en...@google.com> #14Feb 25, 2023 12:42AM

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

my mail is: 3loumwm3arif@gmail.com

sh...@google.com <sh...@google.com> #15Feb 25, 2023 01:08AM

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?

sh...@google.com <sh...@google.com> #16Feb 25, 2023 01:12AM

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

al...@ifit.com <al...@ifit.com> #17Feb 27, 2023 04:37PM

Delete

en...@google.com <en...@google.com> Feb 27, 2023 07:18PM

Status: Assigned (reopened)

sh...@google.com <sh...@google.com> Feb 27, 2023 08:01PM

Accepted by sh...@google.com.

go...@gmail.com <go...@gmail.com> #18Mar 9, 2023 06:25AM

Hmmm

on...@gmail.com <on...@gmail.com> #19Mar 10, 2023 09:26AM

sh...@google.com <sh...@google.com> #20Mar 19, 2023 11:35PM

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

al...@ifit.com <al...@ifit.com> #21Mar 20, 2023 05:49PM

#20

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

al...@ifit.com <al...@ifit.com> #22Mar 20, 2023 05:54PM

en...@google.com <en...@google.com> #23Mar 20, 2023 07:46PM

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

al...@ifit.com <al...@ifit.com> #24Mar 20, 2023 07:50PM

en...@google.com <en...@google.com> #25Mar 20, 2023 09:03PM

Thanks

sh...@google.com <sh...@google.com> #26Mar 23, 2023 03:03PM

testing

al...@ifit.com <al...@ifit.com> #27Mar 23, 2023 08:38PM

-hotlist Google domain
+hotlist 2367385

al...@ifit.com <al...@ifit.com> #28Mar 23, 2023 09:00PM

---------- ထပ်ဆင့်ပေးပို့သည့်မက်ဆေ့ချ် ----------
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>

sh...@google.com <sh...@google.com> #29Mar 23, 2023 09:15PM

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

- Show quoted text -

al...@ifit.com <al...@ifit.com> #30Mar 23, 2023 09:18PM

Mmmank

en...@google.com <en...@google.com> #31Mar 23, 2023 09:24PM

TITsovneMakara@gmail.com

al...@ifit.com <al...@ifit.com> #32Mar 23, 2023 09:30PM

Feedback

al...@ifit.com <al...@ifit.com> #33Mar 23, 2023 09:45PM

aaireill111@gmail.com

sh...@google.com <sh...@google.com> #34Mar 25, 2023 05:53PM

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

al...@ifit.com <al...@ifit.com> #35Mar 27, 2023 03:17PM

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.

sh...@google.com <sh...@google.com> #36Mar 28, 2023 10:51AM

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

- Show quoted text -

sh...@google.com <sh...@google.com> #37Mar 28, 2023 11:05AM

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 -

al...@ifit.com <al...@ifit.com> #38Mar 28, 2023 11:40PM

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

en...@google.com <en...@google.com> #39Mar 28, 2023 11:46PM

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

al...@ifit.com <al...@ifit.com> #40Mar 29, 2023 03:17PM

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

sh...@google.com <sh...@google.com> #41Mar 29, 2023 04:30PM

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

al...@ifit.com <al...@ifit.com> #42Mar 29, 2023 05:32PM

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

adb.CLEARENDPOINTS0.log

26 KB

View

Download

adb.CLEARENDPOINTS1.log

71 KB

View

Download

al...@ifit.com <al...@ifit.com> #43Mar 30, 2023 07:57PM

hi my name abdulrahman afghan
help me japan tool

do...@gmail.com <do...@gmail.com> #44Mar 31, 2023 08:01AM

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

- Show quoted text -

do...@gmail.com <do...@gmail.com> #45Mar 31, 2023 08:03AM

good bay!

1381662341mohamadsalmanpor

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

- Show quoted text -

do...@gmail.com <do...@gmail.com> #46Mar 31, 2023 09:35AM

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

zh...@gmail.com <zh...@gmail.com> #47Mar 31, 2023 10:47AM

1381662341:issu

1381662341mohamadsalmanpor

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

- Show quoted text -

ch...@gmail.com <ch...@gmail.com> #48Apr 3, 2023 09:08AM

Hjh

al...@ifit.com <al...@ifit.com> #49Apr 4, 2023 09:23PM

My device esim update 13 on drive

sh...@google.com <sh...@google.com> #50Apr 5, 2023 12:31AM

al...@ifit.com <al...@ifit.com> #51Apr 7, 2023 07:52PM

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

- Show quoted text -

yo...@gmail.com <yo...@gmail.com> #52Apr 8, 2023 03:33AM

Android

ma...@gmail.com <ma...@gmail.com> #53Apr 9, 2023 11:33PM

Boa noite sou novo aqui mecânico de motos a 30 anos preciso evoluir rs

ma...@gmail.com <ma...@gmail.com> #54Apr 9, 2023 11:35PM

Boa noite como sou mecânico de motos preciso de velocidade 🚄

ma...@gmail.com <ma...@gmail.com> #55Apr 9, 2023 11:37PM

Como destravar evoluir perdão fuiii tão rápido que não dei boa-noite

zh...@gmail.com <zh...@gmail.com> #56Apr 12, 2023 03:34AM

ARM M1 Mac;
Darwin Kernel Version 22.4.0;
Android 9, but different devices with the same version have different connection results.
Currently using adb version 33.0.3 with no issues.

[Deleted User] <[Deleted User]> #57Apr 13, 2023 12:39AM

He he

al...@ifit.com <al...@ifit.com> #58May 11, 2023 09:59PM

Any updates on this issue?

sh...@google.com <sh...@google.com> #59May 13, 2023 03:55AM

For the immediate short-term, can you please test out the following:
$ export ADB_LIBUSB=1
$ adb kill-server && adb root

I hope you'll be able to get past that IOService error ( "usb_osx.cpp:170] Unable to create an interface plug-in (e00002be)") when attempting to execute `adb install <>`

al...@ifit.com <al...@ifit.com> #60May 16, 2023 09:55PM

When I tried running the: $adb kill-server && adb root command after running the: $export ADB_LIBUSB=1 command I got the following error: adb: unable to connect for root: device offline

So I just ran the adb install after I set the export ADB_LIBUSB=1 and it installed successfully.

sh...@google.com <sh...@google.com> May 16, 2023 09:57PM

Marked as fixed.

al...@ifit.com <al...@ifit.com> #61May 17, 2023 09:48PM

Am I ok to update to platform tools version 34.0.1 or should I stay on 34.0.0?

sh...@google.com <sh...@google.com> #62May 17, 2023 09:55PM

We're on track to release 34.0.3 shortly (which includes a fastboot resolution). Meanwhile, yes - you can upgrade to 34.0.1 if you so wish (subject to the workaround above, if/when you run into the known problem on Intel/Mac).

al...@ifit.com <al...@ifit.com> #63May 17, 2023 10:11PM

Ok sounds good. Thank you.

ki...@gmail.com <ki...@gmail.com> #64May 21, 2023 09:17AM

ra...@gmail.com <ra...@gmail.com> #65May 24, 2023 04:17PM

Hey everyone! I had the same problem and this solution fixed my issues. I wanted to share the issue I was facing with ADB on a physical device. It was driving me crazy, but I managed to resolve it, and I thought it would be helpful to share it here for anyone who might face the same problem in the future.

First off, let me provide some context. I'm using a MacBook Pro Mid 2012 with an Intel 7 processor, and I'm running MacOS Monterey using OpenCore-Legacy-Patcher. The emulator was working fine, but I encountered errors when connecting a physical device (Samsung) to my setup.

When I ran flutter doctor -v without any phone connected, everything seemed to be in order. However, when I connected my phone, things went south. The error message I received was:

Exception: Unable to run "adb", check your Android SDK installation and ANDROID_SDK_ROOT environment variable:
/Users/me/Library/Android/sdk/platform-tools/adb

After some investigation, I came across this solution and it worked for me. Here are the steps I took:

Open a terminal window.
Run the following commands:

export ADB_LIBUSB=1
adb kill-server && adb root

After running these commands, I ran flutter doctor -v again, and voila! The issue was resolved, and everything was working smoothly. Here's the output I received:

[✓] Flutter (Channel stable, 3.3.3, on macOS 12.6.5 21G531 darwin-x64, locale en-CA)
    • Flutter version 3.3.3 on channel stable at /Users/lifen/SDKs/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18a827f393 (8 months ago), 2022-09-28 10:03:14 -0700
    • Engine revision 5c984c26eb
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/lifen/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • ANDROID_SDK_ROOT = /Users/lifen/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F17a
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (3 available)
    • SM A520W (mobile) • 521011e6fca754cf • android-arm64 • Android 8.0.0 (API 26)
    • macOS (desktop) • macos • darwin-x64 • macOS 12.6.5 21G531 darwin-x64
    • Chrome (web) • chrome • web-javascript • Google Chrome 113.0.5672.126

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Explanation from ChatGPT:

The commands you ran did two things:

export ADB_LIBUSB=1: This command sets the ADB_LIBUSB environment variable to 1. When this variable is set, ADB uses the libusb library instead of the default USB library. This can sometimes resolve issues with device detection if there are problems with the default USB library.

adb kill-server && adb root: This command does two things. First, adb kill-server stops the ADB server process. Then, adb root restarts the ADB server with root permissions. This can resolve issues with device detection if the ADB server was not running or was running without the necessary permissions.

So, in summary, your issue was likely due to a problem with ADB, either because the Android SDK was not installed correctly, the ANDROID_SDK_ROOT environment variable was not set correctly, or the ADB server was not running with the necessary permissions. The commands you ran changed how ADB interacts with USB devices and restarted the ADB server with root permissions, which resolved the issue.

I hope this solution works for you too! If you have any questions or need further assistance, feel free to ask. Happy coding!

jq...@gmail.com <jq...@gmail.com> #66May 30, 2023 02:43PM

Anything okay

da...@gmail.com <da...@gmail.com> #67Jun 1, 2023 09:49AM

de...@gmail.com <de...@gmail.com> #68Jun 1, 2023 11:48PM

ol...@gmail.com <ol...@gmail.com> #69Jul 11, 2023 03:45AM

adb is GitHub the issue? olsonsebastian13@gmail.com SEBASTIAN S OLSON (406)849-1540✅

icon_tasker.png

5.7 KB

View

Download

icon_tasker_old.png

4.9 KB

View

Download

th...@gmail.com <th...@gmail.com> #70Jul 19, 2023 11:10AM

Thephong.dthap2023@gmail.com.google.android.play.games&st

va...@hotmail.com <va...@hotmail.com> Jul 24, 2023 03:10PM

droidscript_logo_64x64.png

5.6 KB

View

Download

sc...@gmail.com <sc...@gmail.com> #71Jul 25, 2023 05:36AM

It works abspultyely fine after installing mac os venture using open core i faced the issue with adb unable to locate adb or you can say my android device was not detected in android studio after running the commands it works fine.
export ADB_LIBUSB=1
adb kill-server && adb root

ja...@gmail.com <ja...@gmail.com> #72Aug 8, 2023 06:31AM

ATTN:al...@ifit.com

but @<en...@google.com>
"so in the meantime, there are lots of other more bugs to look at, that we're already convinced are real.

you can make this bug more convincing by trying to work out what the actual variable is --- is it some specific model of mac? is it only some specific macOS versions? android versions? is there anything interesting in logcat?"

Isn't that your job? I guess someone should get you some type of underling to pick up your slack. I mean, I'm just saying.
..l.. (-_-) ..l..

de...@gmail.com <de...@gmail.com> #73Aug 25, 2023 12:16PM

Latest Mac OS X Ventura 13.5 (22G74) on M2 Macbook (was also reproduced on 2014 Intel Macbook with the latest Big Sur).
Device: moto g6
Android version: 9

The latest adb doesn't work. It hangs for any command like adb install, adb shell, etc.

Workaround:
1. Download older adb from

https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip
2. export PATH=~/Downloads/platform-tools:$PATH
3. adb kill-server
4. You may need to reconnect your device

Please fix this bug, it is very annoying.

sh...@google.com <sh...@google.com> #74Aug 25, 2023 03:20PM

Do you see the following log entry (in the adb server logs)?
adb E 08-25 08:19:46 97552 2437794 usb_osx.cpp:175] Unable to create an interface plug-in (e00002be)

ms...@masslight.com <ms...@masslight.com> #75Aug 31, 2023 01:08PM

I concur the issue exists on MacOS Ventura 13.5 (M1) and adb Version 34.0.4-10411341.

An excerpt from the adb log:

adb server killed by remote request
08-31 15:49:48.894 41776 3136798 I adb     : transport.cpp:1155 kicking transport 0x141e05120 fdd8dd0
08-31 15:49:48.894 41776 3136798 I adb     : transport.cpp:407 BlockingConnectionAdapter(fdd8dd0): stopping
08-31 15:49:48.894 41776 3136798 I adb     : usb_osx.cpp:617 Kicking handle
08-31 15:49:48.894 41776 3136804 E adb     : usb_osx.cpp:592 usb_read failed with status: e00002eb
08-31 15:49:48.894 41776 3136804 I adb     : transport.cpp:339 fdd8dd0: read failed: Undefined error: 0
08-31 15:49:48.894 41776 3136804 I adb     : transport.cpp:1248 fdd8dd0: connection terminated: read failed
08-31 15:49:48.894 41776 3136798 I adb     : transport.cpp:425 BlockingConnectionAdapter(fdd8dd0): stopped

Setting the ADB_LIBUSB fixes an issue.

sh...@google.com <sh...@google.com> #76Sep 1, 2023 04:28AM

What version of Android device are you seeing this against?

ms...@masslight.com <ms...@masslight.com> #77Sep 1, 2023 08:31AM

Sorry, forgot to mention, it's on Android 9.0.6.

mo...@gmail.com <mo...@gmail.com> #78Sep 4, 2023 11:51AM

ReevesCharles

sh...@google.com <sh...@google.com> #79Sep 5, 2023 04:23AM

Can you please try the same workflow (`adb install <apk>`) on a tcpip connection (using `adb connect ip:port`)? yes, you'll need to initially connect over USB but once you establish tcpip connectivity that should get you past this issue (since this's not something that most users encounter, and the underlying root-cause has to do more with Apple than AOSP).

ms...@masslight.com <ms...@masslight.com> #80Sep 6, 2023 12:15PM

Attaching three files with logs:

ADB_LIBUSB is set -- OK.
ADB_LIBUSB is unset -- FAILS.
ADB_LIBUSB is set and copy over tcpip succeeds.

adb_libusb_is_on__success.txt

7.4 KB

View

Download

adb_libusb_is_off__failed.txt

1.9 KB

View

Download

adb_libusb_is_off__success_over_tcpip.txt

4.3 KB

View

Download

ms...@masslight.com <ms...@masslight.com> #81Sep 6, 2023 12:20PM

Correction to the above (can't edit):

ADB_LIBUSB is UNSET and copy over tcpip succeeds.

mo...@gmail.com <mo...@gmail.com> #82Sep 11, 2023 03:03PM

This is marked as closed and in the release notes for 34.0.4 but I'm not sure it's actually been addressed.

Running 34.0.4 adb very often hangs on install on my laptop. Reverting to 33.0.3 fixes the issue as mentioned above.

Once adb hangs on install it will also hang on any other commands until I run adb kill-server && adb start-server. This fixes the issue for a short period of time, but the next install will often fail.

I'm running this on a Macbook Pro with an M1 chip, running Ventura 13.4.

sh...@google.com <sh...@google.com> Sep 12, 2023 05:38AM

Status: Assigned (reopened)

si...@gmail.com <si...@gmail.com> #83Sep 14, 2023 07:46PM

Fix bug report issue my phone app

sh...@google.com <sh...@google.com> Sep 15, 2023 09:04PM

Accepted by sh...@google.com.

po...@gmail.com <po...@gmail.com> #84Sep 17, 2023 09:35PM

adb kill-server && adb start-server

da...@gmail.com <da...@gmail.com> Sep 24, 2023 10:35PM

Is there a Slang.net app available for Android_.pdf

446 KB

View

Download

rk...@hubspot.com <rk...@hubspot.com> #85Sep 25, 2023 01:01PM

Is there any update on this? My team and I are strongly affected by this as it really breaks the flow if you have to restart adb every couple of minutes. It works for a few builds but then quickly stops working... Is there anything we can do locally to circumvent the problem until the problem is fixed?

no...@gmail.com <no...@gmail.com> #86Sep 27, 2023 06:15AM

Adb kill server

sh...@google.com <sh...@google.com> #87Sep 27, 2023 06:40AM

Did you try resolving the issue with the ADB_LIBUSB env variable set to "1"?

wa...@gmail.com <wa...@gmail.com> #88Oct 4, 2023 11:11PM

Thank

aa...@gmail.com <aa...@gmail.com> #89Oct 15, 2023 02:21AM

var loop = function() { // do cool stuff }

sh...@google.com <sh...@google.com> #90Oct 16, 2023 11:41PM

Marked as fixed.

https://android-review.git.corp.google.com/c/platform/packages/modules/adb/+/2754050

ls...@gmail.com <ls...@gmail.com> #91Oct 19, 2023 04:35PM

Hi any estimate when the fix will be released? This is impacting a lot our productivity. Even an alpha channel would be helpful

sh...@google.com <sh...@google.com> #92Nov 4, 2023 01:00AM

The default for MacOS platforms are already libusb (34.0.5 release, which is the latest downloadable one).
Alternatively, set the env variable mentioned in

comment#87

ew...@dropbox.com <ew...@dropbox.com> #93Nov 6, 2023 09:09PM

Still having issues on the 34.0.5 release. Now when it hangs we cannot run `adb kill-server` to restart adb and have to kill the process at the OS level.

sh...@google.com <sh...@google.com> #94Nov 7, 2023 05:23PM

Release Notes:

https://developer.android.google.cn/tools/releases/platform-tools

ve...@whirlpool.com <ve...@whirlpool.com> #95Nov 8, 2023 10:04PM

Comment has been deleted.

Message last modified on Nov 8, 2023 10:05PM

ve...@whirlpool.com <ve...@whirlpool.com> #96Nov 8, 2023 10:09PM

Is there a solution for this issue yet , still facing the same problems with adb install

dj...@gmail.com <dj...@gmail.com> #97Nov 8, 2023 10:22PM

doc/api/n-api.md

sh...@google.com <sh...@google.com> #98Nov 8, 2023 10:29PM

>>Now when it hangs we cannot run `adb kill-server` to restart adb and have to kill the >>process at the OS level.

It should *not* hang. If it does, the logs need to be uploaded to an appropriate bug (spanning `adb kill-server` )

rk...@hubspot.com <rk...@hubspot.com> #99Nov 13, 2023 11:30AM

I'm on 34.0.5 now for a few weeks now and the problem is still the same as with previous version - adb only works for a few minutes after killing it.

sh...@google.com <sh...@google.com> #100Nov 13, 2023 06:02PM

Status: Assigned (reopened)

@rk...@hubspot.com: What's your host platform? Did you try ADB_LIBUSB? Do you have host/server logs? What's your Android kernel version? Do you have hubs in the middle? Can you reliably reproduce this? Assuming you have a fragile infrastructure (host, cables, hubs, test infra), consider switching to ADB_LIBUSB or Wireless transport (if applicable).

rk...@hubspot.com <rk...@hubspot.com> #101Nov 17, 2023 11:27AM

Hello, I'm mostly experiencing this while developing on the Android emulators, but it's happening on all emulators and on a physical device (specs below). In terms of connection it happens on the emulator, usb-C cable (tried 2 different ones, with 2 different original Apple hubs) and on Wi-Fi debugging connection.

In terms of reproducibility, it's reproducible 100%. But I can't trigger it. I stop ADB by running killall -9 adb, Android studio reconnects it and it works for cca. 15-30 minutes. And then at some point, suddenly, stops working.

Symptoms:

logcat in AS stops updating
trying to install the app through AS doesn't work (says "waiting for devices" but never finishes)
debugger doesn't connect
adb commands mostly don't respond, except for --help or --version (I guess because they're static and don't rely on server)

About ADB_LUBUSB, I'm only running adb from Android Studio. How do I tell it to export that value to 1? I also don't know how to get logs on adb. Googling didn't help, I only found instructions on how to get logs off the Android device that's connected over adb, not for the adb itself. Any tips?

Computer

Apple M1 Max
macOS Ventura 13.6

Android Studio

Android Studio Giraffe | 2022.3.1 Patch 4
Build #AI-223.8836.35.2231.11090377, built on November 13, 2023
Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

Devices

Emulator Pixel 4, API 33, Android 13.0 Google Play, arm64-v8a (used mostly)
Emulator Pixel 6a, API 34, Android 14.0 Google Play, arm64-v8a
OnePlus 8, Android 13

Java version

➜  ~ java --version
openjdk 17.0.6 2023-01-17
OpenJDK Runtime Environment Temurin-17.0.6+10 (build 17.0.6+10)
OpenJDK 64-Bit Server VM Temurin-17.0.6+10 (build 17.0.6+10, mixed mode)

ADB version

➜  ~ adb --version
Android Debug Bridge version 1.0.41
Version 34.0.5-10900879
Installed as /Users/.../Library/Android/sdk/platform-tools//adb
Running on Darwin 22.6.0 (arm64)

rk...@hubspot.com <rk...@hubspot.com> #102Nov 17, 2023 01:41PM

I set the ADB_LIBUSB to 1 and it still happened:

➜  ~ killall -9 adb
➜  ~ export ADB_LIBUSB=1  
➜  ~ echo $ADB_LIBUSB 
1
➜  ~ adb devices
List of devices attached
emulator-5554	device

// 1 hour later ...

➜  ~ echo $ADB_LIBUSB   
1
➜  ~ adb devices
^C                   <- I had to kill the command manually as it didn't return anything for 1 minute
➜  ~ killall -9 adb
➜  ~ adb devices
List of devices attached
emulator-5554	device

sh...@google.com <sh...@google.com> Nov 17, 2023 02:46PM

Accepted by sh...@google.com.

sc...@gmail.com <sc...@gmail.com> #103Nov 24, 2023 12:32PM

---------- Forwarded message ---------
From: <buganizer-system@google.com>
Date: Mon, Oct 16, 2023, 6:42 PM
Subject: Re:

Issue 270205252

: ADB install not working on Android 9 with
latest platform tools version 34.0.0
To: <b-system+404257552@google.com>
Cc: <schultrodney928@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/270205252

*Changed*
status: In Progress (Accepted) → Fixed

*sh...@google.com <sh...@google.com> added

comment #90

https://issuetracker.google.com/issues/270205252#comment90>:*

https://android-review.git.corp.google.com/c/platform/packages/modules/adb/+/2754050

_______________________________

*Reference Info: 270205252 ADB install not working on Android 9 with latest
platform tools version 34.0.0*
component: Android Public Tracker > App Development > SDK > platform tools
> adb <

https://issuetracker.google.com/components/192795>
status: Fixed
reporter: al...@ifit.com
assignee: sh...@google.com
cc: al...@ifit.com, ja...@google.com, sh...@google.com, and 3 more
type: Bug
access level: Default access
priority: P2
severity: S2
blocking: 269001731 <

https://issuetracker.google.com/issues/269001731>
duplicate issue: 288902771
<

https://issuetracker.google.com/issues/288902771>, 304807297
<

https://issuetracker.google.com/issues/304807297>
retention: Component default

Generated by Google IssueTracker notification system

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

issue 270205252

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

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

sh...@google.com <sh...@google.com> #104Nov 24, 2023 03:33PM

Follow steps below to capture logs from your Mac M1. Since the failure in your environment occurs over a wide time window, it's important to
identify the approximate timestamp at which you suspect connectivity dropped.

Host debugging:
- set ADB_TRACE (dynamic setting)
- aosp-master$ export ADB_TRACE=all
- On MacOS, the logs can be found in the directory pointed by the TMPDIR environment variable.
-$ tail -f /tmp/adb*.log
adb I 02-08 09:30:25 139670 139670 main.cpp:62] Android Debug Bridge version 1.0.41
<snip>

Device-side (adbd) debugging:
Set trace_mask on
Restart the daemon and analyze the logs. Caveat is that the device-logs tend to be noisy.
$ adb shell getprop persist.adb.trace_mask
1
$ adb shell setprop persist.adb.trace_mask 0
$ adb shell pkill adbd
$ adb shell
# cd /data/adb
/data/adb # ls -al
total 23
drwx------ 2 root root 3488 2022-02-08 18:04 .
drwxrwx--x 49 system system 4096 2022-01-18 12:13 ..
-rw------- 1 root root 8521 2022-02-08 18:05 adb-2022-02-08-18-04-49-18527
Error(s) that you may run into, and resolution:
$ adb shell setprop persist.adb.trace_mask 0
Failed to set property 'persist.adb.trace_mask' to '0'.
See dmesg for error reason.
$ adb root
$ adb shell setprop persist.adb.trace_mask 0

>>happens on the emulator, usb-C cable (tried 2 different ones, with 2 different original Apple hubs) and on Wi-Fi debugging connection.
FYI, `WiFi Debugging` runs over a different transport therefore it might make sense to open a separate bug for any failure you
experience over that transport. In fact, libusb transport is also distinct from the legacy transport (as far as the possible failure point which is likely USB, is concerned).

One other question: do you experience this failure from adb alone? (if you eliminate Android Studio from this equation)
Studio interacts with the adb server (and is itself the equivalent of the adb client).
If not, the Studio logs are also relevant.

dj...@gmail.com <dj...@gmail.com> #105Nov 28, 2023 03:54AM

https://zoho.com/us/expense/kb/reports/share-my-report/

sh...@google.com <sh...@google.com> #106Nov 29, 2023 12:32AM

Marked as fixed.

Log/trace instructions are on aosp:

https://android-review.git.corp.google.com/c/platform/packages/modules/adb/+/2845056

ga...@gmail.com <ga...@gmail.com> #107Nov 29, 2023 12:49AM

Keep the rhythm step by step

El mar., 28 de noviembre de 2023 18:33, <buganizer-system@google.com>
escribió:

- Show quoted text -

li...@gmail.com <li...@gmail.com> #108Dec 13, 2023 12:14PM

Very much appreciated but I don't know how to make you leave me alone and quit stalking me for the person at 3958 Madison Street she is not interested in my intruders of my life good luck with it's not due to anything I have done for you to re think what you are embarking on

sc...@gmail.com <sc...@gmail.com> #109Dec 21, 2023 06:41AM

On Wed, Dec 20, 2023, 02:03 <buganizer-system@google.com> wrote:

- Show quoted text -

he...@gmail.com <he...@gmail.com> #110Jan 1, 2024 06:15PM

henokdegefe@gmail.com

ra...@gmail.com <ra...@gmail.com> #111Jan 5, 2024 09:19AM

Comment has been deleted.

Message last modified on Jan 5, 2024 09:23AM

ra...@gmail.com <ra...@gmail.com> #112Jan 5, 2024 09:20AM

Comment has been deleted.

Message last modified on Jan 5, 2024 09:23AM

ch...@gmail.com <ch...@gmail.com> #113Jan 11, 2024 09:01AM

所以，现在这个bug已经被修复了吗？

hs...@gmail.com <hs...@gmail.com> #114Feb 8, 2024 03:21PM

فعلت تحديث كامل للفون software

rk...@hubspot.com <rk...@hubspot.com> #115Feb 12, 2024 05:16PM

Hey sh... sorry for the late reply. The problem is still here. I tried the steps you wrote above and I can't activate the root user, I get this:

➜  ~ adb shell setprop persist.adb.trace_mask 0
Failed to set property 'persist.adb.trace_mask' to '0'.
See dmesg for error reason.
➜  ~ adb root
adbd cannot run as root in production builds
➜  ~

What does this mean? Any way around that?

ja...@gmail.com <ja...@gmail.com> #116Mar 4, 2024 09:02PM

Dit not work on my tecno spark 8c

On Sun, Mar 3, 2024, 4:59 AM <buganizer-system@google.com> wrote:

- Show quoted text -

rk...@hubspot.com <rk...@hubspot.com> #117Mar 5, 2024 11:43AM

I managed to find a solution to the problem adbd cannot run as root in production builds, I had to use the emulator without Play Store included, I had only the Google APIs.

rk...@hubspot.com <rk...@hubspot.com> #118Mar 5, 2024 11:46AM

Regarding the original issue, this weekend I updated my Android Studio to the stable Iguana 2023.2.1 and I also update SDK which included ADB 35.0.0-11411520 (1.0.41) and for the past 27 hours I didn't have to kill adb once. So it seems the problem is fixed, at least for me. Thanks!

ja...@gmail.com <ja...@gmail.com> #119Mar 9, 2024 08:38PM

لايتم تثبيت البرنامج او اتطبيقات بشكل اصحيح لان الحزمة لا تقبل يفشل اتثبيت وشكرا

ia...@gmail.com <ia...@gmail.com> #120Apr 5, 2024 12:59AM

How install

ka...@gmail.com <ka...@gmail.com> #121Apr 25, 2024 11:59PM

Install all new

al...@gmail.com <al...@gmail.com> #122May 24, 2024 08:13PM

حلو

[Deleted User] <[Deleted User]> #123May 25, 2024 02:28PM

Reinstall all

rk...@hubspot.com <rk...@hubspot.com> #124May 29, 2024 12:12PM

I'm sad to inform you that the issue reappeared. My whole team and I are back to killing adb on an hourly basis. :(

rk...@hubspot.com <rk...@hubspot.com> #125May 29, 2024 12:14PM

I'm on

Android Debug Bridge version 1.0.41
Version 35.0.0-11411520
Running on Darwin 23.5.0 (arm64)

And Android Studio is

Android Studio Jellyfish | 2023.3.1 Patch 1
Build #AI-233.14808.21.2331.11842104, built on May 15, 2024
Runtime version: 17.0.10+0-17.0.10b1087.21-11572160 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

ab...@gmail.com <ab...@gmail.com> #126Jun 4, 2024 11:35AM

#270205252

[Deleted User] <[Deleted User]> #127Jun 4, 2024 11:32PM

https://support.microsoft.com/en-us/feed/rss/ec99850d-21a3-8453-ca47-447a97b72d4c

ab...@gmail.com <ab...@gmail.com> #128Jun 8, 2024 02:02PM

Job #7016766573 failed for bfa1f69b05c111e8b5a0cd597b19b227a1dd14c2:

ab...@gmail.com <ab...@gmail.com> #129Jun 16, 2024 02:47AM

https://raw.githubusercontent.com/michaelWuensch/BitBanana/master/docs/REPRODUCE.md

ab...@gmail.com <ab...@gmail.com> #130Jun 20, 2024 04:36PM

@gh voda unlimited 💓.tnl

kr...@gmail.com <kr...@gmail.com> #131Jun 28, 2024 01:19PM

This fix has made my custom AOSP based device not being recognized as an Android device (not there at all on the adb devices list). Only downgrading to 34.0.4 helps. OSX Sonoma 14.5, MacBook Air M2.

Let me know if you'd like me to provide some debug logs to help with fixing that in the latest version.

am...@gmail.com <am...@gmail.com> #132Jul 3, 2024 02:07AM

I need to Update my New Phone right now to android 15

em...@sumup.com <em...@sumup.com> #133Jul 18, 2024 01:40PM

Hello, this issue is very present for us. We have a custom AOSP-based device (Android 10) that now often fails to be shown in the device list or hangs on the install command. Sometimes, downgrading to adb prior to 34.0.5 fixes the issue, sometimes upgrading above 34.0.4 fixes it. Sometimes it cannot be fixed. So far we were unable to find a correlation between OS&hardware and the step that fixes it.

Here are adb host logs from a device that attempted connecting with adb 34.0.4-10411341. It is an M1 Pro with Ventura 13.6.1.

One file has the logs where the device was not listed with adb devices, the other file are the logs from where adb devices showed the device, but then adb install hung indefinitely.

adb_devices_not_listing_device.log

46 KB

View

Download

adb_devices_works_then_install_hangs.log

45 KB

View

Download

en...@google.com <en...@google.com> #134Jul 18, 2024 02:08PM

both of those traces seem to be using the non-libusb macOS usb backend, which is no longer supported. please repro with a 35.* adb using libusb.

em...@sumup.com <em...@sumup.com> #135Jul 31, 2024 02:57PM

Here's a host log from one of our devices that fails to recognize the attached device (adb devices returns nothing) on ADB 35.0.1

The device is a MacBook Pro M3 with Sonoma 14.5.

I've not been able to find someone to reproduce the indefinite install hang on 35+, yet, but I know we had this in the past (unfortunately without collecting host logs). I'll continue to ask around.

adb.502 (2).log

11 KB

View

Download

m2...@gmail.com <m2...@gmail.com> Sep 1, 2024 12:14AM

1_5071419141697570216.mp4

7.5 MB

Download

am...@gmail.com <am...@gmail.com> #136Nov 25, 2024 07:56AM

b....@gmail.com <b....@gmail.com> #137
Restricted
Nov 26, 2024 04:56AM

Comment has been deleted.

deleted

Restricted+

0 B

b....@gmail.com <b....@gmail.com> #138
Restricted
Nov 26, 2024 04:58AM

Comment has been deleted.

mw...@gmail.com <mw...@gmail.com> #139Dec 12, 2024 01:31PM

#404

ko...@gmail.com <ko...@gmail.com> #140Jan 17, 2025 09:00PM

Kongpc14567@gmail.com

Issue 270205252

Description

Issue summary

Comments

en...@google.com <en...@google.com> #2Feb 22, 2023 09:48PM

al...@ifit.com <al...@ifit.com> #3Feb 22, 2023 09:55PM

al...@ifit.com <al...@ifit.com> #4Feb 22, 2023 10:01PM

en...@google.com <en...@google.com> #5Feb 22, 2023 10:02PM

al...@ifit.com <al...@ifit.com> #6Feb 22, 2023 10:08PM

al...@ifit.com <al...@ifit.com> #7Feb 22, 2023 10:08PM

al...@ifit.com <al...@ifit.com> #8Feb 23, 2023 10:12PM

en...@google.com <en...@google.com> #9Feb 24, 2023 05:37PM

al...@ifit.com <al...@ifit.com> #10Feb 24, 2023 08:47PM

al...@ifit.com <al...@ifit.com> #11Feb 24, 2023 08:50PM

en...@google.com <en...@google.com> #12Feb 24, 2023 11:42PM

al...@ifit.com <al...@ifit.com> #13Feb 25, 2023 12:33AM

en...@google.com <en...@google.com> #14Feb 25, 2023 12:42AM

sh...@google.com <sh...@google.com> #15Feb 25, 2023 01:08AM

sh...@google.com <sh...@google.com> #16Feb 25, 2023 01:12AM

al...@ifit.com <al...@ifit.com> #17Feb 27, 2023 04:37PM

en...@google.com <en...@google.com> Feb 27, 2023 07:18PM

sh...@google.com <sh...@google.com> Feb 27, 2023 08:01PM

go...@gmail.com <go...@gmail.com> #18Mar 9, 2023 06:25AM

on...@gmail.com <on...@gmail.com> #19Mar 10, 2023 09:26AM

sh...@google.com <sh...@google.com> #20Mar 19, 2023 11:35PM

al...@ifit.com <al...@ifit.com> #21Mar 20, 2023 05:49PM

al...@ifit.com <al...@ifit.com> #22Mar 20, 2023 05:54PM

en...@google.com <en...@google.com> #23Mar 20, 2023 07:46PM

al...@ifit.com <al...@ifit.com> #24Mar 20, 2023 07:50PM

en...@google.com <en...@google.com> #25Mar 20, 2023 09:03PM

sh...@google.com <sh...@google.com> #26Mar 23, 2023 03:03PM

al...@ifit.com <al...@ifit.com> #27Mar 23, 2023 08:38PM

al...@ifit.com <al...@ifit.com> #28Mar 23, 2023 09:00PM

sh...@google.com <sh...@google.com> #29Mar 23, 2023 09:15PM

al...@ifit.com <al...@ifit.com> #30Mar 23, 2023 09:18PM

en...@google.com <en...@google.com> #31Mar 23, 2023 09:24PM

al...@ifit.com <al...@ifit.com> #32Mar 23, 2023 09:30PM

al...@ifit.com <al...@ifit.com> #33Mar 23, 2023 09:45PM

sh...@google.com <sh...@google.com> #34Mar 25, 2023 05:53PM

al...@ifit.com <al...@ifit.com> #35Mar 27, 2023 03:17PM

sh...@google.com <sh...@google.com> #36Mar 28, 2023 10:51AM

sh...@google.com <sh...@google.com> #37Mar 28, 2023 11:05AM

al...@ifit.com <al...@ifit.com> #38Mar 28, 2023 11:40PM

en...@google.com <en...@google.com> #39Mar 28, 2023 11:46PM

al...@ifit.com <al...@ifit.com> #40Mar 29, 2023 03:17PM

sh...@google.com <sh...@google.com> #41Mar 29, 2023 04:30PM

al...@ifit.com <al...@ifit.com> #42Mar 29, 2023 05:32PM

al...@ifit.com <al...@ifit.com> #43Mar 30, 2023 07:57PM

do...@gmail.com <do...@gmail.com> #44Mar 31, 2023 08:01AM

do...@gmail.com <do...@gmail.com> #45Mar 31, 2023 08:03AM

do...@gmail.com <do...@gmail.com> #46Mar 31, 2023 09:35AM

zh...@gmail.com <zh...@gmail.com> #47Mar 31, 2023 10:47AM

ch...@gmail.com <ch...@gmail.com> #48Apr 3, 2023 09:08AM

al...@ifit.com <al...@ifit.com> #49Apr 4, 2023 09:23PM

sh...@google.com <sh...@google.com> #50Apr 5, 2023 12:31AM

al...@ifit.com <al...@ifit.com> #51Apr 7, 2023 07:52PM

yo...@gmail.com <yo...@gmail.com> #52Apr 8, 2023 03:33AM

ma...@gmail.com <ma...@gmail.com> #53Apr 9, 2023 11:33PM

ma...@gmail.com <ma...@gmail.com> #54Apr 9, 2023 11:35PM

ma...@gmail.com <ma...@gmail.com> #55Apr 9, 2023 11:37PM

zh...@gmail.com <zh...@gmail.com> #56Apr 12, 2023 03:34AM

[Deleted User] <[Deleted User]> #57Apr 13, 2023 12:39AM

al...@ifit.com <al...@ifit.com> #58May 11, 2023 09:59PM

sh...@google.com <sh...@google.com> #59May 13, 2023 03:55AM

al...@ifit.com <al...@ifit.com> #60May 16, 2023 09:55PM

sh...@google.com <sh...@google.com> May 16, 2023 09:57PM

al...@ifit.com <al...@ifit.com> #61May 17, 2023 09:48PM

sh...@google.com <sh...@google.com> #62May 17, 2023 09:55PM

al...@ifit.com <al...@ifit.com> #63May 17, 2023 10:11PM

ki...@gmail.com <ki...@gmail.com> #64May 21, 2023 09:17AM

ra...@gmail.com <ra...@gmail.com> #65May 24, 2023 04:17PM

Explanation from ChatGPT:

jq...@gmail.com <jq...@gmail.com> #66May 30, 2023 02:43PM

da...@gmail.com <da...@gmail.com> #67Jun 1, 2023 09:49AM

de...@gmail.com <de...@gmail.com> #68Jun 1, 2023 11:48PM

ol...@gmail.com <ol...@gmail.com> #69Jul 11, 2023 03:45AM

th...@gmail.com <th...@gmail.com> #70Jul 19, 2023 11:10AM

va...@hotmail.com <va...@hotmail.com> Jul 24, 2023 03:10PM

sc...@gmail.com <sc...@gmail.com> #71Jul 25, 2023 05:36AM

ja...@gmail.com <ja...@gmail.com> #72Aug 8, 2023 06:31AM