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 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.
I have to delete the directory ~/Library/Caches/Xamarin before building and running the app from Visual Studio. If I don't, old code is actually deployed to the simulator. Incremental building is not switched on as this was the first thing I suspected.
I think there is a time zone problem that causing this, because I see some where modification dates on the files in the ~/Library/Caches/Xamarin directory. For example, I rebuilt my solution at 12:58. On Windows, I see the following:
I then checked ~/Library/Caches/Xamarin/Build/app/<id>/assemblies
**Notice the two hour time difference. This correlates with the difference between SAST (my timezone) and GMT.
The problem is caused by the contents of ~/Library/Caches/Xamarin/Build/app/<id>/output/temp/mtouch-cache/build.
The cashed version of the app.exe in here has the date of 12:38, which is a previous build, but it looks like this is being used as it has a later time.
This problem occurs on all three our workstations, and it started after the upgrade to Xamarin.iOS 1.3.250. On the Mac, I have the latest stable version installed (reinstalled this morning to make sure). Xamarin.iOS 188.8.131.52.
I just installed version 1.4 beta for Visual Studio, and the problem is still there. In which version will this be fixed?
This fix will be part of the next public release. It did not make it into 1.4.x