"External Dependency Manager" menu option missing

[golergka]

Please fill in the following fields:

Unity editor version: 2019.3.6f1
External Dependency Manager version: 1.2.144
Features in External Dependency Manager in use (Android Resolver, iOS Resolver, VersionHandler, etc.): -
Plugins SDK in use (Firebase, Admob, Facebook, etc.): Facebook, Firebase
Platform you are using the Unity editor on (Mac, Windows, or Linux): Windows
Platform you are targeting (iOS, Android, and/or desktop): Android
Scripting Runtime (Mono, and/or IL2CPP): IL2CPP

Please describe the issue here:

1. Install External Dependency Manager unitypackage.

Expected result:

EDM4U adds the registry to Packages/manifest.json under your current Unity project folder.

You can also manaully add this registry later using the Assets > External Dependency Manager > Unity Package Manager Resolver > Add Registries or Window > Google > Game Package Registry > Add To Project menu options.

As per https://firebase.google.com/docs/unity/setup#add-sdks-upm

Actual result:

There's no "External Dependency Manager" optin in "Assets" menu.

Please answer the following, if applicable:

What's the issue repro rate? (eg 100%, 1/5 etc) 100%

[stewartmiles]

@golergka did you disable the Version Handler component? If so, EDM won't enable other parts of the plugin. I recommend taking a look under Assets > External Dependency Manager > Version Handler > Settings. If you want to force enable components of the plugin you'll need to select all DLLs under Assets/ExternalDependencyManager, select Windows > General > Inspector then check Editor and apply in the Select platforms for plugin section.

[golergka]

did you disable the Version Handler component?

No, I haven't. As I described in the original issue, I only installed the unity package,

I recommend taking a look under Assets > External Dependency Manager

There's no External Dependency Manager menu in Assets whatsoever.

[stewartmiles]

It sounds like the Google.VersionHandler.dll (which bootstraps the installation) was disabled somehow.

If you want to force enable components of the plugin you'll need to select all DLLs under Assets/ExternalDependencyManager, select Windows > General > Inspector then check Editor and apply in the Select platforms for plugin section.

Alternatively, delete the plugin from your project and reimport.

[nwmqpa]

I can confirm the problem still appear on External Dependency Manager version 1.2.153, with Unity 2019.3.5f1.

All dlls but ExternalDependencyManager/Editor/Google.VersionHandler.dll are not selecting Editor as a platform for the plugins

EDIT: My issue got resolved after I reinstalled FirebaseAuth manually to correct compilations problems

[doom-goober]

To expand on @nwmqpa 's problem. If you follow the instructions on https://firebase.google.com/docs/unity/setup it tells you to first install EDM then uninstall your old Firebase packages, do somethings with EDM, then reinstall Firebase packages. If you do this in this order, it will trigger a build break in Unity (because the Firebase packages will not be present) and the build break will prevent EDM from appearing in the menu. So, you must do step 3 first (reinstall Firebase Packages) to stop the build break and get the EDM back into the menu.

[fmoyano]

Hi, I'm having the same problem in version 1.2.156 (Unity version 2019.2.19f1). As soon as I import the plugin I'm getting the following error in the console:

NullReferenceException: Object reference not set to an instance of an object
UnityEditor.EditorPluginImporterExtension+EditorProperty.Reset (UnityEditor.PluginImporterInspector inspector) (at /Users/builduser/buildslave/unity/build/Editor/Mono/ImportSettings/EditorPluginImporterExtension.cs:37)
UnityEditor.Modules.DefaultPluginImporterExtension.RefreshProperties (UnityEditor.PluginImporterInspector inspector) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Modules/DefaultPluginImporterExtension.cs:132)
UnityEditor.Modules.DefaultPluginImporterExtension.OnEnable (UnityEditor.PluginImporterInspector inspector) (at /Users/builduser/buildslave/unity/build/Editor/Mono/Modules/DefaultPluginImporterExtension.cs:109)
UnityEditor.PluginImporterInspector.OnEnable () (at /Users/builduser/buildslave/unity/build/Modules/AssetPipelineEditor/ImportSettings/PluginImporterInspector.cs:450)

The previous version of the plugin that I had was still using the Play Services Resolver name, and what I did was basically delete this folder and import the latest version. Did I do wrong?

EDIT: when I selected Editor as target platform for all .dlls in the package, it worked. However, I feel a bit of discomfort having to do this manually, as it seems to be something wrong with my project... Is it normal that this is happening?

[patm1987]

The old platform associations might be persisted in .meta files if you left those in place (ie: just deleted the DLLs) or in your Library directory. I find that the Library directory is typically safe to delete (if you use meta files in your version control settings).

If you'd like to re-import just for piece of mind, you could try closing Unity, deleting EDM4U, Deleting the Library folder, then re-launching Unity and re-importing EDM4U to see if the dll's come back with the correct platform association.

[google-oss-bot]

Hey @golergka. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!