SDK Installation causing lots of fatal issues.

[cryptogrounds]

Please fill in the following fields:

Unity editor version: 2019.3.11f1 and 2019.3.0f6 maybe it occurs in more?
Firebase Unity SDK version: 6.14.0
Source you installed the SDK (.unitypackage or Unity Package Manager): FirebaseAnalytics.unitypackage (Dotnet4)
Firebase plugins in use (Auth, Database, etc.): Analytics
Additional SDKs you are using (Facebook, AdMob, etc.): Admob
Platform you are using the Unity editor on (Mac, Windows, or Linux): Windows 10
Platform you are targeting (iOS, Android, and/or desktop): All three
Scripting Runtime (Mono, and/or IL2CPP): IL2CPP for iOS/Android, Mono for PC/Mac Standalone

Please describe the issue here:

So I have three issues:
First one is a bunch of errors just whenever I load into the project, or import, etc. The errors are: https://hatebin.com/yfsujgvldd

Second is not having the ability to go to Window>Firebase>Documentation, I get an error for that: https://hatebin.com/dsrtwcoqfj

Lastly, whenever I try to build for Android, unity's process just starts to not respond when the build phase it at "Building Scene 0: "

Please answer the following, if applicable:

Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)? Yes and an empty project

Extra Questions:
Have I tried importing the package again? Yes
Have I tried building without the SDK? Yes and it works perfectly fine
Have I tried reimport all? Yes
Have I tried relaunching Unity? Yes
Do I have both iOS and Android modules installed? *Yes

What's the issue repro rate? 100%

[cryptogrounds]

Bump, really want to be able to use firebase.

[chkuang-g]

I was not able to reproduce on Mac so it could be a Windows specific issue.

According to your log, there seems to have two issues:

• Could not resolve field token - This looks like EDM4U libraries are not enabled properly. A quick workaround with this:
  1. Find all libraries (.dll) under Assets/ExternalDependencyManager/Editor/
  2. In Inspector window, check "Editor" platform and click "Apply"
• jar not found, C:/Program Files/Unity/Hub/Editor/2020.1.0a7/Editor/Data/PlaybackEngines/AndroidPlayer\OpenJDK - This looks like a path issue.
  https://github.com/googlesamples/unity-jar-resolver/blob/6cef4b5f4a12dc7545626676206e52f502c8289b/source/AndroidResolver/src/JavaUtilities.cs#L55
  https://github.com/googlesamples/unity-jar-resolver/blob/6cef4b5f4a12dc7545626676206e52f502c8289b/source/AndroidResolver/src/PlayServicesResolver.cs#L858
  Judge by the code here, there might be some issue with Unity SDK here
  https://docs.unity3d.com/ScriptReference/BuildPipeline.GetPlaybackEngineDirectory.html
  Need a bit more dig for this.

Thanks for reporting this.

[cryptogrounds]

Ok, I will give that a try for the .dll files right now.

[cryptogrounds]

here is all the spam i get after i check editor in all the .dll files in the folder

and yeah unity still freezes on build, thought i might as well add that again since this is my third time trying to import it :(

[patm1987]

Hi @NightStormYT ,

Sorry that it took so long to get to your question!

My first request would be that you try the new 6.15 SDK - but I don't want to make you wait longer before giving you some more things to look at.

Looking through your logs, I'm noticing lines like:

Failed with exception GooglePlayServices.JavaUtilities+ToolNotFoundException: jar not found,

So a few things. First, I'd suggest trying to reinstall Java/Android SDK via Unity Hub:

(I see in your error log that you do have it setup)

And I'd make sure that you are using the built in Java SDK:

There have been reports about needing to toggle this checkbox in newer versions of Unity.

If you have a system wide Java installed - you may try using that (or temporarily clearing the $JAVA_HOME variable). There are some other suggestions in this forum post regarding this option in Unity.

Another thing I might suggest trying is clearing out your Temp/ and Library/ folders with Unity closed (Temp/ should actually go away when you close Unity). If you're using .meta files (default), it will just regenerate itself automatically and sometimes clears up funky project-level issues.

Let me know if any of those work - or if you resolved it on your own since posting this issue!

--Patrick