If returned the WindowManagerGlobal.ADD_BAD_APP_TOKEN, the exception occurs when the WMS.addWindow () function is called to check whether the window to be added is not in violation of the policy according to the android window policy.

Return WindowManagerGlobal.ADD_BAD_APP_TOKEN This ensures secure interaction between the application and the window manager (by making it impossible to add windows on top of other applications), and also makes it easy for the activity manager to make direct requests to the window manager.Īnd the code that throws “BadTokenException”

The activity manager gives this token to both the (*application) and the window manager, and it sends the token to the window manager each time it wants to add a new window to the screen. When an application starts up for the first time, the ActivityManagerService creates a special kind of window token called an application window token, which uniquely identifies the application’s top-level container window. Without window tokens, this necessary identification step wouldn’t be possible and the window manager wouldn’t be able to protect itself from malicious applications. If the tokens don’t match, the window manager rejects the request and throws a BadTokenException. The window manager protects against this by requiring applications to pass their application’s window token as part of each request to add or remove a window. Window tokens are important for security reasons because they make it impossible for malicious applications to draw on top of the windows of other applications. WindowManagerService (WMS) is a system service that manages the windows on Android.Īs the name suggest, a window token is a special type of Binder token used by window manager to uniquely identify a window in the system.

Android windowmanager layoutparams