appium: ECCONNRESET error after adb shell dumpsys battery unplug

The problem

I was trying to get Android into doze mode, then wake it up again and verify if it had any new notifications.

Environment

Appium version: 1.8.2-beta OS : macOS High Sierra Node version : 10.8.0 Devices: Android both 7.0 and 8.0, real devices

Details

The commands that I used are on appium logs. Also I do have some sleeps between adb commands and the steps(go into doze mode, wake up, check notification), which didn’t help at all. Also i found that when i called openNotifications() an error 500 was returned (not always is, but this time was)

Link to Appium logs

https://gist.github.com/notihs/0f91d95af61a5ccd9d39c7c82d1e9f2c

Code To Reproduce Issue [ Good To Have ]

There’s not much to it, so I think that this isn’t necessary. Basically just running some commands (visible on appium logs) and then calling openNotifications() on an AndroidDriver object

[EDIT] Using 1.11.0-beta.2 this is not reproducible anymore

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 19

Most upvoted comments

Like I said you are free to modify the server for your local needs. It is impossible to cover and predict all possible cases here, so I would rather keep everything as is for now.