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.
Created attachment 14319 [details]
a screenshot of the problem in XS 6 preview 3
With the Xamarin Studio 6 (preview 3) on Mac we are getting a ton of warnings that show up as squiggly lines underneath types in the text editor. I found out that it is because of the following situation, which may not be something you guys test for. To reproduce:
1. Create an iOS project.
2. Create an iOS Today Extension project.
3. Create a shared project and reference the shared project from the iOS project and the iOS Today Extension project.
4. Create a couple of classes in the shared project. Reference one of the classes in the shared project from another class in the shared project.
5. Build. Notice that everything is fine.
6. Now create a reference to the iOS Today Extension Project from the iOS project. This is necessary as stated here: "The Container app must have a reference to the Extension." https://developer.xamarin.com/guides/ios/platform_features/introduction_to_extensions/
7. Build again. Notice that now warnings appear for classes in the shared project that reference other classes in the shared project. That's because iOS sees those types twice: once for the iOS project itself, and once for the iOS Today Extension project. Interestingly the warnings do not show in the build output; they only show up in the Xamarin Studio text editor.
See the attached screenshot.
About Xamarin Studio
Version 6.0 (build 1752)
Installation UUID: ef4eb426-7861-41a8-860d-6c0e3c8baa5f
Mono 4.2.1 (explicit/6dd2d0d)
GTK+ 2.24.23 (Raleigh theme)
Package version: 402010102
Apple Developer Tools
Xcode 7.1.1 (9081)
Version: 126.96.36.199 (Business Edition)
Build date: 2015-12-08 16:20:29-0500
Version: 188.8.131.52 (Business Edition)
Android SDK: /Users/ncook/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.0.3 (API level 15)
4.4 (API level 19)
5.0 (API level 21)
SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.1
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
Xamarin Android Player
Location: /Applications/Xamarin Android Player.app
Version: 184.108.40.206 (Starter Edition)
Release ID: 600001752
Git revision: 82f4627b45b35ff833ffd6fe8dcd8601b595b0a2
Build date: 2015-11-04 11:57:18-05
Xamarin addins: 22dfcd8727ec2315920dc0c22d77470698c2b839
Build lane: monodevelop-lion-roslyn
Mac OS X 10.11.1
Darwin Nate-Insightly-MacBook-Pro.local 15.0.0 Darwin Kernel Version 15.0.0
Sat Sep 19 15:53:46 PDT 2015
Created attachment 14321 [details]
sample solution with projects demonstrating the problem
Created attachment 14322 [details]
Screenshot of the problem in the sample project
Make sure you switch to the iOS context in the shared project when you are in MyOtherClass in the sample project to see the problem.
Fixed in version 220.127.116.1106 (master)
Author: David Karlas??
Commit: 1ea0b403d378a1b5ef8f63d49204d44928f97bf0 (xamarin/md-addins)
Included in Commit: 16bd222c073bfa96a76d4ede80fb9ac65b041239 (mono/monodevelop)
This bug has re-appeared in the latest Xamarin Stable. Created a new bugzilla here: https://bugzilla.xamarin.com/show_bug.cgi?id=44746