[windows] Docker APK build

Describe the bug I ran:

• docker pull debian:latest
• docker build -f android.Dockerfile -t exokit .
• docker run exokit cat exokit.apk >exokit.apk

As instructed.

The full error log was:

Step 1/12 : FROM debian:latest —> 00bf7fdd8baf Step 2/12 : RUN apt-get update -y && apt-get install -y build-essential wget python git unzip default-jdk —> Using cache —> 84a026d7b00a Step 3/12 : RUN groupadd -g 999 appuser && useradd -r -u 999 -g appuser appuser —> Using cache —> 0431fe293649 Step 4/12 : ENV HOME /home/appuser —> Using cache —> e03eb1e0a52e Step 5/12 : ADD . $HOME/app —> b8c07fba40aa Step 6/12 : WORKDIR $HOME/app —> Running in 0a86d0caa1f0 Removing intermediate container 0a86d0caa1f0 —> 5a17f368f268 Step 7/12 : RUN echo $HOME —> Running in f81a11f8cf5e /home/appuser Removing intermediate container f81a11f8cf5e —> fa9f3c4f46a9 Step 8/12 : RUN chown -R appuser:appuser $HOME && chmod -R 777 $HOME —> Running in 32b96fb9fd76 Removing intermediate container 32b96fb9fd76 —> 32ff829c0b8a Step 9/12 : USER appuser —> Running in 80d2cdae055c Removing intermediate container 80d2cdae055c —> 0e3717eef25a Step 10/12 : RUN wget “https://nodejs.org/dist/v11.6.0/node-v11.6.0-linux-x64.tar.gz” -O node.tar.gz -q && tar -zxf node.tar.gz > /dev/null && rm node.tar.gz && mv node-v11.6.0-linux-x64 node —> Running in 2c028081b16a Removing intermediate container 2c028081b16a —> 0b58a7e3cf41 Step 11/12 : RUN wget https://dl.google.com/android/repository/sdk-tools-linux-4333796.zip -q && unzip sdk-tools-linux-4333796.zip > /dev/null && rm sdk-tools-linux-4333796.zip && mkdir android-sdk && export ANDROID_HOME=$(pwd)/android-sdk && mv tools android-sdk/tools && yes | $ANDROID_HOME/tools/bin/sdkmanager --licenses > /dev/null && $ANDROID_HOME/tools/bin/sdkmanager “platform-tools” “platforms;android-28” > /dev/null && $ANDROID_HOME/tools/bin/sdkmanager “ndk-bundle” > /dev/null && export PATH=“$PATH:$(pwd)/node/bin” && scripts/make-toolchain-android.sh && scripts/build-android.sh —> Running in ac614095cdca Exception in thread “main” java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156) at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75) at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81) at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73) at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48) Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) … 5 more The command ‘/bin/sh -c wget https://dl.google.com/android/repository/sdk-tools-linux-4333796.zip -q && unzip sdk-tools-linux-4333796.zip > /dev/null && rm sdk-tools-linux-4333796.zip && mkdir android-sdk && export ANDROID_HOME=$(pwd)/android-sdk && mv tools android-sdk/tools && yes | $ANDROID_HOME/tools/bin/sdkmanager --licenses > /dev/null && $ANDROID_HOME/tools/bin/sdkmanager “platform-tools” “platforms;android-28” > /dev/null && $ANDROID_HOME/tools/bin/sdkmanager “ndk-bundle” > /dev/null && export PATH=“$PATH:$(pwd)/node/bin” && scripts/make-toolchain-android.sh && scripts/build-android.sh’ returned a non-zero code: 1

[kennardconsulting]

Hurrah that works! Thanks.

Just to confirm, I understand Exokit is not a browser, but can it display a non-VR HTML ‘landing page’ with a button that you click to start VR?

[avaer]

An example start command I use:

.\adb.exe shell am start -n com.webmr.exokit/android.app.NativeActivity -e ARGS "'node --experimental-vm-modules /package -x webvr https://aframe.io/aframe/examples/boilerplate/hello-world/'"