UI Automator Viewer 的 GUI 损坏

Question

The problem

The whole GUI is broken. No messages, no texts in the buttons, weird symbols, etc.
I think it might be the SWT (see image) .

Environment

• Desktop OS: macOS Catalina 10.15.4 (19E287)

• Mobile platform/version under test: Android

• Real device or emulator/simulator: Emulated device via Android Studio QEMU

• Java: Installed Java with brew.

  openjdk version "1.8.0_252"
  OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_252-b09)
  OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.252-b09, mixed mode)

• Android Studio Installed from official webpage.

  Android Studio 4.0
  Build #AI-193.6911.18.40.6514223, built on May 20, 2020
  Runtime version: 1.8.0_242-release-1644-b3-6222593 x86_64
  VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
  macOS 10.15.4
  GC: ParNew, ConcurrentMarkSweep
  Memory: 1237M
  Cores: 12
  Registry: ide.new.welcome.screen.force=true
  Non-Bundled Plugins:

Steps to reproduce

1. Install Java 8
2. Install Android Studio
3. Install Intel HAXM
4. Run from terminal uiautomatorviewer or /Users/user/Library/Android/sdk/tools/bin/uiautomatorviewer

Enviroment variables

export JAVA_HOME_8=$(/usr/libexec/java_home -v 1.8)

export JAVA_HOME=$JAVA_HOME_8
export PATH=$PATH:$JAVA_HOME/bin

export M2_HOME=/opt/apache-maven-3.6.3
export PATH=$PATH:$M2_HOME/bin

export ANDROID_HOME=/Users/user/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/build-tools
export PATH=$PATH:$ANDROID_HOME/platform-tools
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin

Maybe I'm missing something. Also, if logs are needed please tell me.
Thanks

Answer 1

If you are using dark mode, can you try switching your macOS theme to light mode? I got a Java update dialog which looked similar to your screenshot. I realized the texts were there but they were white and couldn't be seen over a white window background. I realized this when I clicked on a button.

Answer 2

You must change to Light mode appearance in your Mac setting

Answer 3

I had the same problem. I was able to fix it by switching from adoptopenjdk to using Java 1.8.0_231. Could be that the problem is the different GUI they use in adoptopenjdk vs oracle. From adoptopenjdk FAQ "For JDK8, AdoptOpenJDK is using an open-source renderer called Pisces. " Hope that helps.