Unity takes over mobile SDK dependencies from Google
Google is retiring the External Dependency Manager for Unity next month. Unity has forked it, shipped it as a first-party package and promised to keep the lights on.
Unity has announced External Dependency Manager (EDM), an official Unity package for handling native Android and iOS dependencies, distributed through the Unity Package Manager. It is built on a fork of Google's External Dependency Manager for Unity (EDM4U), which Google is deprecating on 26 October 2026. Unity says it has been working with Google to keep the handover smooth for both game developers and the teams maintaining the SDKs they rely on.
The problem EDM exists to solve is unglamorous and constant. Most mobile games ship with several SDKs for advertising, analytics, monetisation and push notifications, and each one drags its own native Android and Apple libraries into the build. With multiple SDKs in a project, a library conflict is close to inevitable, and resolving those clashes by hand is slow and easy to get wrong. EDM lets an SDK declare the libraries it needs in a plain text file, then orchestrates their inclusion so Gradle, CocoaPods or Swift Package Manager can do the actual resolving.
What changes for existing projects
For teams already on EDM4U, the move is meant to be boring. EDM is free for Unity 2022.3 and later, it reads the same XML dependency files that SDKs use today, and it can be installed from the Unity Registry inside the Package Manager. If EDM4U is already present, the Editor asks which dependency manager to use. Nothing is deleted, and developers can switch back from Assets > External Dependency Manager.
Removing EDM4U is a separate decision. Unity says to uninstall it once the project has moved across, but to leave it in place if it arrived through an SDK until that SDK itself supports EDM. The company expects existing projects to migrate without trouble and is asking developers to file anything unexpected through the Editor's built-in bug reporter.
Our opinion
A tool that quietly fixes build errors is never going to trend, so it is worth saying plainly that this is the kind of plumbing problem that ruins people's weeks. Google inventing EDM4U, maintaining it for years and then handing the keys to the engine maker is a sensible end to a dependency nobody wanted to own twice, and Unity having the package under its own roof should make it easier to keep it in step with Editor releases and platform changes.
The promise that matters is maintenance, not the fork itself. Unity's track record of keeping older versions alive while it chases the next big thing is mixed, and any developer who has watched a once-essential package go quiet will treat the words “actively maintained” with caution. Unity should publish a support window for EDM and stick to it, because a dependency manager that stops working is worse than no dependency manager at all.