appium-boneyard/appium-android-bootstrap

Npm module for androidBootstrap, the java project which appium uses to interact with UiAutomator

appium-android-bootstrap's Issues

timeout unit default value is wrong in WaitForIdle.java

Code here: https://github.com/appium/appium-android-bootstrap/blob/master/bootstrap/src/io/appium/android/bootstrap/handler/WaitForIdle.java#L49
It used timeout=10 for default value.

Actually, UiDevice.waitForIdle(long timeout) with param in milliseconds: https://android.googlesource.com/platform/frameworks/testing/+/master/uiautomator/library/core-src/com/android/uiautomator/core/UiDevice.java#483

So maybe you the default value should be 10000

Issues changing the bootstrap

I have been compiling the bootstrap using mvn package -P 4.4. Then I put the jar in the jar directory for Appium.

When I run appium, it's behaviour doesn't change despite the modifications I have made.

Why doesn't it take it into consideration ?

An in-range update of appium-base-driver is breaking the build 🚨

Version 3.3.1 of appium-base-driver was just published.

Branch	Build failing 🚨
Dependency	appium-base-driver
Current Version	3.3.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

appium-base-driver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 2 commits.

• 54abe10 3.3.1
• 42f64a8 Get message for MJSONWP error (#241)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of appium-base-driver is breaking the build 🚨

Version 3.5.0 of appium-base-driver was just published.

Branch	Build failing 🚨
Dependency	appium-base-driver
Current Version	3.4.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

appium-base-driver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 4 commits.

• 46a78c9 3.5.0
• b161cb9 Tune arguments transformation for /timeouts API call (#248)
• b90ed15 fix raising NotYetImplementedError against commands which exist in image-element (#245)
• 4ed0c0b Add an optional parameter to /window call (#244)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

How to build AppiumBootstrap.jar

Hi all,

I tried to build AppiumBootstrap.jar by doing the steps as https://github.com/appium/appium-android-bootstrap/blob/master/bootstrap/README.md, and I got bootstrap-1.0.0-SNAPSHOT.jar.
I installed Appium by using AppiumForWindows_1_4_13_1.zip. And I renamed bootstrap-1.0.0-SNAPSHOT.jar to AppiumBootstrap.jar, ran Appium and has the error

info: [debug] spawning: C:\Users{Window user}\AppData\Local\Android\sdk\platform-tools\adb.exe -s 169.254.138.177:5555 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.microsoft.office.outlook -e disableAndroidWatchers false
info: [debug] [UIAUTOMATOR STDOUT] WARNING: linker:
info: [debug] [UIAUTOMATOR STDOUT] libdvm.so has text relocations. This is wasting memory and is a security risk. Please fix.
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_RESULT: shortMsg=java.lang.RuntimeException
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_RESULT: longMsg=Didn't find class "io.appium.android.bootstrap.Bootstrap" on path: DexPathList[[zip file "/system/framework/android.test.runner.jar", zip file "/system/framework/uiautomator.jar", zip file "/data/local/tmp/AppiumBootstrap.jar"],nativeLibraryDirectories=[/system/lib]]
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_CODE: 0
info: [debug] UiAutomator exited

Could you please help me the issue? How can I rebuild AppiumBootstrap.jar?

Thanks,
Ha

An in-range update of appium-adb is breaking the build 🚨

Version 6.16.0 of appium-adb was just published.

Branch	Build failing 🚨
Dependency	appium-adb
Current Version	6.15.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

appium-adb is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 2 commits.

• eab8074 6.16.0
• 624cb95 Add the troubleshooting link to the exception messages (#345)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of appium-base-driver is breaking the build 🚨

Version 2.32.0 of appium-base-driver was just published.

Branch	Build failing 🚨
Dependency	appium-base-driver
Current Version	2.31.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

appium-base-driver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 4 commits.

• ac5386d 2.32.0
• bd39876 Fix sending of commands by JWProxy class (#218)
• 8439803 Update dependencies to enable Greenkeeper 🌴 (#216)
• 72dd453 Enforce UTF-8 encoding on request headers (#214)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

1.5 Cleanup

• Make sure all deps are up to date (and there are no unused deps)
• Take a look at all TODOs to see if we need to resolve any for the release
• Set up code coverage
• Set up CI (unit tests, functional tests, code coverage; should be on all relevant platforms, and should include multi-executor parallelism for long-running testsuites)
• Ensure that we are using appium-support functions, not home-grown helpers
• Ensure that we have high unit test code coverage percentage
• Ensure that we have sufficient/appropriate functional test coverage
• Write a decent README, explaining (a) what the purpose of the module is, (b) how it relates to other appium modules, and (c) how to use its interface
• Ensure that code conforms to our style
• Ensure we are not using any sync functions
• Ensure that code is well-commented

An in-range update of appium-support is breaking the build 🚨

Version 2.18.0 of appium-support was just published.

Branch	Build failing 🚨
Dependency	appium-support
Current Version	2.17.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

appium-support is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 4 commits.

• ba73a1b 2.18.0
• a3e9a6d Merge pull request #75 from appium/jlipps-mjpeg
• 0b69abc add mjpeg stream helper class
• 42a2ab3 2.17.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Failed to Dump Window Hierarchy

I am currently experiencing a lot of "Failed to Dump Window Hierarchy" Errors.

Example Request Response:

REQUEST
{"using":"xpath","value":"//*[@text='AppLock is running']"}
RESPONSE
{"status":13,"value":{"message":"An unknown server-side error occurred while processing the command.","origValue":"Failed to Dump Window Hierarchy"},"sessionId":"68ee59cb-e1c0-42d3-b1c7-12081e877fbb"}

The issue seems to be a temporary one as the test afterwards continues properly (e.g. i am always dumping the page source and a screenshot after a failure)

Any ideas why this happens?

Appium Version is 1.3.4

An in-range update of appium-support is breaking the build 🚨

Version 2.19.0 of appium-support was just published.

Branch	Build failing 🚨
Dependency	appium-support
Current Version	2.18.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

appium-support is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 3 commits.

• b2dadcc 2.19.0
• 86965ef Merge pull request #77 from appium/jlipps-jimp
• d469a3c use appium-support jimp helper

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Bootstrap hangs for ~10 seconds

The BOOTSTRAP hangs sometimes for ~10 seconds while searching elements.
See bold time-stamps below.

Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d) - on windows
Android 5.1.1 (with real device)

I have done plenty of tests with Android v4.4 & 5.0 devices and I haven't seen this happening with them.
Any ideas how to troubleshoot further?

2016-08-31 15:02:10:322 - info: --> POST /wd/hub/session/11265439-6cd8-4d8c-a8c4-1041f140058b/elements {"using":"id","sessionId":"11265439-6cd8-4d8c-a8c4-1041f140058b","value":"com.android.incallui:id/name"}
2016-08-31 15:02:10:322 - info: [debug] Waiting up to 0ms for condition
2016-08-31 15:02:10:322 - info: [debug] Pushing command to appium work queue: ["find",{"strategy":"id","selector":"com.android.incallui:id/name","context":"","multiple":true}]
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"find","params":{"strategy":"id","selector":"com.android.incallui:id/name","context":"","multiple":true}}
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] Got command action: find
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] Finding com.android.incallui:id/name using ID with the contextId:  multiple: true
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] Using: UiSelector[RESOURCE_ID=com.android.incallui:id/name]
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] getElements selector:UiSelector[RESOURCE_ID=com.android.incallui:id/name]
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] Element[] is null: (0)
2016-08-31 15:02:10:322 - info: [debug] [BOOTSTRAP] [debug] getElements tmp selector:UiSelector[INSTANCE=0, RESOURCE_ID=com.android.incallui:id/name]
2016-08-31 15:02:20:715 - info: [debug] [BOOTSTRAP] [debug] Failed to locate element. Clearing Accessibility cache and retrying.
2016-08-31 15:02:20:715 - info: [debug] [BOOTSTRAP] [debug] Finding com.android.incallui:id/name using ID with the contextId:  multiple: true
2016-08-31 15:02:20:715 - info: [debug] [BOOTSTRAP] [debug] Using: UiSelector[RESOURCE_ID=com.android.incallui:id/name]
2016-08-31 15:02:20:715 - info: [debug] [BOOTSTRAP] [debug] getElements selector:UiSelector[RESOURCE_ID=com.android.incallui:id/name]
2016-08-31 15:02:20:715 - info: [debug] [BOOTSTRAP] [debug] Element[] is null: (0)
2016-08-31 15:02:20:715 - info: [debug] [BOOTSTRAP] [debug] getElements tmp selector:UiSelector[INSTANCE=0, RESOURCE_ID=com.android.incallui:id/name]
2016-08-31 15:02:30:855 - info: [debug] [BOOTSTRAP] [debug] Element[] is null: (1)
2016-08-31 15:02:30:856 - info: [debug] [BOOTSTRAP] [debug] getElements tmp selector:UiSelector[INSTANCE=1, RESOURCE_ID=com.android.incallui:id/name]
2016-08-31 15:02:40:906 - info: [debug] [BOOTSTRAP] [debug] Returning result: {"status":0,"value":[{"ELEMENT":"1"}]}
2016-08-31 15:02:40:906 - info: [debug] Responding to client with success: {"status":0,"value":[{"ELEMENT":"1"}],"sessionId":"11265439-6cd8-4d8c-a8c4-1041f140058b"}
2016-08-31 15:02:40:925 - info: <-- POST /wd/hub/session/11265439-6cd8-4d8c-a8c4-1041f140058b/elements 200 30599.140 ms - 89 {"status":0,"value":[{"ELEMENT":"1"}],"sessionId":"11265439-6cd8-4d8c-a8c4-1041f140058b"}

UiScrollableParser.coerceArgToType lacks support for type double

We're trying to use setSwipeDeadZonePercentage(double percentage) to be able to use a partially obscured UiScrollView.

This method takes a double between 0 and 1 as its argument. When passing i.e. 0.2, AndroidBootstrap logs:

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] UiScrollable coerce type: double arg: 0.2
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {"status":9,"value":"Could not parse UiSelector argument: Could not coerce 0.2 to any sort of Type"}

Doc: https://developer.android.com/reference/android/support/test/uiautomator/UiScrollable.html#setSwipeDeadZonePercentage(double)

Possible optimization for getting page source

I was looking through this code today and noticed that whenever I send a command to get the page source, bootstrap will:

1. Dump the UI XML into a on-device temp file
2. Read it back into a string
3. Do some cleanup on the string
4. ... and then pass it back in a JSON response

And this is all done on-device in bootstrap.

Can't the XML be passed back as a string and skip to step 3?