-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
appWorkingDir fails for shortcut #117
Comments
Please provide the full server log |
appium-server-logs.txt |
I'd say WAD does not support providing aliases as |
Damn! Close the thread, if no more suggestions. |
Isn't it possible to figure out what app path the alias is pointing to from the client code before creating the session? Something like https://stackoverflow.com/questions/39309779/how-to-get-full-target-string-from-shortcut-lnk |
As for a possible solution, I have implemented shortcut's target field's value grabber using command line tools:
where "type" - displays the contents of a text file, "find" - searches for a string of text in a file or files. After grabbing I provide "app" property with a necessary app's version of exe-file. |
Hi!
Test run fails with message:
when synergy of arguments "appWorkingDir" & "app" are used for launching application via its shortcut. For instance:
Launching the test with only property "app" is fine for shortcuts. However, the app uses a certificate, what it searches for in app's directory. That's why I need property "appWorkingDir" to work with shortcuts too (it's fine with app: '*.exe').
Immediate answer regarding *.exe:
Path to direct .exe fail I cannot use, because its name changes constantly.
The second reason is that specific flag = "appArguments" is specified in shortcut.
There is no flag for the application to specify a path to the necessary certificate.
Any help/solution?
The text was updated successfully, but these errors were encountered: