
While debugging various session tests failure I found that sometimes this list was empty (e.g. when a controller had failed to connect, or hadn't finished connecting yet) - resulting in these methods being silent no-ops. I think it's basically never expected for there to be no controllers connected when these methods are invoked, so this logs at ERROR level to give a clue of what happened when looking at the test logcat. PiperOrigin-RevId: 564750969
Session test module
Tests cross-process use of the session module. To run the tests:
- Prepare a device (either an emulator or a real device) to run the tests on.
- Run
./gradlew :test-session-current:cAT