Player artifacts
During a player build, the Addressables system copies the following files from the Library/com.unity.addressables/aa/<AddressablesPlatform> folder to the StreamingAssets folder:
| File | Description |
|---|---|
| Local AssetBundles | .bundle files according to group, profile, and platform settings. By default, these files are located in the BuildTarget subfolder. To change the build location of the AssetBundle files produced by a group, modify the Build & Load Paths setting. |
settings.json |
Contains Addressables configuration data used at runtime. |
catalog.json |
The content catalog used to locate and load assets at runtime if no newer remote catalog is available. For more information about catalogs, refer to Content catalogs. |
AddressablesLink/link.xml |
Prevents the Unity linker from stripping types used by your assets. For more information about code stripping, refer to Managed Code Stripping. In Unity versions 2021.2 and later, this file temporarily copies the AddressableAssetSettings.ConfigFolder, or the Assets/Addressables_Temp folder if no settings file exists. |
For a full list of platform names, refer to AddressablesPlatform.
Artifacts not included in the player
The following artifacts aren't included in a built player.
Remote content
Upload files used for remote content to a hosting server. By default these files are located in the ServerData folder.
| File | Description |
|---|---|
| Remote AssetBundles | .bundle files according to group, profile, and platform settings. By default, these files are located in the BuildTarget subfolder. To change the build location of the AssetBundle files produced by a group, modify the Build & Load Paths setting. |
catalog_{timestamp or player version}.json |
A remote catalog which when downloaded overrides the local catalog. This file is only created if the Build Remote Catalogs option in Catalog settings is enabled. By default the file name includes the timestamp of the build. To use a version number instead, specify the value of the Player Version Override in Catalog settings. For more information about catalogs, refer to Content catalogs. |
catalog_{timestamp or player version}.hash |
A file used to check whether the remote catalog has changed since the last time a client app downloaded it. Similar to the remote catalog file, this file is only created if the Build Remote Catalogs option in Catalog settings is enabled. To change the build location of this file modify the Build & Load Paths in Catalog settings. By default, the file name includes the timestamp of the build. To use a version number instead, specify the value of the Player Version Override in Catalog settings. For more information about catalogs, refer to Content catalogs. |
Content state file
The addressables_content_state.bin file is used to make a content update build. If you support dynamic content updates, you must save this file after each full content build that you release. Otherwise, you can ignore this file.
By default this file is located in Assets/AddressableAssetsData/<AddressablesPlatform>. Refer to AddressablesPlatform for all platform names. To change the build location of the file specify the value of the Content State Build Path in Catalog settings.
Note
Check this file into version control and create a new branch each time a player build is released.
Diagnostic data
Additional files can be created to collect data about the content build.
The files are:
Library/com.unity.addressables/AddressablesBuildTEP.json: build performance data. Refer to Build profiling for more information.Library/com.unity.addressables/buildlayoutreport: information about AssetBundles produced by the build. Refer to Build layout report for more information.