-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Cannot use extra CLI flags (sometimes required by plugins) #17084
Comments
@boneskull Has something changed with CLI args in latest beta? |
AFAIK it is necessary for a plugin/driver to provide a schema where supported CLI args are described. See https://github.com/appium/appium/pull/17050/files#diff-3baee5b43161e5ca3169450387053776d15111d589a22e656715c1ef103c5688R387 |
They do specify a schema, @mykola-mokhnach "appium": {
"pluginName": "device-farm",
"mainClass": "DevicePlugin",
"schema": {
"$schema": "http://json-schema.org/draft-07/schema",
"additionalProperties": false,
"description": "Appium configuration schema for the Device Farm plugin.",
"properties": {
"platform": {
"type": "string"
}
},
"title": "Fake Plugin Configuration",
"type": "object"
}
} Can we double check this is working for plugins? |
I do not observe any schema that describes CLI args. Nevertheless I might be wrong. |
this all looks correct except in the fake-driver example, |
xcuitest driver uses the same approach (schema inside package.json). Not sure which of these approaches is correct |
Server command:
Can't reproduce the error |
|
This sounds like it's been resolved, so I'll close it. |
@boneskull Can we load all the plugins CLI args from a file? Currently, the plugin device-farm has three CLI args and may to come.
|
Some plugins like device-farm make use of CLI arguments passed to Appium.
For example: there is the
plugin-device-farm-platform
argument, which can take valuesandroid
,ios
orboth
Since beta.26, you can specify the plugin to use, but you cannot specify any extra plugin arguments.
Without the argument, Appium runs but it is not properly configured:
With the argument, Appium will throw an error:
The text was updated successfully, but these errors were encountered: