Hello

This situation happens around line 3829 of the master build script (the "build.cmd" file in the builder's install directory). I suspect the "xcopy" command to fail.

Let's try this: open the "build.cmd" file with your favourite text editor, go to line 3825 and replace this block:

% build.cmd lines 3825-3830
		rem // copy the Swift module files in the framework's Modules subdirectory if we have one
		call :test_if_dir "!TARGET_BUILD_DIR!\!PRODUCT_NAME!.swiftmodule" && (
			echo  + Exporting !PRODUCT_NAME! Swift module...
			mkdir "!OUTDIR!\Modules" > nul 2>&1
			xcopy "!TARGET_BUILD_DIR!\!PRODUCT_NAME!.swiftmodule" "!OUTDIR!\Modules\!PRODUCT_NAME!.swiftmodule" /d /e /i /y > nul || ( set ERROR_TAG=20250925131400& goto :exit_error )
		)
%

with this one:

% build.cmd lines 3825-3830 (patched)
		rem // copy the Swift module files in the framework's Modules subdirectory if we have one
		call :test_if_dir "!TARGET_BUILD_DIR!\!PRODUCT_NAME!.swiftmodule" && (
			echo  + Exporting !PRODUCT_NAME! Swift module...
			mkdir "!OUTDIR!\Modules" > nul 2>&1
			mkdir "!OUTDIR!\Modules\!PRODUCT_NAME!.swiftmodule" > nul 2>&1
			copy /y /b "!TARGET_BUILD_DIR!\!PRODUCT_NAME!.swiftmodule\"*.* "!OUTDIR!\Modules\!PRODUCT_NAME!.swiftmodule\" > nul || ( set ERROR_TAG=20250925131400& goto :exit_error )
		)
%

Just copy/paste. Save and exit. Rebuild. Does it fix it?

It should be immediate. There is clearly something wrong here.

Would you mind sending me this Xcode project so I can reproduce the problem ? Send it to pm at this domain. Delete the "build" and "Pods" directories to save space in the zip.

Alternatively, if you feel confident enough, you try inserting blocks of

% build.cmd
			echo Reached line XXX
			pause
%

statements (with X equal to the line number in the script where you're pasting these blocks), so that when the build script executes near these lines, you can follow its path down to the line that blocks exactly. When you've reached it, see if it has "null redirections" (" > nul" and/or "> nul 2>&1"); these hide the output of the command that's being run. Remove these redirections (simply remove the "> nul" string bit) and let the script run again: hopefully the failing command will display something.

Let me know

So the problem is the "dash -c" call not returning. That's a bug I must fix, but I must understand *why* it behaves this way.

By disabling module map generation like you did in your changes (commenting out the lines that look for umbrella header files) you won't be able to build mixed-source (Swift+ObjC) projects, and many of them are nowadays. So your fix didn't really fix things, but congratulations for the attempt at debugging it on your side.

Yes, both problems are linked. There is definitely *something* in your Xcode project that makes the build script derail, and I'd love to be able to reproduce that in vitro to understand the cause of the problem and fix it properly. Can't you really send me that Xcode project ? Confidentiality is guaranteed (I can sign a NDA if necessary). Not being able to reproduce the problem makes the whole process a lot harder.

If you prefer to continue debugging it on your side, you may attempt a fresh build (all caches cleared) in verbose mode, by holding the Shift key when you click the Build button. This will display a lot more info, including the command interpreter's environment variables at each relevant step of the build. I suspect one of them might contain something that isn't well digested by the build script. Also, when debugging something, it is essential that you stay focused on the first error that shows up (warnings excluded), because errors usually cascade and it's no point wasting time trying to "fix" the final error when it's being caused by an earlier one.

Thank you for having sent me the project.

I am surprised - I could build your project successfully, the error doesn't show up.

I just made one observation though: you don't use CocoaPods (I see you renamed the Podfile in Podfile.bak), so while adding the Firebase frameworks by hand, you must also add the -ObjC linker flag as per Google's instructions. You also need to copy the frameworks yourself in the compiled app using a pre-packaging script (i.e. copy the necessary Firebase *.framework directories in build\Release-iphoneos\Unity-iPhone\TacTiles.app\Frameworks).

But this does not explain the error you're having, because your error occurs before that step.

I suspect something in your command line environment variables that's not digested by the build script. It might be something related to your computer's locale (language settings).

The build script expects path separators to be the '\' character, but in some countries I have been told that another character is used as path separator. This might be the problem.

As it turns out I cannot reproduce that on my computer, I will need your help to debug it.

Please do a full rebuild in *verbose mode* (hold down the Shift key when you click Build), then send me the resulting log file. If you're concerned about privacy (the information displayed may contain your private key passphrase), you may send me the build.log file by email instead of posting it on the forum.

These flags are good.

But the log you posted isn't the full log. It's as if you copy/pasted the contents of the window. The full build log is much longer, it's stored in the "build.log" file at the root of the Xcode project. When you build in verbose mode, in that file there will be a dump of your environment settings, and that's what I'm interested in seeing.