Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Recently I had to track down a bug that occurred when building for release but not in debug builds. After some investigation it was clear that it would be a lot quicker to reproduce the problem if I could trigger the problem from a unit test. Attempting to build the unit test target with a release configuration did, however, give a compile time error.
Steps to reproduce:
- Create a unit test target.
- Add a unit test.
- Try to archive the test target for release.
Fails with the error message:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Error: Error executing task GenerateJavaStubs: The type 'Xamarin.Android.NUnitLite.TestResultActivity' needs to have a public default constructor. (ColleaguesApi.Tests)
Could you please confirm your full version information:
Xamarin Studio in OS X
"Xamarin Studio -> About Xamarin Studio -> Show Details -> Copy Information [button]"
If you could also attach a sample application that exhibits the problem that would be great!
Radek: Is it possible that the linker is removing the default constructor from Xamarin.Android.NUnitLite.TestResultActivity?
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!