You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does your app compile and launch successfully without the Intune App SDK? Yes
Have you checked the [Microsoft Intune App SDK for Android] repository for similar issues? Yes
Are you using the latest version of the [SDK and Plugin]? Yes
Summary
When processing .jars with BuildToolCLI, the tool removes META-INF from the output .jar.
This creates various problems. For example, some .jars contain embedded proguard config META-INF/com.android.tools/r8/*, and stripping them causes compilation errors.
Note that when the --input is a directory rather than a .jar, BuildToolCLI copies META-INF correctly.
Details
Intune Android App SDK Version: 9.7.0
Gradle Version: N/A, this is standalone BuildToolCLI
AGP Version: N/A, this is standalone BuildToolCLI
Operating System (Mac, Linux, Windows) and Version: Linux (Fedora 37)
Android Studio Version: N/A, this is standalone BuildToolCLI
Logs
Android Studio / Gradle Logs
N/A, no gradle or Android Studio. This is standalone BuildToolCLI.
It doesn't print any errors, rewrite completes successfully. Downstream dex-ing fails with the rewritten .jars.
Gradle Build Plugin Report Logs
N/A, no gradle or Android Studio. This is standalone BuildToolCLI.
It doesn't print any errors, rewrite completes successfully. Downstream dex-ing fails with the rewritten .jars.
The text was updated successfully, but these errors were encountered:
Hi @nikita-island , thanks for reporting this issue. We have created a bug (ADO# 25068431) internally to track. I'd like to ask a few clarification questions please:
Is your app a native Android app? Or is it built with some other frameworks like Xamarin?
Does it work when you put the jar file in a directory, and provide the directory as --input?
Questions to Ask Before Submission
Summary
When processing
.jar
s withBuildToolCLI
, the tool removesMETA-INF
from the output.jar
.This creates various problems. For example, some
.jar
s contain embedded proguard configMETA-INF/com.android.tools/r8/*
, and stripping them causes compilation errors.Example of a public
.jar
where proguard config gets stripped: org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm:1.6.4Note that when the
--input
is a directory rather than a.jar
,BuildToolCLI
copiesMETA-INF
correctly.Details
BuildToolCLI
BuildToolCLI
BuildToolCLI
Logs
Android Studio / Gradle Logs
N/A, no gradle or Android Studio. This is standalone
BuildToolCLI
.It doesn't print any errors, rewrite completes successfully. Downstream dex-ing fails with the rewritten
.jar
s.Gradle Build Plugin Report Logs
N/A, no gradle or Android Studio. This is standalone
BuildToolCLI
.It doesn't print any errors, rewrite completes successfully. Downstream dex-ing fails with the rewritten
.jar
s.The text was updated successfully, but these errors were encountered: