You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WD is generating calls without the session ID so we are receiving 404 no route found on every configuration tested.
Environment
Appium version (or git revision) that exhibits the issue: 1.22
WD version: 1.14
Desktop OS/version used to run Appium: Azure Devops Hosted MacOs-11
Npm or Yarn package manager: npm
Mobile platform/version under test: android api 27
Real device or emulator/simulator: emulator
Details
The problem here is that the same configuration is working on a local machine whilst it doesn't on the Azure Devops Hosted MacOs-11. I opened a bug on appium cause we thought that the problem would be something related to them but appium is working as intended.
As you can see in the image above, the route that sends the message is not formed correctly, its's missing the session Id. Is there anything we can do to include there the session id?
The problem
WD is generating calls without the session ID so we are receiving 404 no route found on every configuration tested.
Environment
Appium version (or git revision) that exhibits the issue: 1.22
WD version: 1.14
Desktop OS/version used to run Appium: Azure Devops Hosted MacOs-11
Npm or Yarn package manager: npm
Mobile platform/version under test: android api 27
Real device or emulator/simulator: emulator
Details
The problem here is that the same configuration is working on a local machine whilst it doesn't on the Azure Devops Hosted MacOs-11. I opened a bug on appium cause we thought that the problem would be something related to them but appium is working as intended.
As you can see in the image above, the route that sends the message is not formed correctly, its's missing the session Id. Is there anything we can do to include there the session id?
Link to logs
https://gist.github.com/jose-larrubia-savia/753937f738f54df2b8e520a2c5c4e548
Code Sample
The text was updated successfully, but these errors were encountered: