-
Notifications
You must be signed in to change notification settings - Fork 11
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
The default element-wait retry do not override when trying to update from code #112
Comments
Please provide full logs |
Please find the attached log https://gist.github.com/dipakkumar1225/a1bda54988dd57c154b37b9b0dd3ae6a |
@dipakkumar1225 what is the output of |
|
@dipakkumar1225 I'm unable to reproduce the issue
|
On my end, I am still encountering the issue. I've attached a sample source link for reference: https://github.com/dipakkumar1225/Appium2.0Plugin.git. Could you please review and identify any mistakes I might be making? In the meantime, I'd like to share my observation: When running from the CLI, I use the --node option as: appium --base-path="/wd/hub/" --allow-insecure="adb_shell" --relaxed-security --session-override --use-drivers="UiAutomator2" --use-plugins="images, element-wait, appium-dashboard" --config "%cd%\config\serverconfig.json" However, in code, GeneralServerFlag.CONFIGURATION_FILE which corresponds to the --nodeconfig option. |
@saikrishna321 , any update on this appium --base-path="/wd/hub/" --allow-insecure="adb_shell" --relaxed-security --session-override --use-drivers="UiAutomator2" --use-plugins="images, element-wait, appium-dashboard" --config "%cd%\config\serverconfig.json" However, in code, GeneralServerFlag.CONFIGURATION_FILE which corresponds to the --nodeconfig option. |
@dipakkumar1225 Everything works fine with your given example.
You need to load the config like this
|
Thank You @saikrishna321, After loading the config file as you suggested, it began to function correctly.
However, I have a concern. If I need to override the timeout for a specific element that takes longer than the timeout defined in serverconfig.json, would the following approach be appropriate? If not, could you please provide guidance?
|
@dipakkumar1225 Yes this would work. |
The default element-wait retry do not override when I am trying to update from code:
{
address: '0.0.0.0',
allowCors: false,
basePath: '',
callbackPort: 4723,
debugLogSpacing: false,
keepAliveTimeout: 600,
localTimezone: false,
loglevel: 'debug',
logNoColors: false,
logTimestamp: false,
longStacktrace: false,
noPermsCheck: false,
port: 4723,
relaxedSecurityEnabled: false,
sessionOverride: false,
strictCaps: false
}
(no configuration file loaded)
via CLI or function call:
{
address: '127.0.0.1',
allowInsecure: [ 'adb_shell' ],
basePath: '/wd/hub/',
loglevel: 'info:debug',
relaxedSecurityEnabled: true,
sessionOverride: true,
useDrivers: [ 'UiAutomator2' ],
usePlugins: [ 'element-wait', 'gestures', 'appium-dashboard' ]
}
final configuration:
{
address: '127.0.0.1',
allowInsecure: [ 'adb_shell' ],
basePath: '/wd/hub/',
logFile: 'D:\Automation-Framework\Generic\Logs\1',
loglevel: 'info:debug',
nodeconfig: { server: { plugin: [Object] } },
port: 4723,
relaxedSecurityEnabled: true,
sessionOverride: true,
useDrivers: [ 'UiAutomator2' ],
usePlugins: [ 'element-wait', 'gestures', 'appium-dashboard' ],
showConfig: true,
allowCors: false,
callbackPort: 4723,
debugLogSpacing: false,
keepAliveTimeout: 600,
localTimezone: false,
logNoColors: false,
logTimestamp: false,
longStacktrace: false,
noPermsCheck: false,
strictCaps: false
}
The text was updated successfully, but these errors were encountered: