I think in
https://github.com/appium/android-apidemos/blob/master/src/io/appium/android/apis/accessibility/AccessibilityNodeProviderActivity.java
you should use
if (virtualViewId == HOST_VIEW_ID) {
not
if (virtualViewId == View.NO_ID) {

Only by accident both are -1 and you code works.

This is quite strange. If com.example.android.apis is installed then the contents of io.appium.android.apis will change. There are more elements, some appear to be duplicated.

The work around is to run adb uninstall com.example.android.apis

In theory the new package name should isolate the app.

just pulled and built and using uiautomatorviewer there are no content descriptions anymore!

When the app first launches, I'm not seeing content descriptions on the elements. I checked the static layout with my content desc script and they're all set correctly. I think the issue is due to dynamic elements not having a content desc set by the text property for android.widget.TextView.

> page
get /source
TextView
  class: android.widget.TextView
  text: API Demos
TextView
  class: android.widget.TextView
  text: Accessibility
TextView
  class: android.widget.TextView
  text: Animation
TextView
  class: android.widget.TextView
  text: App
TextView
  class: android.widget.TextView
  text: Content
TextView
  class: android.widget.TextView
  text: Graphics
TextView
  class: android.widget.TextView
  text: Media
TextView
  class: android.widget.TextView
  text: NFC
TextView
  class: android.widget.TextView
  text: OS
TextView
  class: android.widget.TextView
  text: Preference
TextView
  class: android.widget.TextView
  text: Text
TextView
  class: android.widget.TextView
  text: Views

🚨 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.

🚨 You need to enable Continuous Integration on Greenkeeper 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:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  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 click the 'fix repo' button on account.greenkeeper.io.

Got this:

content').
[aapt]
[aapt] /Users/baba/Documents/Work/appium/submodules/ApiDemos/res/layout/progressbar_2.xml:22: error: creating resource for external package android: id/progress_large.
[aapt] /Users/baba/Documents/Work/appium/submodules/ApiDemos/res/layout/progressbar_2.xml:22: error: Error: No resource found that matches the given name (at 'id' with value '@+android:id/progress_large').
[aapt]
[aapt] /Users/baba/Documents/Work/appium/submodules/ApiDemos/res/layout/progressbar_2.xml:31: error: creating resource for external package android: id/progress_small.
[aapt] /Users/baba/Documents/Work/appium/submodules/ApiDemos/res/layout/progressbar_2.xml:31: error: Error: No resource found that matches the given name (at 'id' with value '@+android:id/progress_small').
[aapt]
[aapt] /Users/baba/Documents/Work/appium/submodules/ApiDemos/res/layout/progressbar_2.xml:36: error: creating resource for external package android: id/progress_small_title.
[aapt] /Users/baba/Documents/Work/appium/submodules/ApiDemos/res/layout/progressbar_2.xml:36: error: Error: No resource found that matches the given name (at 'id' with value '@+android:id/progress_small_title').
[aapt]

@Jonahss any idea how to make it compatible with all version build-tools?

I think we should use a different name for appium's flavor of the api demos. It's conflicting with the preinstalled api demos. I can't run any tests with it on Sauce because the old one must be uninstalled first.

package="com.example.android.apis">

What do you think of changing this to:

package="io.appium.android.apis">

I pulled ApiDemos from AOSP master and got it building on Gradle.
https://github.com/bootstraponline/api-demos

may make sense to update the appium version at some point.

🚨 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.