Jonathan Lipps
Jonathan Lipps
That's correct. automationName is a session capability, not related to the server.
i don't think Sauce can have any stance on 'official' names for env vars. but i agree that the various clients should endeavor to use the same thing to avoid...
fair enough. i think the sauce docs should always use 1 style as an example, and have all the clients support all 4 styles.
I'm not sure offhand. Can someone create an issue with repro steps at the Appium repo?
(a) I don't have access to that repo, (b) it would be nice to have it written up as a bug report since I probably won't have time to do...
I wonder if we should add something like a `--ext-search-root` flag where you could simply tell Appium the directory to start its hunt for extension packages. That way you could...
Yes, fair point. I think what I meant was to use an approach like you do here, but instead of relying on `process.cwd()`, allowing the user to specify a path.
In this case, _all_ of the listed handlers are executed. It's done as a nested stack based on when each plugin calls `await next()`. There's no guarantee that plugins will...
Disabling all plugins except device farm is not enough to help us figure out whether the problem is in the Appium driver or in something the device farm plugin is...
Yes, I agree, let's make `appium@beta` point to latest 2.0 release as well. We can probably update references to `next` in the docs with a quick find/replace too.