microsoftconnect / intune-app-wrapping-tool-android

Use the Intune App Wrapping Tool for Android to enable Android apps to be managed by Microsoft Intune
28 stars 11 forks source link

The same apk file successfully wrapped on one windows machine and no output apk file on another #65

Closed paulinaZasada-hub closed 2 years ago

paulinaZasada-hub commented 2 years ago

Me and my colleague are trying to wrap the same apk file. For my machine it's working fine, meaning I have the output apk file and success message in PowerShell. My colleague though, is struggling, because her process is finishing in the middle without any error message, but also without success message and output apk file. This is her log from PowerShell:

PS C:\Program Files (x86)\Microsoft Intune Mobile Application Management\Android\App Wrapping Tool> invoke-AppWrappingTool -InputPath .\fileStep13.apk -OutputPath .\App-Wrapped.apk -Verbose
Application wrapping in progress. App Wrapping Tool Version: 1.0.3610.6
Using Apktool 2.6.0 on fileStep13.apk
Loading resource table...
Decoding AndroidManifest.xml with resources...
Loading resource table from file: C:\Users\KB\AppData\Local\Temp\IntuneAppWrappingTool-7862730524804707949\framework\1.apk
Regular manifest package...
Decoding file-resources...
Win version: 0x4a62000a = 1247936522 (Windows Vista)
Decoding values */* XMLs...
Baksmaling classes.dex...
Copying assets and libs...
Copying unknown files...
Copying original files...
Using Apktool 2.6.0 on IntuneAppBase.apk
Loading resource table...
Decoding AndroidManifest.xml with resources...
Loading resource table from file: C:\Users\KB\AppData\Local\Temp\IntuneAppWrappingTool-7862730524804707949\framework\1.apk
Regular manifest package...
Decoding file-resources...
Decoding values */* XMLs...
Baksmaling classes.dex...
Copying assets and libs...
Copying unknown files...
Copying original files...
SDK information for the application set to {minSdkVersion=28, targetSdkVersion=30}
Checking whether resources has changed...
Building resources...
aapt2 compile command ran:
[C:\Users\KB\AppData\Local\Temp\brut_util_Jar_87074634624135250082093660415071642874.tmp, compile, --dir, C:\Users\KB\AppData\Local\Temp\IntuneAppWrappingTool-7862730524804707949\sourceApk\res, --legacy, -o, C:\Users\KB\AppData\Local\Temp\IntuneAppWrappingTool-7862730524804707949\sourceApk\build\resources.zip]
aapt2 link command ran:
[C:\Users\KB\AppData\Local\Temp\brut_util_Jar_87074634624135250082093660415071642874.tmp, link, -o, C:\Users\KB\AppData\Local\Temp\APKTOOL14154867220678917489.tmp, --min-sdk-version, 28, --target-sdk-version, 30, --no-auto-version, --no-version-vectors, --no-version-transitions, --no-resource-deduping, -0, arsc, -I, C:\Users\KB\AppData\Local\Temp\IntuneAppWrappingTool-7862730524804707949\framework\1.apk, --manifest, C:\Users\KB\AppData\Local\Temp\IntuneAppWrappingTool-7862730524804707949\sourceApk\AndroidManifest.xml, C:\Users\KB\AppData\Local\Temp\IntuneAppWrappingTool-7862730524804707949\sourceApk\build\resources.zip]
Loading resource table...
PS C:\Program Files (x86)\Microsoft Intune Mobile Application Management\Android\App Wrapping Tool>

The only difference between our environments I believe is Java version, I run Java 1.8 and she runs openJDK 17 on her machine. Anyone has an idea what can cause that? Thanks!

paulinaZasada-hub commented 2 years ago

Rebooting machine did the trick.