Bug 53242 - Create new android project, enable multidex, build fails
Summary: Create new android project, enable multidex, build fails
Status: RESOLVED DUPLICATE of bug 44187
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2017-03-10 22:09 UTC by James Moore
Modified: 2017-04-12 18:59 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description James Moore 2017-03-10 22:09:47 UTC
Create a new Android C# project.  Go in to build settings and turn on multidex.  No other changes needed.





/Users/james/Projects/MultidexTest/MultidexTest/MultidexTest.csproj (Build) ->
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets (_CompileToDalvikWithDx target) ->

	/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: error : Tool exited with code: 10. Output: Error: Can't read [/Library/Frameworks/Xamarin.Android.framework/Versions/7.2.0-1/lib/xbuild-frameworks/MonoAndroid/v7.1/mono.android.jar] (Can't process class [android/app/ActivityTracker.class] (Unsupported class version number [52.0] (maximum 51.0, Java 1.7)))
Comment 1 James Moore 2017-03-10 22:11:00 UTC
=== Xamarin Studio Professional ===

Version 6.3 (build 831)
Installation UUID: 6dc077b1-7f04-4c1c-b481-1dcbb9a8b0a1
	Mono 4.8.0 (mono-4.8.0-branch/0494d70) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 408000516

=== NuGet ===


=== Xamarin.Profiler ===

Version: 1.3.2
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Xamarin.Android ===

Version: (Visual Studio Professional)
Android SDK: /Users/james/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		4.4 (API level 19)
		5.0 (API level 21)
		6.0 (API level 23)
		7.0 (API level 24)
		7.1 (API level 25)

SDK Tools Version: 25.3.1
SDK Platform Tools Version: 25.0.3
SDK Build Tools Version: 25.0.2

Java SDK: /Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home
java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)

Android Designer EPL code available here:

=== Apple Developer Tools ===

Xcode 8.2.1 (11766.1)
Build 8C1002

=== Xamarin.Mac ===

Version: (Visual Studio Professional)

=== Xamarin Inspector ===

Version: 1.2.0-rc.2
Hash: 15b00be
Branch: d15-1
Build date: Mon, 06 Mar 2017 15:58:04 GMT

=== Xamarin.iOS ===

Version: (Visual Studio Professional)
Hash: 9995504
Branch: master
Build date: 2017-03-03 17:18:51-0500

=== Build Information ===

Release ID: 603000831
Git revision: 7de8ca50bde6552a271e08e88e99a4e0d30cd384
Build date: 2017-02-27 11:27:41-05
Xamarin addins: 959ddb54b5c8f1d757919063b3e9e7feef7028a7
Build lane: monodevelop-lion-d15-1

=== Operating System ===

Mac OS X 10.12.3
Darwin retina.local 16.4.0 Darwin Kernel Version 16.4.0
    Thu Dec 22 22:53:21 PST 2016
    root:xnu-3789.41.3~3/RELEASE_X86_64 x86_64
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2017-04-12 18:59:49 UTC

*** This bug has been marked as a duplicate of bug 44187 ***