Question Warning "Cannot set deprecated build target 'OSXIntel'" with Default Build Script on Windows

Hello,
I use Unity 2021.3 LTS with build target "Windows" and Addressables.

When I press the Addressable build (NOT the Unity build) with the "Default Build Script" I always get the warning
"Cannot set deprecated build target 'OSXIntel'"

The bundle still works and loads properly, but I would like to remove the warning.

I don't know where the build target OSXIntel is from, my project build settings are the default settings after I switch to "Windows", which are:
Target: "Windows"
Architecture "Intel 64-bit"

 

I was having a similar issue to this, and it turned out to be one of my addons that was the cause of it - the now deprecated PEEK addon. Since it was deprecated I removed the addon and the issues went away.

That said, I'm not sure why the addon was causing this, but hopefully it's an avenue you can investigate.

 

Hmm it also happens in a fresh, empty project without any addons other than Addressables, which is the newest version, using the 3d URP template.

I will check if there is anything outdated in the template.

 

Hello,
I use Addressables version 1.19.19 but it shows as the newest for me, is the 1.20.5 not released to the public yet?

I get the warning for the Addressable bundles, there are multiple warnings / bundles (I assume that every scene has a own bundle?) here is one example:

Cannot set deprecated build target 'OSXIntel' for Assets/Exported/Default/defaultlocalgroup_assets_all_70726457b52e690f0bdd38012093e3b5.bundle
UnityEditor.GenericMenu:CatchMenu (object,string[],int)


Cannot set deprecated build target 'OSXIntel64' for Assets/Exported/Default/defaultlocalgroup_assets_all_70726457b52e690f0bdd38012093e3b5.bundle
UnityEditor.GenericMenu:CatchMenu (object,string[],int)

The Addressables Profile BuildTarget: [UnityEditor.EditorUserBuildSettings.activeBuildTarget] while the active build target is "Windows" (see above)

Btw I also tried to change to Android and build the bundles for Android and the warning didn't show up there, is there any chance that my windows build settings are messed up? Are there any other settings beside the Windows build settings (see first post) which could cause the warning?

 

I made a bug report (directly inside the Unity Editor) last week, but I don't know where it went or how to track it. The bug report dialog said it was successful and I will receive a email but I didn't hear anything since then.

 

A small update:
I sent you the report link with a PM, but today I found something new.

I use this for a "mod creator" project and made a custom profile which outputs the bundles in a custom path "BundleOutput" inside the Assets directory, so that it is easier to find for the user.

Backstory:
But this was a bit annoying because then the Editor would consider them as "assets" and did it's additional magic, like creating meta files. Then I found that I can add a "~" at the end, so Unity will ignore the folder, which makes sense in this case, because the user should only build and the copy the output to the "mod folder" which is inside the "main" game directory structur.

Anyways:
By "removing" the folder from the Assets directory (adding the "~" at the end), the warnings are also gone.

So I assume that the warning did not get output by the bundle build but maybe during the assets "import" which happend directly after the bundle build was done, because the bundles were built inside the Assets directory.

The default output location is outside the assets directory so, this would explain why it doesn't happen in a "default" setup.