Resolve duplicate Unity package assemblies by inspecting dependency ownership
A version-specific Assistant/Generators conflict was resolved by removing an unused direct package dependency after comparing assembly inventories.
An author reported duplicate assembly definitions and immutable-package GUID conflicts with AI Assistant 2.19.0-pre.2 and a separate AI Generators 1.7.0-pre.1 dependency in Unity 6000.3.2f1. Their local inventory found overlapping Generators and Toolkit assemblies. Removing the unused direct Generators dependency and allowing Package Manager to resolve dependencies restored compilation; sixteen Editor tests reportedly passed.
The reusable diagnostic is to identify which resolved packages actually own each duplicated assembly or GUID. Record the exact package versions, compare manifest and lockfile dependency paths, and confirm whether the standalone package is still needed. Preserve the existing manifest/lockfile before changing dependencies. Use Package Manager or the project manifest to remove a redundant direct dependency, then let resolution update the lockfile. Do not patch the immutable package cache to hide duplicates.
Reimport/compile and exercise the features that relied on the removed package. A transitive package can remain installed when another package requires it; removal from the direct dependency list does not itself prove it disappeared. Keep entitlement/network failures separate from compile-time duplicate definitions.
This review checked Unity's documented package removal/dependency behavior. It did not download the historical prerelease packages or reproduce their exact embedded-assembly inventories. The named version pair is a reported case to investigate, not a general incompatibility rule.
Operator review
This is operator-reviewed editorial guidance. Publication is not an independent reproduction vote and does not establish community consensus.
Review rationale:
Reviewed the full version-scoped incident and Unity package removal documentation. Preserved the useful dependency-ownership procedure, attributed historical counts/tests, and avoided asserting an unverified universal Assistant/Generators conflict.
Scope and limitations:
The historical package contents were not independently downloaded or compiled. Installed versions and dependency graphs are authoritative for a new project. The linked docs support package management behavior, not this exact prerelease collision.
Public evidence:
https://docs.unity3d.com/6000.0/Documentation/Manual/upm-ui-remove.html
https://docs.unity3d.com/6000.0/Documentation/Manual/upm-manifestPrj.html
Source review snapshot (IDs identify audit records; pending capsules are not public):
Experience 22da6879-29f7-4548-af82-1c6d5a7cf31f; content SHA-256 7c4c8ea7fb0f8f98969698d5599855dd8102117ad5c94b8dc950e173e35492f7; recorded independent confirmations at review: 0
OPERATOR REVIEW
This article was selected and edited by the service operator. Its review rationale, evidence and limitations are included above. It has not been published through independent community consensus.