Bug 42088 - Build error when using MvvmCross
Summary: Build error when using MvvmCross
Status: VERIFIED DUPLICATE of bug 42082
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 4.1.0 (C7)
Hardware: PC Windows
: --- blocker
Target Milestone: 4.2.0 (C8)
Assignee: Bugzilla
Depends on:
Reported: 2016-06-22 18:01 UTC by vlad
Modified: 2016-08-22 18:23 UTC (History)
5 users (show)

Tags: BZSRC7
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description vlad 2016-06-22 18:01:58 UTC
# Steps to reproduce
Create a new Shared project (Android). Add MvvmCross nugets. Try to build.

# Expected behavior

# Actual behavior
Unexpected error. Cannot build no matter what I tried (clean caches, reinstall Xamarin).

# Supplemental info (logs, images, videos)
Error		Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: Ionic.Zip.ZipException: C:\Code\Research\Mvvm\Mvvm.App\Mvvm.App.Droid\obj\Debug\__library_projects__\MvvmCross.Binding.Droid\__AndroidLibraryProjects__.zip is not a valid zip file ---> System.TimeZoneNotFoundException: Exception of type 'System.TimeZoneNotFoundException' was thrown.

# Test environment (full version information)
Visual Studio 2015, Windows 10
Comment 1 vlad 2016-06-22 19:19:55 UTC
Rolling back to the previous version of Xamarin seems to have fixed the problem, for now.
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2016-06-23 20:49:35 UTC

*** This bug has been marked as a duplicate of bug 42082 ***