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.
Every couple weeks, I log into my computer, fire up Xamarin studio and all of my images are no longer associated to the project. I have to add them all back in. Of course I miss some when I do this which results in a ton of regression errors when we go to QA.
Actually this is not the issue I was having weeks ago. This issue appears to be related to the Alpha version of the Scandit component. They are working with Xamarin on the component and I am an alpha tester for them.
Here is the email i sent to them...
Steps to reproduce:
1. Create the Scandit component locally by running the command line
2. Go to edit components and add the component in. So far so good. Works
3. Run the project with any code which uses the UIImage constructor to
create an image from the bundle. In this example below I am creating
items in my UITableView.
MenuItem onePointThree = new MenuItem();
onePointThree.Name = "Order Item Search";
onePointThree.Icon = new UIImage("search2.png");
4. Run the project and notice that no images appear. Loading the images
at runtime seems to be the culprit.
5. Remove the component reference.
6. Run the project now and the images are back.
Marking invalid for now since it sounds like an issue with the component. If further investigation determines it to be a Xamarin Studio or Xamarin.iOS bug, please reopen.