In my general build settings, I typically use my intended app name to also fill the “Description” field. However, when I do an all-desktop-targets build with the script, this field gets changed to read “XojoBuildPressed”.
I only thought a little of this, till I just noticed another effect. When observing a built app in Windows Task Manager, the process name is also “XojoBuildPressed”. To get what I want, I don’t use the script (and spend a little more time toggling between 64/32 bit and Linux ARM.) I have not checked this behavior on other targets.
Bug or feature? Or am I missing something?
I can tell you exactly what this is, because it is my doing.
Dim oldDescription as string = PropertyValue( "App.Description" )
PropertyValue( "App.Description" ) = "XojoBuildPressed"
// --- Figure out which architecture
Dim currentBuildArchiteture as integer = 9 // --- Universal
select case PropertyValue( "App.MacArchitecture" )
case "x64"
currentBuildArchiteture = 16
case "ARM64"
currentBuildArchiteture = 24
end select
// --- Tell Xojo to build using that architecture.
dim appPath as string = buildApp( currentBuildArchiteture, false )
PropertyValue( "App.Description" ) = oldDescription
I used this to workaround build problems with Xojo when they first started shipping ARM. My guess is that your script is somehow missing the line which sets it back to oldDescription once it’s done.
Mind you if you’re not using App Wrapper like this anymore, which I don’t think is needed, you can remove the entire section, so it doesn’t modift this field at all.
Thanks, I’ll take a look. Per our own past conversation, I did remove the AppWrapper stuff from the script, and instead just use its IDE script. But maybe I didn’t prune enough. This is a recent development, so that would make sense. 
1 Like
Thanks! That was what was causing the IDE to increment the non-release version once too often when I was building Universal + Windows version.