-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Description
Hi Guys,
This one's strange.
I originally had a build of Newtonsoft.Json.MonoDroid in a solution I'm working on. I noticed your MonoDroid build includes the same library, but named Newtonsoft.Json.Android. So I removed my version and included yours.
The solution built fine, but deploying fell over with a message that Newtonsoft.Json.MonoDroid could not be found. It worked when I added my reference back in.
After trying for ages to coerce the thing into a successful deployment, I think I've discovered a quirk in Mono for Android. You see, despite your binary being named Newtonsoft.Json.Android, the assembly is still named Newtonsoft.Json.MonoDroid, which Mono for Android must be looking for when it attempts to package the solution files.
Has anyone else encountered this?