Error: "java.exe" exited with code 1 in Release mode

[dehghani-mehdi]

Steps to Reproduce

1. Open up any Xamarin.Android project
2. Change Solution Configuration to Release mode
3. Try to build the solution

Expected Behavior

Successful build.

Actual Behavior

I got this error

"java.exe" exited with code 1.

Version Information

I'm using VS 2017, v 15.6

Xamarin 4.9.0.749
Xamarin Designer 4.10.58
Xamarin.Android SDK 8.2.0.15

I tired following:

1. Updating Proguard to latest version
2. Updating JDK (jdk1.8.0_162), but downgraded to 161 again
3. Set 1G as Java max heap size
4. And all other solutions that you can find here: https://forums.xamarin.com/discussion/9305/java-exe-exited-with-code-1-xamarin-android-common-targets

I'm using Support library v4 and v7, Picaso, CallygraphyXamarin and JSON.net

In Debug mode I can build and archive the solution without any problem.

Update:
If I disable Proguard , I can get successful build/archive.

[jonpryor]

Please provide diagnostic build log output.

What OS+platform are you on? Is it 32-bit or 64-bit?

[dehghani-mehdi]

@jonpryor Windows 10 x64

The diagnostic build log output:
diagnostic build log output.txt

[jonpryor]

@dehghani-mehdi: Thank you.

This appears to be the culprit:

1>  C:\Program-Files-(x86)\Java\jdk1.8.0_161\\bin\java.exe -jar "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\Android\proguard\lib\proguard.jar" -include "'C:\Program-Files-(x86)\Android\android-sdk\\tools\proguard\proguard-android.txt'" -include "'obj\Release\proguard\proguard_xamarin.cfg'" -include "'obj\Release\proguard\proguard_project_references.cfg'" -include "'obj\Release\proguard\proguard_project_primary.cfg'" -include "'proguard.cfg'" -include "'IT_IS_JUST_PATH_TO_SOLUTION\packages\Xamarin.Android.Arch.Lifecycle.Runtime.1.0.0\build\MonoAndroid80\..\..\proguard\proguard.txt'" -include "'IT_IS_JUST_PATH_TO_SOLUTION\packages\Xamarin.Android.Support.Core.UI.26.1.0.1\build\MonoAndroid80\..\..\proguard\proguard.txt'" -include "'IT_IS_JUST_PATH_TO_SOLUTION\packages\Xamarin.Android.Support.Media.Compat.26.1.0.1\build\MonoAndroid80\..\..\proguard\proguard.txt'" -include "'IT_IS_JUST_PATH_TO_SOLUTION\packages\Xamarin.Android.Support.v7.RecyclerView.26.1.0.1\build\MonoAndroid80\..\..\proguard\proguard.txt'" -include "'IT_IS_JUST_PATH_TO_SOLUTION\packages\Xamarin.Android.Support.Animated.Vector.Drawable.26.1.0.1\build\MonoAndroid80\..\..\proguard\proguard.txt'" -include "'IT_IS_JUST_PATH_TO_SOLUTION\packages\Xamarin.Android.Support.Design.26.1.0.1\build\MonoAndroid80\..\..\proguard\proguard.txt'" -injars "'obj\Release\android\bin\classes\..\classes.zip'(!META-INF/MANIFEST.MF);'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\MonoAndroid\v8.1\mono.android.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\0\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\11\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\12\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\13\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\14\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\15\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\16\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\17\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\18\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\19\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\2\jl\okhttp.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\20\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\21\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\22\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\3\jl\okio.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\4\jl\picasso-2.5.2.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\6\jl\arch-core-common.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\7\jl\arch-lifecycle-common.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\8\jl\bin\classes.jar'(!META-INF/MANIFEST.MF);'obj\Release\lp\9\jl\bin\classes.jar'(!META-INF/MANIFEST.MF)" -libraryjars "'C:\Program-Files-(x86)\Android\android-sdk\platforms\android-27\android.jar'" -outjars obj\Release\proguard\__proguard_output__.jar -optimizations !code/allocation/variable  (TaskId:396)
1>  proguard.ParseException: Unknown option '-dontwarn' in line 1 of file 'proguard.cfg', (TaskId:396)
1>    included from argument number 10 (TaskId:396)
1>      at proguard.ConfigurationParser.parse(Unknown Source) (TaskId:396)
1>      at proguard.ProGuard.main(Unknown Source) (TaskId:396)
1>  Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 (TaskId:396)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2132,3): error MSB6006: "java.exe" exited with code 1.

In particular that second line:

proguard.ParseException: Unknown option '-dontwarn' in line 1 of file 'proguard.cfg',

This appears to be an issue regarding file encoding.

Unfortunately I don't know what the current-working-directory for that java.exe, and thus I don't know where proguard.cfg is coming from. Is it in your project directory?

For that matter, I don't know why proguard.cfg is being mentioned at all. Presumably it's via @(ProguardConfiguration), but I don't see it listed in other mentions of @(ProguardConfiguration) in that log file, so this is a tad confusing.

[jonpryor]

Would you be able to provide your project? I really don't understand where proguard.cfg is coming from.

[dehghani-mehdi]

@jonpryor You're welcome, I added proguard.cfg to the root of the project and set as ProguardConfiguration (in build action section). it's one of solutions that I found in that post on Xamarin's forum.
I got the error without that too.
Should I send log without proguard.cfg?

[jonpryor]

@dehghani-mehdi: Yes, or you can read the log and provide the next bit of output around error MSB6006: "java.exe" exited with code 1.

[dehghani-mehdi]

Here you go
xamarin log.txt

[dehghani-mehdi]

Error point to line 2132, col 3 of:

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets" Which is:

  <Proguard
    Condition="'$(AndroidEnableProguard)' == 'True' and '$(_ProguardProjectConfiguration)' != ''"
    ProguardJarPath="$(ProguardJarPath)"
    AndroidSdkDirectory="$(_AndroidSdkDirectory)"
    JavaToolPath="$(JavaToolPath)"
    ProguardToolPath="$(ProguardToolPath)"
    ToolExe="$(ProguardToolExe)"
    UseProguard="$(UseProguard)"
    JavaPlatformJarPath="$(JavaPlatformJarPath)"
    ClassesOutputDirectory="$(IntermediateOutputPath)android\bin\classes"
    AcwMapFile="$(_AcwMapFile)"
    ProguardCommonXamarinConfiguration="$(IntermediateOutputPath)proguard\proguard_xamarin.cfg"
    ProguardGeneratedReferenceConfiguration="$(_ProguardProjectConfiguration)"
    ProguardGeneratedApplicationConfiguration="$(IntermediateOutputPath)proguard\proguard_project_primary.cfg"
    ProguardConfigurationFiles="$(ProguardConfigFiles)"
    JavaLibrariesToEmbed="@(_JarsToProguard);@(_InstantRunJavaReference)"
    ExternalJavaLibraries="@(AndroidExternalJavaLibrary)"
    DoNotPackageJavaLibraries="@(_ResolvedDoNotPackageAttributes)"
    ProguardJarOutput="$(IntermediateOutputPath)proguard\__proguard_output__.jar"
    EnableLogging="$(ProguardEnableLogging)"
    DumpOutput="$(IntermediateOutputPath)proguard\dump.txt"
    PrintSeedsOutput="$(IntermediateOutputPath)proguard\seeds.txt"
    PrintUsageOutput="$(IntermediateOutputPath)proguard\usage.txt"
    PrintMappingOutput="$(IntermediateOutputPath)proguard\mapping.txt"
    ProguardInputJarFilter="$(_AndroidProguardInputJarFilter)"
     />

[omarhimada]

I'm getting this same issue. Only occurs in Release mode. I tried playing around with the configuration manager (ignoring certain projects, etc.) but no luck
Xamarin.Forms.Core runtime is v4.0.30319, Android is up to date, etc.

[dehghani-mehdi]

@omarhimada if you use third-party libraries, maybe you need to use custom ProGuard config. for example see: https://github.com/square/okio#proguard

[Nixon-Joseph]

I'm also getting this, seems to be identical. Any help would be appreciated, we're supposed to go live in a couple weeks, and this was building fine up until now.

So far the only change that I can see possibly doing this is I recently added Firebase for my android project. Removing Firebase and all relevant code for it does stop the error.

I'm thinking maybe it has something to do with the required GooglePlay package for Firebase?

[Nixon-Joseph]

Can't figure it out. Have tried updating my proguard (because my build target is 8.1), creating a custom proguard config, and every other suggestion that the internet has.
I've decided not to enable Proguard for this particular project, because Xamarin.Android doesn't obfuscate anyway, and without it. my apk is only 1MB bigger. So the difference is negligible. Hopefully it gets fixed in the future, but where obfuscation isn't even an option (I thought it was before this), I'll just live without it for now.

Hopefully you have the same option, if no other fixes come up.

[omarhimada]

Question: does disabling proguard have any performance implications besides just increased file size?

…

On Mon, Apr 30, 2018, 3:41 PM Joseph Nixon, ***@***.***> wrote: Can't figure it out. Have tried updating my proguard (because my build target is 8.1), creating a custom proguard config, and every other suggestion that the internet has. I've decided not to enable Proguard for this particular project, because Xamarin.Android doesn't obfuscate anyway, and without it. my apk is only 1MB bigger. So the difference is negligible. Hopefully it gets fixed in the future, but where obfuscation isn't even an option (I thought it was before this), I'll just live without it for now. Hopefully you have the same option, if no other fixes come up. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1369 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACZr50TbPffkeLqBUH082qyfRDslqyPVks5tt2jpgaJpZM4SejfI> .

[Nixon-Joseph]

I haven't seen any, but I imagine it would depend on the size of your project. My compiled application without Proguardends up only being about 17MB (for now).

https://docs.microsoft.com/en-us/xamarin/android/deploy-test/release-prep/proguard?tabs=vswin

This document shows what proguard does in Xamarin.Android - "ProGuard Step
After the linker step completes successfully, Proguard is run to remove unused Java bytecode. This is the step that optimizes the APK."

In summary, my limited understanding, is after linking (the part that really trims down your file size), all Proguard does is run through your leftover code, and removes all references to unused parameters, variables, methods, etc...

I would imagine that if you had a very large project, it would be far more useful. But for mine, I doubt there will be any notable difference.

[omarhimada]

I mean, I agree that it sounds like it probably doesn't make a HUGE difference, but it's bound to have atleast SOME difference I just hope there is some solution that doesn't involve disabling a nice-to-have feature

…

On Mon, Apr 30, 2018, 3:54 PM Joseph Nixon, ***@***.***> wrote: I haven't seen any, but I imagine it would depend on the size of your project. My compiled application without Proguardends up only being about 17MB (for now). https://docs.microsoft.com/en-us/xamarin/android/deploy-test/release-prep/proguard?tabs=vswin This document shows what proguard does in Xamarin.Android - "ProGuard Step After the linker step completes successfully, Proguard is run to remove unused Java bytecode. This is the step that optimizes the APK." In summary, my limited understanding, is after linking (the part that really trims down your file size), all Proguard does is run through your leftover code, and removes all references to unused parameters, variables, methods, etc... I would imagine that if you had a very large project, it would be far more useful. But for mine, I doubt there will be any notable difference. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1369 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACZr5y2GtaULd-EQy_B5flEYkLCEy5FAks5tt2vkgaJpZM4SejfI> .