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.
Steps to reproduce:
1. Open VS 2010/VS 2012
2. Open the application APIDemo
3. Set the target framework of the application as Android 4.2 JellyBean
4. Build the application.
5. Observe that 1 build error appears:
Actual result: The aplication APIDemo does not build successfully with the target framework as Android 4.2 JellyBean. as it gives one error on build: "Error1:'EGLConfig' is an ambiguous reference between 'Javax.Microedition.Khronos.Egl.EGLConfig' and 'Android.Opengl.EGLConfig' C:\Users\jatinvm\Desktop\4.2Testing\monodroid-samples-master\ApiDemo\Graphics\CubeRenderer.cs 89 43 ApiDemo"
Below is the build output for the same:
Expected result: The application should build and run successfully.
Windows 7 and 8
VS 2012/VS 2010
MFA 188.8.131.52430532 - 432af4490489b682f622f391539e628052784024
Regression status: Not a regression, as this feature was not available with the stable version of MD and MFA.
Note: The application builds successfully with the target framework as Android 4.1 and lower, the issuen exists only with the target framework as Android 4.2 JellyBean.
Fixed in git master.
We have verified this issue with following builds:
mono-android-184.108.40.206769865 - e785fc9cbf20440d09988327bdaf614804d55a21
The issue still exists, as the application does not build with the target framework set as 4.2 Jellybean.
Note: The application build successfully when build on MD 3.0.6 beta using the same version of MFA.
Hence, reopening this issue w.r.t to VS 2010/VS 2012
Re-opening based on comment 2 "Hence, reopening this issue w.r.t to VS 2010/VS 2012"
Fixed in https://github.com/xamarin/monodroid-samples/commit/b019a60c1bd56261af6324075b0492a9b388ca4b
ApiDemo now has a TargetFramework of v4.2.
Today we have checked this issue on following builds :
VS 2010 / 2012
App info : monodroid-samples-60ecd1df4a9964cc33a891ee73a0eeffb7fb6daf
Now we are able to build and run the application on device and emulator successfully with target framework set as Android 4.2 JellyBean.
Hence closing this issue. Changing its status to verified