Bug 23887 - Missing assembly....
Summary: Missing assembly....
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.18.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2014-10-16 17:29 UTC by Jose Gonzalez
Modified: 2017-08-07 20:50 UTC (History)
3 users (show)

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 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.

Related Links:

Description Jose Gonzalez 2014-10-16 17:29:15 UTC

The following error keeps happening:

C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2,2): Error XA0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: Could not load assembly 'eCandidus.A.LoDe, Version=, Culture=neutral, PublicKeyToken=null'. Perhaps it doesn't exist in the Mono for Android profile? (XA0000) (eCandidus.A.CLLink)

Sometimes if I remove the refence to eCandidus.A.LoDe and the re-add it, the problem goes away. If it does not, I try everything including restart computer until it works.
Comment 1 Sunil Kumar 2014-10-17 11:37:38 UTC
Could you please provide us test steps/Sample to reproduce this issue?
Comment 2 Jon Douglas [MSFT] 2017-08-07 20:50:10 UTC
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!