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.
If two projects have the same obj directory and one has an EmbeddedNativeLibrary, then it will be included in the other project too. Carefully building the projects one by one sometimes results in successful APK generation.
Even if the same obj folder is not a generally good idea, I would like to file this as a bug in the Xamarin.Android compiler, as we didn’t have any problem with this on any other platforms (including .Net and Xamarin.iOS).
4> obj\Release\__library_projects__\MonoGame.Framework\native_library_imports\armeabi\libopenal32.so (TaskId:157)
4> obj\Release\__library_projects__\MonoGame.Framework\native_library_imports\armeabi-v7a\libopenal32.so (TaskId:157)
4> obj\Release\__library_projects__\MonoGame.Framework\native_library_imports\x86\libopenal32.so (TaskId:157)
4> obj\Release\__library_projects__\MonoGame.Framework.Net\native_library_imports\armeabi\libopenal32.so (TaskId:157)
4> obj\Release\__library_projects__\MonoGame.Framework.Net\native_library_imports\armeabi-v7a\libopenal32.so (TaskId:157)
4> obj\Release\__library_projects__\MonoGame.Framework.Net\native_library_imports\x86\libopenal32.so (TaskId:157)
4>The "BuildApk" task failed unexpectedly.
4>System.ArgumentException: An item with the same key has already been added.
This is not currently supported.
I am marking this issue as NEEDINFO for the time being as the reproduction project noted in https://bugzilla.xamarin.com/show_bug.cgi?id=23057#c0 no longer exists. We will need a new reproduction to confirm this behavior still exists in latest Xamarin builds. If this has already been fixed, please feel free to add a comment indicating this.
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!