Develop Reference

UIAutomator viewer - incorrect UI XML Snapshoot

I've downloaded the SDK to try the uiautomationviewer.bat. It is works fine with native apps like 'calculator':
But, it shows incorrect position of elements in some games, viewer just loose focus or so, for example:
Environment:
OS - Windows 7 Pro / Android 7.0
Real Device - Samsung A510F
Java - 1.8.0_151
Android Debug Bridge version - 1.0.39
SDK version - 26.0.1
uiautomatorviewer - 25.3.1
Is there some way to find out what is going on (probably logs)? How to get XML with correct position of elements on the not native apps in my case?

How to setup an emulator running API 25 using a build matrix on Travis CI?

I am attempting to setup Travis CI so that it runs instrumentation tests on an emulator running API 25. Travis runs the tests to completion on API 4/10/19, but fails to startup the emulator for API 25, with the following message:
$ echo no | android create avd --force -n test -t $ANDROID_TARGET --abi $ANDROID_ABI
Valid ABIs: no ABIs.
Error: Invalid --abi armeabi-v7a for the selected target.
The output of android list targets shows that the API 19 emulator has a Tag/ABI, whereas the API 25 emulator does not:
id: 7 or "android-19"
Name: Android 4.4.2
Type: Platform
API level: 19
Revision: 4
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : default/armeabi-v7a
id: 11 or "android-25"
Name: Android 7.1.1
Type: Platform
API level: 25
Revision: 3
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : no ABIs.
How can I fix this so that the API 25 emulator launches and runs the tests?
The full .travis.yml file is as follows:
language: android
android:
components:
- tools
- platform-tools
- tools # appears twice as per Travis docs
- build-tools-23.0.1
- build-tools-25.0.2
- android-4
- android-10
- android-19
- android-23
- android-25
- extra-android-m2repository
- sys-img-armeabi-v7a-android-25
env:
matrix:
- ANDROID_TARGET=android-4 ANDROID_ABI=armeabi
- ANDROID_TARGET=android-10 ANDROID_ABI=armeabi
- ANDROID_TARGET=android-19 ANDROID_ABI=armeabi-v7a
- ANDROID_TARGET=android-25 ANDROID_ABI=armeabi-v7a
before_script:
# Create and start emulator
- android list targets
- jdk_switcher use oraclejdk8
- echo no | android create avd --force -n test -t $ANDROID_TARGET --abi $ANDROID_ABI
- emulator -avd test -no-skin -no-audio -no-window &
- adb wait-for-device
- while [[ `adb shell pm path android` == 'Error'* ]]; do sleep 2; done
- adb shell input keyevent 82 &
script: ./gradlew --info connectedAndroidTest
sudo: false

Note: emulator version 26.1.4+ versions can introduce or fix bugs. If a reproducible ci build is required, the best option is to download the desired sdk-tools version no via android components.
Note: emulator version 26.1.3 is here including interesting fixes. I'm busy to revise my answer now:
Related issue using emulator 26.1.2 here. Relaunch last build like me to use 26.1.3 and pray, green
I am attempting to setup Travis CI so that it runs instrumentation
tests on an emulator running API 25. Travis runs the tests to
completion on API 4/10/19, but fails to startup the emulator for API
25...
How can I fix this so that the API 25 emulator launches and runs the
tests?
Update: I confirmed that ARM ABIs for APIs 23, 25 and 26 are also missing in Android Studio, so:
It's not a Travis-ci issue. I reproduced it locally as shown in the next image.
You can use ARM ABI for API-24. I forked your project and it worked in build #6 (next image).
You can use Google APIs image for API-25 as I explain below using the new sdkmanager: 1
You can use Google APIs image for API-25 using legacy tools if you know the img name: 1,2,3
We need to ask to Google or someone else why the ARM ABIs for these APIs are missing.
Update: A related bug was already reported to Google and discussed here, please, star it:
For some reason it's marked as being only available on windows. I'm
not sure if this is a problem with ADRT itself or the configuration
for this package, but from a quick look it seems like it's probably a
problem with adrt itself.
I'm not sure if the api-25 issue is related but I expect that it will work combining several solutions:
Use system images with google_apis to simplify the build matrix and avoid missing ABIs.
Use the new sdkmanager and avdmanager required by the recent Sdk Tools.
Use the new Trusty images including these tools to simplify the Travis-ci configuration or alternatively use dist: precise as explained here.
See the links below to working samples using a build matrix that includes Api-25 emulator.
I updated the api 23 system image one time on a macbook via Android Studio and appeared a message about the new version was not supported by my computer, so I use the google_apis one.
I offer a possible solution to the issue commented by Ashish Pathak (I'm also ardock) here.
I need to update my response to support the new Travis-ci images that comes with new SDK tools.
The new pre-installed Sdk Tools will simplify the solution and reduce the YAML file in size.
As announced in this blog post by Carmen Andoh and Dominic Jodoin on 19 Jun 2017:
Updates are coming to all Ubuntu Trusty 14.04 images
This new generation of Trusty images is already available in
production and can be used by adding group: edge in your .travis.yml
file:
sudo: required
dist: trusty
group: edge # Add this
And as explained here:
As a bit more information, this new Android image comes with:
Android SDK 25.2.3 build-tools-25.0.2
The new sdkmanager tool - a command line tool that allows you to view,
install, update, and uninstall packages for the Android SDK. Replaces
the previous android tool, see
https://developer.android.com/studio/tools/help/android.html
Also, the new Android image should be retro-compatible. See the full
list of Android SDK components that can be specified in the
.travis.yml file, including build-tools-26.0.0-preview.
But they are not using the new avdmanager, I'll try to fix it this weekend.
Alternatively, you can use the previous images by adding dist: precise.
The lines below are part of my answer on a related question: prior to the images update:
Full working sample using constraint-layout codelab repository for Android API level 22 to 25:
Two more samples using sdkmanager and avdmanager:
Android Maps Utils library - Google
Dexter library - Karumi
References
Official documentation related to Auto-download missing packages with Gradle
The new Emulator options are explained in Start the Emulator from the Command Line
avdmanager explained here replaces android avd since SDK tools version 25.3.0
sdkmanager explained here also enhanced to view and accept all licenses from the command line

Structr - which version of Neo4j to use

Windows 7, java 8, Neo4j 3.0.0-M03, initial install of structr.
When I first try to run the program I'm getting this error:
SEVERE: Vital service HttpService failed to start: No resource provider available for servlet JsonRestServlet. Aborting
Reading the Google Groups the report is that structr is only good up to 2.2.6 - looking at the Neo4j Release Page 2.2.6 has been skipped - it goes from 2.1.8 to 2.2.8.
My question is what version should I use?
Also - is java 7 still a requirement? Looking at the Oracle website I'm seeing that 7 has been deprecated and won't be patched.

The most recent pre-built versions of Structr are built against and embed Neo4j 2.2.8.
To use with custom Neo4j versions, you can to build your own driver, see https://github.com/structr/structr-neo4j-driver. Should work with any 2.x version of Neo4j.
On the Java side, Java JDK 8 is a requirement.

Main.axml cant be opened VS2015

Connection to the layout renderer failed. This may be caused by a misconfiguration of Java
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
The value in my environment variable PATH is
C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files\Java\jdk1.8.0_51\bin;C:\Program Files (x86)\GtkSharp\2.12\bin

I got same error.
Mine was fixed by changing the following
Naivgate to the .Droid project,
Right Click -> properties
Select Application
Set Minimum Android to Target -> Andriod4.0.3 (API level15 - Ice Cream Sandwich)
Target Android Version -> Use Compile using Sdk Version

Failed to deploy to Google App Engine because --use_java7 flag has not been set

------------ Deploying frontend ------------
Preparing to deploy: Created staging directory at:
'C:\Users\ADMINI~1\AppData\Local\Temp\appcfg2555411734473986257.tmp'
java.lang.RuntimeException: The application contains Java 7 classes,
but the --use_java7 flag has not been set.
Debugging information may be found in
C:\Users\Administrator\AppData\Local\Temp\appengine-deploy7182870224187999057.log
Debug Log:
Unable to update:
java.lang.RuntimeException: The application contains Java 7 classes, but the --use_java7 flag has not been set.
at com.google.appengine.tools.admin.Application.createStagingDirectory(Application.java:576)
at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:370)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:53)
at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:433)
at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
I'm attempting to deploy a google app to my google app engine account and eclipse is giving me this error. It seems rather straight forward, but I can't find where to set a flag for java7.
I'm using the latest version of Eclipse (Juno Service Release 1) and my google plugin is 4.2.

The relevant system level property is shown here: com.google.apphosting.runtime.use_java7
It can be passed into appCfg.sh like so:
appcfg.sh --use_java7 update

As per the 1.7.3 blog post:
In an upcoming release, we will be including some of the new Java 7
functionality as well as formal Java 7 support within the App Engine
Java runtime.
and...
And while Java 7 support is not yet available within the App Engine
Java runtime, developers interested in an early preview can sign up
for our trusted tester program.
You'll need to either be accepted into the TT program, or to wait for a future release where Java 7 works in production.