Bug 2367 - Invalid Java generated for constructors that call base with different parameters
Summary: Invalid Java generated for constructors that call base with different parameters
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 2.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-12-06 12:10 UTC by Jonathan Pobst
Modified: 2011-12-08 22:12 UTC (History)
3 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 Jonathan Pobst 2011-12-06 12:10:37 UTC
Calls to Java's "super" in constructors is based on the constructor definition even though it may be calling base with different parameters:

using System;
using Android.Content;
using Android.Widget;

namespace LayoutTest
	class MyLayout : LinearLayout
		// This constructor is fine
		public MyLayout (Context context) : base (context)

		// This constructor causes the error:
		// cannot find symbol
		// symbol  : constructor LinearLayout()
		// location: class android.widget.LinearLayout
		// 		super ();
		public MyLayout () : base (null)
Comment 1 Philippe Girolami 2011-12-07 03:52:30 UTC
"The workaround is to remove your constructor with no parameters:
protected DrteView()
: this((Context)CdlAndroidSettings.Organizer.Form)

I can do that while I'm doing development on other parts but I'm going to need that empty constructor in a couple of weeks.

BTW, the same thing happens if I create any constructor that doesn't take a Context and doesn't have a matching base constructor with the same parameters.
Comment 2 Jonathan Pryor 2011-12-08 22:12:35 UTC
Fixed in 6679dfc62eae462b5acc9deb095d0fa41786f80b.

As ar as comment #1 goes, with the current fix we'll skip generating a default constructor for DrteView's default constructor, allowing the ACW to compile properly.