They work in conjunction with the underlying graphical system that provides required functionality-support for graphics hardware, pointing devices, and a keyboard-and are often written and created using a widget toolkit.įew window managers are designed with a clear distinction between the windowing system and the window manager. Most window managers are designed to help provide a desktop environment. Under Wayland clients always draw their own window decorations.Ī window manager is system software that controls the placement and appearance of windows within a windowing system in a graphical user interface. This likely leaves the user stuck on the splash screen until they force close the app.Under X11, when the window manager is not running, the window decorations are missing for most windows.

Judging from telemetry, it appears to be happening at the time of calling SplashScreen.hide() within the react native part of the app. invoke Method.javaĬom.Zygote$n Zygote.java:240Ĭom.ZygoteInit.main ZygoteInit.java:845 splashscreen.SplashScreen$2.run SplashScreen.java:66Īndroid.os.Handler.handleCallback Handler.java:869Īndroid.os.Handler.dispatchMessage Handler.java:101Ī ActivityThread.java:6735 : not attached to window managerĪ WindowManagerGlobal.java:509Ī WindowManagerGlobal.java:399Ī WindowManagerImpl.java:123Ī Dialog.java:381Ī Dialog.java:360 I’m seeing something similar in my production crash reports from time to time. Handler.java:95 android.os.Handler.dispatchMessageĪctivityThread.java:7331 Handler.java:739 android.os.Handler.handleCallback SplashScreen.java:58 .splashscreen.SplashScreen$2.run WindowManagerImpl.java:140 ĭialog.java:701 ĭialog.java:684 From time to time I get the following error in our logs: View=.PhoneWindow$DecorView not attached to window manager

Window manager in android