AppiumTestDistribution / appium-device-farm

This is an Appium 2.0 plugin designed to manage and create driver sessions on available devices.
https://devicefarm.org
Apache License 2.0
292 stars 90 forks source link

UnhandledRejection: { modelName: 'Session', cause: 'Record to update not found.' } #1191

Closed Muratoi closed 1 week ago

Muratoi commented 2 weeks ago

Describe the bug

Session stucked on node, because of UnhandledRejection

Link to Appium logs

Create a GIST https://gist.github.com/Muratoi/24d472c9ae86387e3cb208db43ee9f7c

Environment

  1. Appium version (or git revision) that exhibits the issue: 2.5.4
  2. Last Appium version that did not exhibit the issue (if applicable):
  3. Node.js version (unless using Appium.app|exe): v16.16.0
  4. Npm or Yarn package manager: 8.11.0
  5. Mobile platform/version under test: Android
  6. Real device or emulator/simulator: Emulator
  7. Appium CLI or Appium.app|exe: CLI
saikrishna321 commented 2 weeks ago

@Muratoi what is the version of the device-farm ur using ?

Muratoi commented 2 weeks ago

@saikrishna321 latest device-farm@8.4.7-rc.41

saikrishna321 commented 2 weeks ago

@Muratoi Are you using any setSessionName? Is this error happening all the time?

Muratoi commented 2 weeks ago

@saikrishna321 No, it’s automatically provided by Appium session_id, and that’s problem only happen when tests runs on node side, in hub everything is okay, and I guess it should be noted: in dashboard in last activity I can’t see stop screen recording activity, as it should be, so maybe problem happen here

Muratoi commented 2 weeks ago

And I forget to mention, if I set df:skipReport as True, problem doesn't appear, it’s cause definitely because of dashboard

saikrishna321 commented 2 weeks ago

@Muratoi can u try with latest version rc42

Muratoi commented 2 weeks ago

Looks fixed, thank you! @saikrishna321

saikrishna321 commented 2 weeks ago

I see some areas to improve this error. Will make fixes in next release

Muratoi commented 2 weeks ago

@saikrishna321 Sorry, i was wrong about that error still exist

Muratoi commented 2 weeks ago

checked on 8.4.7-rc.43, is something that i can do for now?

SrinivasanTarget commented 1 week ago

@Muratoi will be fixed on #1194

sudharsan-selvaraj commented 1 week ago

@Muratoi Try with 8.4.7-rc.45.