Bug 20509 - generator error if java class (SomeClass) and interface with I Prefix (ISomeClass) exist
Summary: generator error if java class (SomeClass) and interface with I Prefix (ISomeC...
Alias: None
Product: Android
Classification: Xamarin
Component: Bindings ()
Version: 4.12.4
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2014-06-10 08:41 UTC by Miljenko Cvjetko Mel
Modified: 2015-11-16 01:05 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:

Comment 1 Udham Singh 2014-06-10 09:16:04 UTC
I have checked this issue with the sample project attached in bug description and observed the same behavior mentioned in bug description. Please refer the screencast : http://screencast.com/t/k0xpnAV9

Environment Info :

Mac OS X 10.9.2
Xamarin Studio : 5.0 (build 878)
Xamarin.Android : 4.12.4 (Business Edition)
Xamarin.iOS : (Hash: fc6f56b)

=== Build Information ===

Release ID: 500000878
Git revision: bcd66920d963483e7d638a2339c4022fe035b529
Build date: 2014-05-27 17:36:26-04
Xamarin addins: da9064ce55b0fa90930a7c437a4cc1ae0e5c778c
Comment 2 Atsushi Eno 2015-11-16 01:05:59 UTC
There is no way to "automatically" avoid that kind of issue (with any approach it will break existing stuff). You have to play with Metadata.xml.