Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to give an existing SessionID when an object is instantiated so that it will not apply for a new SessionID? #837

Open
suzhenyu006 opened this issue Mar 8, 2023 · 1 comment

Comments

@suzhenyu006
Copy link

The problem

I have a test scenario. I need to use Java and Python to test appium on a device. Java has applied for a SessionID, and Python cannot apply again, but Python does not apply for a SessionID and cannot get a driver object

Environment

  • Appium version (or git revision) that exhibits the issue:
  • Last Appium version that did not exhibit the issue (if applicable):
  • Desktop OS/version used to run Appium:
  • Node.js version (unless using Appium.app|exe):
  • Mobile platform/version under test:
  • Real device or emulator/simulator:
  • Appium CLI or Appium.app|exe:

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium Logs

Code To reproduce issue

self.c = webdriver.Remote(command_executor = self.adb_remote_url + "/wd/hub", desired_capabilities=self.desired_caps)
self.c.session_id = self.session_id

@KazuCocoa
Copy link
Member

Perhaps this lib does not have the ability if the base selenium client did not have the feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants