I know there’s an option in the UCB web interface to enable Development builds; however, is this possible via scripting as well, during one of the pre-build methods for instance?
There’s BuildOptions.Development, but to my knowledge this has to be passed directly into the BuildPipeline.BuildPlayer() call, which is not accessible to us in UCB.
Hm… I’ve tried setting this to true in my cloud build pre-build script, and when I print out the content of EditorUserBuildSettings.development it does show “True”; however, the resulting .apk is still not showing the “Development Build” watermark on-device.
Now the only workaround I know is to manage Development flag in two places (with UCB interface for cloud builds and with EditorUserBuildSettings.development for local builds).
AFAIK UCB overwrites the .development setting as I remember from my own experiments.
So the only thing that works if you have two UCB build settings, one for development and one for production. That’s what I do and I’m happy with that.
@ruslan_seleznov local builds should not be needed anymore due to UCB. If you need them for local test, you simply set it up the way you need it and build.
Everything else is up to UCB to have builds that are done in a certain way.
What if you want to change some other build setting, such as IL2CPP Code generation (faster smaller builds) or similar? This is not possible through UCB atm?