[AS + Wear emulators] Device Manager doesn't remember pairing until devices started [291704385]

Fixed

Bug

Status Update

No update yet.

Description

ys...@google.com

created issue #1

Jul 18, 2023 08:22AM

1. Describe the bug or issue that you're seeing.

When using multiple paired emulators, knowing which devices are paired is useful for starting the right ones.  Unfortunately the recent changes in Device Manager seem to make it only discover that after launching *both* emulators.

2. If you know what they are, write the steps to reproduce:

   3A. See screenshot with wear emulator running, no paired icons next to API 33.
   3B. See screenshot with both emulators running, paired icons next to API 33
   3C. After Stopping device, pairing is still remembered.



Build: AI-231.9161.38.2311.10457801, 202307071931

AI-231.9161.38.2311.10457801, JRE 17.0.7+0-17.0.7b829.16-10353782x64 JetBrains s.r.o., OS Linux(amd64) v6.1.25-1rodete1-amd64, screens 3840.0x2160.0, 2560.0x1440.0

AS: Hedgehog | 2023.1.1 Canary 12
Kotlin plugin: 231-1.8.21-release-380-AS9161.38.2311.10457801
Android Gradle Plugin: 8.0.2
Gradle: 8.2.1
Gradle JDK: JetBrains Runtime version 17.0.7
NDK: from local.properties: (not specified), latest from SDK: 25.2.9519653
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)

DiagnosticsReport20230718-091822.zip

1.6 MB

Download

Tue Jul 18 2023 09:19:36 GMT+0100 (British Summer Time).png

73 KB

View

Download

Tue Jul 18 2023 09:20:07 GMT+0100 (British Summer Time).png

80 KB

View

Download

Comments

lu...@google.com <lu...@google.com> Jul 18, 2023 09:18AM

Assigned to an...@google.com.

jb...@google.com <jb...@google.com> Jul 18, 2023 08:40PM

Status: New

ys...@google.com <ys...@google.com> Jul 20, 2023 04:18PM

Assigned to di...@google.com.

di...@google.com <di...@google.com> #2Jul 21, 2023 12:51PM

It doesn't reproduce for me in Canary 13. Yuri, would you mind attaching the settings file for this so I can check if it's corrupted? The settings file is named wearPairing.xml and should be somewhere in /usr/local/google/home/<username>/.config/Google/AndroidStudio2023.1

di...@google.com <di...@google.com> #3Jul 27, 2023 03:42PM

Reassigned to ro...@google.com.

Never mind, I managed to reproduce it consistently. It seems like a race condition in the initialization of the Device Manager, maybe related to http://ag/22397223

James, it seems like the flow might be missing the initial state of pairing?

di...@google.com <di...@google.com> Jul 31, 2023 03:07PM

Marked as fixed.

ro...@google.com <ro...@google.com> #4Aug 1, 2023 09:17PM

Fix is in ag/24229062

an...@google.com <an...@google.com> #5Sep 6, 2023 09:33PM

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

Android Studio Hedgehog | 2023.1.1 Beta 2
Android Gradle Plugin 8.2.0-beta02

We encourage you to try the latest update.

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

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

Issue 291704385

Description

Issue summary

Comments

lu...@google.com <lu...@google.com> Jul 18, 2023 09:18AM

jb...@google.com <jb...@google.com> Jul 18, 2023 08:40PM

ys...@google.com <ys...@google.com> Jul 20, 2023 04:18PM

di...@google.com <di...@google.com> #2Jul 21, 2023 12:51PM

di...@google.com <di...@google.com> #3Jul 27, 2023 03:42PM

di...@google.com <di...@google.com> Jul 31, 2023 03:07PM

ro...@google.com <ro...@google.com> #4Aug 1, 2023 09:17PM

an...@google.com <an...@google.com> #5Sep 6, 2023 09:33PM

Add comment

Issue metadata