I'm trying to upgrade to the latest IOS-Unity plugin and I keep getting this compilation error:
Assets/Scripts/Analytics.cs(38,16): error CS0012: The type
System.Threading.Tasks.Task' is defined in an assembly that is not
referenced. Consider adding a reference to assemblyUnity.Tasks,
Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'
It's worth noting that before this error it complained about a duplicate UnityCompat.dll file (defined in both Firebase/Plugins and Parse/Plugins -- I ended up removing the one in the Parse directory, but I have tried the opposite as well).
Any pointers would be great. Also worth noting that this happened after removing obsolete files from the PlayServices plugin when prompted.
Answering my own question (from https://groups.google.com/forum/#!topic/firebase-talk/2w1Lk62VIcg)
Parse/Plugins/Unity.Tasks needs to the enabled for compilation (using Unity's Inspector)
Parse/Plugins/Unity.Compat needs to be disabled
I had a similar problem and resolved it by following the documentation :
(https://firebase.google.com/docs/unity/setup#set_up_environment)
Assets > Play Services Resolver > Version Handler > Update to enable the correct DLLs for your project.
Related
I have an old WPF/HelixToolkit/SharpDX project from 2016 that I started working with. I was having some viewport issues and thought they might be cured by updating HelixToolkit & SharpDX packages. Unfortunately, after the updates my project will no longer compile.
I tried Build->Clean and Rebuild All, but no joy. Still getting these errors:
Severity Code Description Project File Line Suppression State
Error The "SharpDX.Toolkit.EffectCompilerTask" task could not be loaded from the assembly \SharpDX.Toolkit.CompilerTask.dll. Could not load file or assembly 'file:///C:\SharpDX.Toolkit.CompilerTask.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. MyWPFMagViewer2
Severity Code Description Project File Line Suppression State
Warning The referenced component 'SharpDX.Toolkit.Compiler' could not be found. MyWPFMagViewer2
I'm really hoping it's something simple, but I don't have a clue what it might be. Can anyone help?
TIA,
Frank
I never found an answer to this problem, but I was able to work around it by re-cloning my project from GitHub, and not updating SharpDX
Frank
I have an old Xamarin project which compiled OK a year or so ago, in VS2017.
Today I tried recompiling, but I am getting this error:
Can not resolve reference: SMDiagnostics, referenced by Mono.Android > System.Runtime.Serialization. Please add a NuGet package or assembly reference for SMDiagnostics, or remove the reference to Mono.Android
AFAIK I haven't changed anything in my project, although of course Windows10 will have been updated.
There are several options for Mono.android in the reference manager:
I have tried removing the ref and re-installing a couple of them, with no improvement.
Furthwermore, I have searched for 'SMDiagnsotics' in the project and found no mention of it anywhere.
Now aded a new reference to SMDiagnostics; that issue resolved but moved on to a new error. Strange though how unchanged project source can result in multiple errors after a short break of not maintaining it.
I have referenced HttpStatusCode via System.Net in a Portable Class Library.
I then need to reference that status code from a MonoDroid project that includes that PCL. I understand that the System.Net namespace exists in the System DLL for MonoDroid and this has been included.
However this results in a build error:
CS0012: The type 'System.Net.HttpStatusCode' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Net, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes'.
Now I realise there are strong namespacing issues with referencing the PCL System.Net, and that there is a Shim DLL in MvvmCross.PortableSupport that is supposed to resolve this issue. I have included MvvmCross.PortableSupport.3.0.8.1\lib\MonoAndroid16\System.Net.dll to the MonoDroid project, but I still get the same error.
What am I missing?
Thanks!
Matthew
So I was unable to determine the underlying issue, but the workaround was to avoid referencing the System.Net symbol from the native code via the Portable Class Library (framework 104 btw)
In this instance, instead of exposing the HttpStatusCode from the PCL, I exposed it as an integer and thus worked around the problem.
Stuart is away on holiday at the moment but he suggested this as a workaround and it works fine. It's not clear why the shim System.Net.Dll that MvvmCross includes isn't redirecting the reference correctly to the native library.
I've got an error when I try to build a project (monodroid/mvvmcross).
This is the message error :
Error 37 The type 'Android.App.ListActivity' is defined in an assembly that is not referenced. You must add a reference to assembly 'Mono.Android, Version=0.0.0.0, Culture=neutral, PublicKeyToken=c4c4237547e4b6cd'.
Someone have an idea how to solve this problem ? This is strange because there wasn't this error before.
This error is located in MvxDialogActivityView.cs (cirrious.MvvmCross.Dialog.Droid)
I think your problem is that parts of your code is compiled against Xamarin.Android while others are compiled against Mono for Android.
See: http://forums.xamarin.com/discussion/1476/changes-to-assembly-strongnames-in-xamarin-android-4-6-0
You will need to recompile all parts of your application to target the same version of Xamarin's products.
My lib directory only has 1 jar. xml-apis 2.8.1. When I remove it, everything compiles. This is the error I get:
java.lang.LinkageError: Class org/xml/sax/SAXParseException violates loader constraints
Any idea what's going on?
The xml-apis classes are included in the JRE. This issue is also known as being part of the "jar hell" problem, and - in the JVM space - typically occurs with XML libraries being included multiple times in the classpath, i.e. from the JRE rt.jar, by the application server or as a dependency of third-party libraries. This leads to LinkageError exceptions as the one provided above.
This is one example that describes how to solve this issue in Grails 1.3.7.