Event forwarding did not work for same emulators
See original GitHub issueEnv Info
- OS: MacOS 10.15.5
- kotlinc version: 1.3.72
- adb version: 30.0.3
- Emulator 1: Pixel 3 API 30 - Google Play
- Emulator 2: Pixel 3 API 30 - Google Play
Issue
Used command in the readme to run on emulators, however it did not forward the touch events.
Command Used
adb -s emulator-5554 shell getevent | ./adb-event-mirror.main.kts emulator-5556 --debug
Debug Log
Screen capture
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Android Emulator not able to receive data from socket but ...
Case 1 . when I run it using emulator I get the following IP 10.0.2.15. Result of ifconfig is same as well generic_x86:/...
Read more >Is it possible to connect to Android emulators running on a ...
If you have enabled Remote Login on the Mac, then you can use ssh port forwarding to connect to the emulator. Install an...
Read more >Emulator release notes - Android Developers
This update includes the following fix: Windows: Fixed an issue where the virtual scene camera and webcam would not work on the emulator....
Read more >Testing apps locally with the emulator | Cloud Pub/Sub ...
To develop and test your application locally, you can use the Pub/Sub emulator, which provides local emulation of the production Pub/Sub service. You...
Read more >android emulator does not work on windows 11 (if we use ...
Google, any updates on this issue from your side? Can you apply the same fix and ship it through Android Studio?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
And in case I’m dumb and don’t spot the problem again tomorrow:
The problem is we’re comparing “event10” and “event8” lexicographically which means “event10” incorrectly sorts lower than “event8” but we want the lowest numeric value, not which sorts lowest in string form.
Ok I have the fix, but I’m going to try to land testing first so I can script up a bunch of test cases to prevent regression.