-
-
Notifications
You must be signed in to change notification settings - Fork 518
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
Init AppiumDriver error when i update serenity to new version 4.2.0 #3512
Comments
This might be the root issue: "Illegal key values seen in w3c capabilities: [app, appActivity, appPackage, autoGrantPermissions, automationName, flutterElementWaitTimeout, flutterEnableMockCamera, fullReset, hub, newCommandTimeout, platformVersion]" |
Hi @wakaleo . When i using version 3.6.22 or 4.1.20 of serenity. This error not happen |
4.2.0 uses the later version of Selenium and the Appium client - there may be upgrades in your config that you need to do related to these new versions. (There are no code changes in Serenity between 4.1.20 and 4.2.0, just library updates) |
Yes. When i use my custom driver. It works ok. But if i using webdriver.driver = appium, it had error. |
I have the same error, I'm using a serenity.properties file.. |
It is better to use the serenity.conf file, but that looks like a w3c config issue - maybe check the Appium docs |
OK, I got it. However, with the next configuration in the serenity.properties file:
And build.gradle file:
It works !!, any problems.. But, if I update the dependencies, for example: serenity_version = '4.2.0' Not works, I see the error :
I can't to update the dependencies version.... What can happened here ???? :-( |
I suspect Selenium or Appium may be stricter in the w3C standards in the latest versions. Try with serenity.conf instead of serenity.properties. Check the w3C documentation to make sure all the options you have configured are legal. Have a look at the driver creation logic to see what is being passed through to Appium (this hasn't changed in Serenity so I suspect Appium or Selenium are more strict now). |
I have made the change by adding the serenity.conf file, however, I continue to have exactly the same problem. I have deleted the serenity.properties file. serenity.conf
build.gradle:
|
@maalben
All capabilities with prefix
But probably the same can be done in serenity.conf:
|
Hello @janmekota !!! I have a question, the capabilities in java properties works ? And your answer is true, yoo could share a example how you implements it ?, with the last version appium and serenity... Thanks in advanced ... |
I am unfamiliar with serenity.properties:
There are some properties, which may not be necessary in your case. |
What happened?
I see error
What did you expect to happen?
No response
Serenity BDD version
4.2.0
JDK version
openjdk version "17.0.7" 2023-04-18 LTS OpenJDK Runtime Environment Corretto-17.0.7.7.1 (build 17.0.7+7-LTS) OpenJDK 64-Bit Server VM Corretto-17.0.7.7.1 (build 17.0.7+7-LTS, mixed mode, sharing)
Execution environment
-MacOs 14.4
How to reproduce the bug.
AndroidDriver androidDriver() {
return (AndroidDriver)
((WebDriverFacade) getDriver()).getProxiedDriver();
}
How can we make it happen?
Work on this myself and propose a PR (with Serenity BDD team guidance)
The text was updated successfully, but these errors were encountered: