Closed AlexeyRybakov closed 1 year ago
In our case, the test does not fail, but it takes longer
In our case, the test does not fail, but it takes longer
You are right. But it could fail if you enable an AdbServer, than it will try to close a keyboard by a back action. The test would fail if you check that the keyboard is present.
Describe the bug
Kaspresso recognizes SoftKeyboard as a SystemDialog and tries to close it.
To Reproduce Steps to reproduce the behavior:
Expected behavior The SoftKeyboard should not trigger suspending of SystemDialogs.
Smartphone (please complete the following information):
Additional context It seems like the problem in this line: https://github.com/KasperskyLab/Kaspresso/blob/56067aab6410ce9b9492e5e0385b94a93346f34e/kaspresso/src/main/kotlin/com/kaspersky/kaspresso/systemsafety/SystemDialogSafetyProviderImpl.kt#L109 Where SoftKeyboard package is
com.google.android.inputmethod.latin
Code to reproduce:
Activity:
Logs: