Apk deployment for

This article introduces approaches for limiting the size of your APK files for your Android deployments.ArcGIS Maps SDK for Kotlin makes use of a native library written in C++. The library provides very fast map rendering and processing capabilities which have consistent behavior on all supported platforms. Your map in an app written for an iPhone using the iOS SDK will look the same as it does on the various Android architectures.Android supports many instruction set architectures, and the APK needs a compiled version of the ArcGIS Maps API for Kotlin library (included as an .so file) for each architecture. Consequently, the final APK size can get quite large, especially if you are using multiple native libraries. The Google Play Store, however, limits your APK to 100MB.For a larger applications, there are two options to reduce the size of your deployment: ABI filters and SDK splits.ABI FiltersABI (Application Binary Interface) filters determine which architectures to allow in an APK deployment. For example, x86 architectures, typically used for emulator environments, are generally not included in release builds.ABI filters are applied in your Gradle build script (Module:app). The abifilters property in ndk specifies which ABI(s) to include in a build type. The following example applies ABI filters to the release build, allowing only architectures supported by the armeabi-v7a and arm64-v8a ABIs. While indispensable for debugging on an emulator, the x86 libraries do not belong in your deployed APK.Without an ABI filter, your APK will include all available architectures, with .so files for each. In the image below, the APK is 76MB. After applying the filter, APK size reduces from 76MB to 51MB. Additional information about ABI management in your application can be found at ABI Management on developer.android.com.APK SplitsIf your application supports many architectures, you can further reduce APK size by using APK splits, whereby each APK includes only one architecture.ArcGIS Maps SDK for Kotlin, release 100.5 and later, supports x64 architectures, adding more .so files to a single APK deployment. If you are deploying to the Google Play Store, consider APK splits to reduce the download size of your app. In areas with slow mobile networks or high data costs, smaller download size can make a big difference. For more information go to Build multiple APKs on developer.android.com.

NGINX packages in your system, back up your configs and logs:sudo cp -a /etc/nginx /etc/nginx-plus-backupsudo cp -a /var/log/nginx /var/log/nginx-plus-backupLog in to the Customer Portal and download the following two files:nginx-repo.keynginx-repo.crtUpload nginx-repo.key to /etc/apk/cert.key and nginx-repo.crt to /etc/apk/cert.pem. Make sure that files do not contain other certificates and keys, as Alpine Linux does not support mixing client certificates for different repositories.Add the NGINX public signing key to the directory /etc/apk/keys:sudo wget -O /etc/apk/keys/nginx_signing.rsa.pub wget -O /etc/apk/keys/app-protect-security-updates.rsa.pub any previously configured NGINX Plus repository:sed "/plus-pkgs.nginx.com/d" /etc/apk/repositoriesAdd the NGINX Plus repository to /etc/apk/repositories file:printf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | sudo tee -a /etc/apk/repositoriesAdd the NGINX App Protect WAF repository to /etc/apk/repositories file:printf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | sudo tee -a /etc/apk/repositoriesprintf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | sudo tee -a /etc/apk/repositoriesWe recommend removing all community-supported NGINX packages. Note that all NGINX modules will be removed as well.sudo apk del -r app-protectsudo apk del -r nginxUpdate the repository and install the most recent version of the NGINX Plus and NGINX App Protect WAF:sudo apk updatesudo apk add app-protectAlternatively, use the following commands to install the most recent version of NGINX App Protect WAF for NGINX Plus R28:sudo apk updatesudo apk add app-protectAlternatively, use the following commands to list available versions:sudo apk updatesudo apk info app-protectFinally, install a specific version from the output of command above. For example:sudo apk add app-protect=30.4.457.0-r1Check the NGINX binary version to ensure that you have NGINX Plus installed correctly:Load the NGINX App Protect WAF module on the main context in the nginx.conf file:load_module modules/ngx_http_app_protect_module.so;Enable NGINX App Protect WAF on an http/server/location context in the nginx.conf via:Start the App Protect and NGINX services:sudo service nginx-app-protect startsudo service nginx startDocker Deployment General Docker Deployment Instructions Create a Dockerfile (see examples below) which copies the following files into the docker image:nginx.conf: User defined nginx.conf with

Nginx-plus\n" | \ tee /etc/apt/sources.list.d/nginx-app-protect.list RUN printf "deb [signed-by=/usr/share/keyrings/app-protect-security-updates.gpg] \ `lsb_release -cs` nginx-plus\n" | \ tee /etc/apt/sources.list.d/app-protect-security-updates.list# Download the apt configuration to `/etc/apt/apt.conf.d`:RUN wget -P /etc/apt/apt.conf.d Update the repository and install the most recent version of the NGINX App Protect WAF Compiler package:RUN --mount=type=secret,id=nginx-crt,dst=/etc/ssl/nginx/nginx-repo.crt,mode=0644 \ --mount=type=secret,id=nginx-key,dst=/etc/ssl/nginx/nginx-repo.key,mode=0644 \ apt-get update && DEBIAN_FRONTEND="noninteractive" apt-get install -y app-protect-compilerAlpine 3.16 / Alpine 3.17 / Alpine 3.19 Converter Docker Deployment Example # syntax=docker/dockerfile:1# For Alpine 3.16/3.17/3.19:FROM alpine:3.19# Download and add the NGINX signing keys:RUN wget -O /etc/apk/keys/nginx_signing.rsa.pub \ && wget -O /etc/apk/keys/app-protect-security-updates.rsa.pub Add NGINX Plus repository:RUN printf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | tee -a /etc/apk/repositories \ && printf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | tee -a /etc/apk/repositories# Update the repository and install the most recent version of the NGINX App Protect WAF Compiler package:RUN --mount=type=secret,id=nginx-crt,dst=/etc/apk/cert.pem,mode=0644 \ --mount=type=secret,id=nginx-key,dst=/etc/apk/cert.key,mode=0644 \ apk update && apk add app-protect-compilerOffline Installation To perform an offline installation of NGINX App Protect WAF you can use a host with access to the NGINX repository to download all the packages (including dependencies) to your local repository.Example Deployment for CentOS/RHEL Add the NGINX App Protect WAF Packages to an Internal Repository On a host with access to the NGINX App Protect WAF repository:Install the downloadonly plugin for Yum:yum -y install yum-plugin-downloadonlyDownload all NGINX App Protect WAF packages, including all dependencies:mkdir -p /etc/packages/yum install --downloadonly --downloaddir=/etc/packages/ app-protectDownload the epel-release dependency package:For CentOS:yum install --downloadonly --downloaddir=/etc/packages/ epel-releaseFor RHEL 7:wget -P /etc/packages RHEL 8.1+ / Oracle Linux 8.1+:wget -P /etc/packages RHEL 9+:wget -P /etc/packages the packages in /etc/packages to your local repository.Install NGINX App Protect WAF from an Internal Repository On an offline host:Add your internal repository configuration.Install NGINX App Protect WAF:yum -y install app-protectExample Deployment for Debian/Ubuntu Add the NGINX App Protect WAF Packages to an Internal Repository On a host with access to the NGINX App Protect

-sf /dev/stdout /var/log/nginx/access.log \ && ln -sf /dev/stderr /var/log/nginx/error.log# Copy configuration files:COPY nginx.conf custom_log_format.json /etc/nginx/COPY entrypoint.sh /root/CMD ["sh", "/root/entrypoint.sh"]Alpine 3.16 / Alpine 3.17 / Alpine 3.19 Docker Deployment Example # syntax=docker/dockerfile:1# For Alpine 3.16/3.17/3.19:FROM alpine:3.19# Download and add the NGINX signing keys:RUN wget -O /etc/apk/keys/nginx_signing.rsa.pub \ && wget -O /etc/apk/keys/app-protect-security-updates.rsa.pub Add NGINX Plus repository:RUN printf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | tee -a /etc/apk/repositories# Add NGINX App Protect repository:RUN printf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | tee -a /etc/apk/repositories \ && printf " -o '^[0-9]+\.[0-9]+' /etc/alpine-release`/main\n" | tee -a /etc/apk/repositories# Update the repository and install the most recent version of the NGINX App Protect WAF package (which includes NGINX Plus):RUN --mount=type=secret,id=nginx-crt,dst=/etc/apk/cert.pem,mode=0644 \ --mount=type=secret,id=nginx-key,dst=/etc/apk/cert.key,mode=0644 \ apk update && apk add app-protect# Forward request logs to Docker log collector:RUN ln -sf /dev/stdout /var/log/nginx/access.log \ && ln -sf /dev/stderr /var/log/nginx/error.log# Copy configuration files:COPY nginx.conf custom_log_format.json /etc/nginx/COPY entrypoint.sh /root/CMD ["sh", "/root/entrypoint.sh"]This section explains how to build a Docker image for the purpose of converting policy files from other F5 WAF products to NGINX App Protect WAF JSON declarative format.For more details regarding this feature refer to Converter Tools.Converter Docker Deployment Instructions You need root permissions to execute the following steps.Create a Dockerfile (see examples below).Log in to the Customer Portal and download the following two files:nginx-repo.keynginx-repo.crtCreate a Docker image:For CentOS/Oracle Linux/Debian/Ubuntu/Alpine/Amazon Linux:DOCKER_BUILDKIT=1 docker build --no-cache --secret id=nginx-crt,src=nginx-repo.crt --secret id=nginx-key,src=nginx-repo.key -t app-protect-converter .The DOCKER_BUILDKIT=1 enables docker build to recognize the --secret flag which allows the user to pass secret information to be used in the Dockerfile for building docker images in a safe way that will not end up stored in the final image. This is a recommended practice for the handling of the certificate and private key for NGINX repository access (nginx-repo.crt and nginx-repo.key files). More information here.For RHEL:podman build --no-cache --secret id=nginx-crt,src=nginx-repo.crt --secret id=nginx-key,src=nginx-repo.key -t

Morning We have a custom app being built for us as an APK which I have successfully deployed previously. I've added it to our private google store and then deployed via a group. Worked absolutely fine. The recent update and the most important one as it's the go live APK for the new system we're working on, I cannot get to work at all and I'm into my 5th version of the APK from the vendor and I've tried every way I know. I'm new to Android I've only ever worked with Apple and it's seemless deploying APPs with Apple. Android is a nightmare. I've followed the following process;1) All Apps2) Add3) Managed Google Play app4) I've added two here a test app and the actual deployment. 5) Now once uploaded I press sync, the test app which has been used the entire time shows up. The go live app doesn't. In Attachment 1, it has the logo. And the app doesn't sync into the app library. I try changing the APK of the test version and I get every error under the sun. Default name is incorrect. Unable to change this APK. Login to the Admin Google store - Which then gives me another error to say that this doesn't exist. The other way of doing it is by 1) Add app2) Line of business App3) I then add the APK, I add the scope and I add the exact same group as I've deployed all of the test devices. I even add it to all users, everything possible. And does the app deploy to the phone? It doesn't. I've changed the deployment type from required to available for enrolled devices to available with or without enrolment. It can't be seen in the store. It doesn't show any statistics at all. That's allowing ANY user to download and install this app. I've spent the best part of 10 hours on this and I can't find any decent tutorials to see if I am going wrong. I've deployed and set up iOS MDM on InTune deploying hundreds of apps and never had this before. Maybe I am missing something simple.