Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. This issue has a workaround that will be available in the Known Issues section of the upcoming Addressables 4.x documentation. The details of that workaround will also be pasted below. If a project ever had Addressables 3.0.0+ installed and is then downgraded to an earlier version (for example, 2.11.1), the Content Directory build script and group template introduced by 3.0.0+ remain registered in the project's Addressable Asset Settings. Earlier versions of Addressables don't support these objects, which leads to the error described in the bug. To resolve this issue, remove the unsupported objects from the Addressable Asset Settings and clear the affected build reports as follows: 1. Open the Addressable Asset Settings Inspector Window > Asset Management > Addressables > Settings 2. Expand theBuild and Play Mode Scripts section. Select the Schema Driven Build entry, and select the minus button at the bottom of the list to remove it. 3. Expand the Asset Group Templates section. Select the Content Directory entry, and select the minus button at the bottom of the list to remove it. 4. If the Report window still logs errors, remove the affected build reports from the build report list in the left sidebar panel of the Addressables Report window. To do this, right-click in the window and select Remove Report to remove the selected report, or Remove All Reports to remove them all. We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
How to reproduce:
1. Create a new Unity project and install the 3.1.0 ver. Addressables package
2. Change the Addressables package version to 2.11.1
3. Go to Window -> Asset Management -> Addressables -> Groups
4. Right-click -> Create New Group
5. Observe the results
Expected results: Content Directory is not available
Actual results: Content Directory is available and adding it throws warnings
Reproducible with: 2.11.1 (6000.7.0a2)
Reproducible on: macOS Tahoe 26
Not reproducible on: No other environment tested
Note: The bug is reproducible even after fully reinstalling the package, if the 3.1.0 was ever installed in the project, the bug is reproducible
Full warnings:
Issues you vote on will appear here