Unity 6 'Default' is not a valid subtarget for the Standalone build target

[brentopc]

Running a pretty basic windows build returns the error 'Default' is not a valid subtarget for the Standalone build target. I am unable to get around this error.

I believe it is due to (int)StandaloneBuildSubtarget no longer contains Default it is now only Player and Server.

[ArielJurkowski]

I confirm I have the same issue on the latest dev codebase with Unity 6. Out of curiosity, it did build the project after I changed the obsolete methods in BuildProject.cs and brute-forced NamedBuildTarget.Standalone with StandaloneBuildSubtarget.Player in a few places, but I’ll wait for a proper fix.

[robinnorth]

Thanks for the reports, @brentopc and @ArielJurkowski! I've been able to reproduce this using the v8.0.0-pre.1 release on Unity 6, so will target v8.0.0 for a fix when I have some time to look into it further.

[NobelImmerser]

@ArielJurkowski or @robinnorth I'm hitting this also, can you share how you set StandaloneBuildSubtarget to get it to work?

[jason-storey]

Hate to be a pain and bump a topic but is there any news on this one? I'm setting up some project build pipelines and aim to do some tutorials on them. I would love to do it through SUB but its actively broken at the moment with this issue.

Great job on the build tools in general though. I only found them recently and the inspect tooling is very elegant and clean!

[NobelImmerser]

I'm curious too. I had to abandon this tool because of it.

[brentopc]

I am currently using this tool and do not have this issue anymore, the fix that was suggested has worked for me.

…

________________________________ From: TenasticImmerser ***@***.***> Sent: Tuesday, March 18, 2025 9:09:44 PM To: superunitybuild/buildtool ***@***.***> Cc: Brentopc ***@***.***>; Mention ***@***.***> Subject: Re: [superunitybuild/buildtool] Unity 6 'Default' is not a valid subtarget for the Standalone build target (Issue #153) I'm curious too. I had to abandon this tool because of it. — Reply to this email directly, view it on GitHub<#153 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXGEZVBBZHXLP3YPXG3ZQZT2VC7VRAVCNFSM6AAAAABVN62TAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZVGA2TMMJWHE>. You are receiving this because you were mentioned.Message ID: ***@***.***> [NobelImmerser]NobelImmerser left a comment (superunitybuild/buildtool#153)<#153 (comment)> I'm curious too. I had to abandon this tool because of it. — Reply to this email directly, view it on GitHub<#153 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXGEZVBBZHXLP3YPXG3ZQZT2VC7VRAVCNFSM6AAAAABVN62TAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZVGA2TMMJWHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[robinnorth]

@jason-storey I have started working on a fix for this, so hopefully it will be resolved soon. Thanks for the kind words about SuperUnityBuild!

[wallstop]

I'm very interested in using this. If you currently use this from Unity 6, it will corrupt your player state, the only fix being to delete the Library folder. This is very bad.

The mutation happening here is never undone. It looks like it should be undone here and maybe some other places.

I think part of the problem is that a lot of parsing/storage of the BuildTarget's SubTarget is defaulted to 0, which silently corrupts data, as 0 is a "valid" enum value (Default), so the rest of the code treats the lack of data as a presence of data, then does the wrong thing.

But @robinnorth, you're the expert, this is just my side analysis. Was going to try to submit a patch, but this looks pretty involved, as a lot of this data will be persisted already by users (BuildTarget.subTarget, in particular).

Would love to have this tool in my arsenal, it looks very useful. If you need manpower and have a rough design / guidelines for what the changes should be, happy to contribute back in a directed fashion, feel free to reach out to me here or over email.

[XeonG]

Forgot the last time this issue screwed over my project... anyway been months and was trying it again.. and yup

in the library folder deleting 'EditorUserBuildSettings.asset' seems to get rid of the error and save the hassle of library import (hopefully.. just gonna test a build and make sure, hopefully fixed

[Timo654]

Any news on Unity 6 support? I updated our game from 2022 to Unity 6, but SuperUnityBuild doesn't really work with it.

[Phildor92]

#155 I created this pull request with a fix

[XeonG]

#155 I created this pull request with a fix

That was the only thing that was needed ? That works? just this has bricked project before so don't want to try it again without knowing for

[Phildor92]

#155 I created this pull request with a fix

That was the only thing that was needed ? That works? just this has bricked project before so don't want to try it again without knowing for

From my tests, yes.

As for bricking your project, there is a way to get out of the compile loop. If you switch to a different build platform (I think I picked Web) from your build profiles and then restart Unity it should restart without issue, and then build (Windows) manually from the build (profiles) popup and it should be fine again. I'm not 100% on the steps to get out of it but I know it's possible (it took me some attempts to fix it and I only used the one project)