-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Close keyboard if opened #66
Comments
We cannot call An (overengineered?) workaround could be running some second simple "maestro daemon" process on the host machine. Edit: After giving it some thought, I think that ExampleTake this code snippet: import 'package:maestro_test/maestro_test.dart';
Automator.init(verbose: true);
final automator = Automator.instance;
// ...
Automator.isKeyboardOpened() would make a HTTP request not to the connected Android device, but to the maestro daemon instead. Then the maestro deamon would be able to Pros:
Cons:
|
Another idea worth trying out: use |
We could see how Maestro by mobile.dev does this. See: |
We could differentiate between host services and local services (ADB does it). |
Important updateIn #593 we've got a powerful new capability of acting as a host. This means we're able to use Here's how Maestro does this – the |
We lost this feature in 1.0 :) |
Do you have any news about this please ? |
There's no easy way to do this using UiAutomator.
There's a hack though. An ugly one, but
it worksit works only through ADB.Here's the link
The text was updated successfully, but these errors were encountered: