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.
My project was ok, I deleted bin and obj directories (may be coincidential) and afterwards I started receiving this message:
1>C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(640,2): monodroid error XA0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: Ionic.Zip.BadCrcException: CRC error: the file being extracted appears to be corrupted. Expected 0xABD280D6, Actual 0x1EDCA6CD
no extra information given.
We have deleted bin and obj directories from android app and able to build and deploy it successfully without any errors.
Could you attach a small complete project that demonstrates this behavior? Also add sub steps (if any) that are not in description.
Please add the logs from the following places:
On XS IDE Log Location: XS>Help> Open Log Directory> IDE.log file (with latest
If using VS, IDE log: Location: C:\User\AppData\Local\Xamarin\Log\
(Devenev file with latest timestamp)
XS 4.2.3(build 60)
sorry, I reported the bug because the program told me so. After rebooting the computer due to windows update, the project compiled again. Maybe the specified file was locked by the system for some reason.
Unfortunately I can't provide any extra information, as the problem disappeared long ago.
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!