We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I haven't tested anything yet but it looks like no big breaking changes in the release notes yet. We could do some testing in beta 1 or around, but beta 3 would be nice as https://developer.android.com/about/versions/15/overview#platform_stability
Review test note:
appium/ruby_lib_core#535
Curren preview is handled as 14. This is expected since older version also so. Maybe beta will have proper one.
[ADB] Current device property 'ro.build.version.release': 14
In an early device case, it is handled as sdk level 14.
Currently we may need to take a look location service
ERROR AppiumLibCoreTest::WebDriver::DeviceTest#test_location (205.82s) Minitest::UnexpectedError: Selenium::WebDriver::Error::UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: 'Command '/Users/kazu/Library/Android/sdk/platform-tools/adb -P 5037 -s <device> shell am start-foreground-service -e longitude 100 -e latitude 100 -e altitude 75 io.appium.settings/.LocationService' exited with code 255'; Command output: Error: Not found; no service started. UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: 'Command '/Users/kazu/Library/Android/sdk/platform-tools/adb -P 5037 -s <device> shell am start-foreground-service -e longitude 100 -e latitude 100 -e altitude 75 io.appium.settings/.LocationService' exited with code 255'; Command output: Error: Not found; no service started. at getResponseForW3CError (/Users/kazu/.nvm/versions/node/v16.15.1/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/errors.js:1118:9) at asyncHandler (/Users/kazu/.nvm/versions/node/v16.15.1/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:491:57) /Users/kazu/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/selenium-webdriver-4.18.1/lib/selenium/webdriver/remote/response.rb:55:in `assert_ok' /Users/kazu/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/selenium-webdriver-4.18.1/lib/selenium/webdriver/remote/response.rb:34:in `initialize' /Users/kazu/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/selenium-webdriver-4.18.1/lib/selenium/webdriver/remote/http/common.rb:83:in `new' /Users/kazu/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/selenium-webdriver-4.18.1/lib/selenium/webdriver/remote/http/common.rb:83:in `create_response' /Users/kazu/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/selenium-webdriver-4.18.1/lib/selenium/webdriver/remote/http/default.rb:103:in `request' lib/appium_lib_core/common/base/http_default.rb:66:in `request' /Users/kazu/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/selenium-webdriver-4.18.1/lib/selenium/webdriver/remote/http/common.rb:59:in `call' /Users/kazu/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/selenium-webdriver-4.18.1/lib/selenium/webdriver/remote/bridge.rb:607:in `execute' lib/appium_lib_core/common/base/bridge.rb:303:in `set_location' lib/appium_lib_core/common/base/has_location.rb:47:in `location=' lib/appium_lib_core/common/base/has_location.rb:67:in `set_location' test/functional/android/webdriver/device_test.rb:63:in `test_location'
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I haven't tested anything yet but it looks like no big breaking changes in the release notes yet. We could do some testing in beta 1 or around, but beta 3 would be nice as https://developer.android.com/about/versions/15/overview#platform_stability
Review test note:
appium/ruby_lib_core#535
Curren preview is handled as 14. This is expected since older version also so. Maybe beta will have proper one.
In an early device case, it is handled as sdk level 14.
Currently we may need to take a look location service
The text was updated successfully, but these errors were encountered: