-
Notifications
You must be signed in to change notification settings - Fork 572
ci: find a way to make it work #1177
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
Conversation
|
@KazuCocoa maybe try the same workaround as in appium/appium#21636 ? |
|
Could be, but then this means we may need to put the workaround in our troubleshooting documentation since this behavior possibly widely occur |
|
Ok, I see the reason. The "symlink" to the global e.g. install xcuitest first, then uia2. Then, symlink to So, if the environment installs xcuitest driver as "last" installed appium module, it should not have this import error. I haven't read Appium code. I'll take a look tonight |
|
(I expected the symlink to be kept for each node_modules) |
|
Thanks for checking it @KazuCocoa This looks really weird to me, perhaps some npm wizardry happens that we don't understand? The code to create symlink is located in https://github.com/appium/appium/blob/d12a6a53cf06a30b450c67b829efde15b2f89ee1/packages/appium/lib/cli/extension-command.js#L459 |
|
I've created appium/appium#21664 |
https://github.com/appium/python-client/actions/runs/18627636752/job/53107861784 but, for example https://github.com/appium/java-client/actions/runs/18460537702/job/52590775529 worked. (both had newer than appium/appium-xcuitest-driver#2637 change)
I wondered what was wrong with this GitHub Actions. Current way is installing appium related things via
runthough. Some deps might be weird?https://github.com/appium/ruby_lib_core/actions/runs/18627784681/job/53108204968 is also had the same error.