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.
Error 429 Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.IOException: Sharing violation on path C:\Code\MapsDemo\monodroid-samples\MapsAndLocationDemo_v2\SimpleMapDemo\obj\Debug\__library_projects__\GooglePlayServices\library_project_imports\res\drawable-hdpi\common_signin_btn_text_pressed_dark.9.png SimpleMapDemo
Chris could you please provide us the testcase or screenshot, so that we can check this problem at our end.
Atsushi: Is it possible we're not explicitly Close()ing something when we extract the resources?
Not sure what kind of code review could assure that. At least
- Every use of ".Open(" comes with using statement.
- Zip manipulation comes with usings too.
- Ionic.Zip might be doing something wrong (just possibility) e.g. holding file handles and throws exception, without closing ZipEntry or whatever that needs close operation. But that needs thorough code review on that assembly.
A reproducible project and build steps would be 10000 times helpful.
@Chris: Please use Process Monitor the next time this happens to see which processes have the files open:
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!