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.
Created attachment 9840 [details]
Full build log
The following error :
System.IO.FileNotFoundException: Could not load assembly 'Newtonsoft.Json, Version=, Culture=neutral, PublicKeyToken=null'. Perhaps it doesn't exist in the Mono for Android profile?
happens when trying to compile the XamarinStore sample on my PC (Win8.1, VS2013).
I tried the following without success :
- manually removing and re-adding JSON.net via the Component Store
- manually removing the component and adding the latest version of JSON.net via Nuget
It seems to be a problem with the characters used in the project directory Téléchargements. If you replace the é characters in the directory Téléchargements with plain ASCII e characters then the build will work. With the é characters in the directory the build seems to create another TÃ©lÃ©chargements directory on disk using the incorrectly encoded characters and this is being used as the path to Newtonsoft.Json.dll which is not in that directory so the build is failing.
Looking at a similar bug #3943 there seems to be a problem with the Android tools when non-English characters are used in the path. Although the error message from the bug #3943 is different from the error you are seeing.
*** Bug 31749 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 14918 ***