Debug: add binary diagnostics to find arm64 build output location

[m13v]

Adds ls of release dirs before binary check so we can see where arm64 binary actually lands on Codemagic mac_mini_m2 Xcode 16.4.

[greptile-apps]

Greptile Summary

Adds diagnostic output to the "Create universal app bundle" step in the Codemagic CI/CD workflow to help debug where arm64 binaries are placed during builds on mac_mini_m2 machines with Xcode 16.4.

• Logs BINARY_NAME variable and contents of all relevant build directories before binary verification
• Filters out build artifacts (.build, .o, .d files) and limits output to 30 lines for readability
• Removes redundant directory listing after error message since diagnostics now show this information earlier
• No functional changes to build process, purely diagnostic

Confidence Score: 5/5

• This PR is safe to merge - it only adds diagnostic logging with no functional changes to the build process
• The changes are purely diagnostic, adding directory listings before binary verification to help debug arm64 binary locations. No build logic is modified, and the diagnostics use appropriate error handling. This is a temporary debugging aid that poses no risk to the build process.
• No files require special attention

Important Files Changed

Filename	Overview
codemagic.yaml	Adds diagnostic logging to show directory contents before binary verification, helping debug arm64 binary location on M2 machines

_{Last reviewed commit: 69fb2ee}

[gemini-code-assist]

Code Review

This pull request adds diagnostic commands to a Codemagic workflow to help debug the location of build artifacts. My review focuses on improving the correctness and readability of these new shell commands. I've identified a potential issue where the 'not found' message for missing directories may not be displayed as intended and have suggested a refactoring to fix this.

[gemini-code-assist]

The || echo " (not found)" fallback may not work as expected. The exit code of a pipeline is determined by the last command (head), which exits with 0 even on no input. This prevents the fallback from triggering when a directory is missing.

To make this more robust and correctly report when a directory is not found, it's better to explicitly check for the directory's existence. I've also corrected the grep pattern to use single quotes, which is safer in shell scripts to prevent unintended expansions and correctly pass the pattern to grep.

          echo "Desktop/.build/release/ contents:"
          if [ -d "Desktop/.build/release/" ]; then
            ls "Desktop/.build/release/" | grep -v '\.build\|\.o$\|\.d$' | head -30
          else
            echo "  (not found)"
          fi
          echo "Desktop/.build/arm64-apple-macosx/release/ contents:"
          if [ -d "Desktop/.build/arm64-apple-macosx/release/" ]; then
            ls "Desktop/.build/arm64-apple-macosx/release/" | grep -v '\.build\|\.o$\|\.d$' | head -30
          else
            echo "  (not found)"
          fi
          echo "Desktop/.build/x86_64-apple-macosx/release/ contents:"
          if [ -d "Desktop/.build/x86_64-apple-macosx/release/" ]; then
            ls "Desktop/.build/x86_64-apple-macosx/release/" | grep -v '\.build\|\.o$\|\.d$' | head -30
          else
            echo "  (not found)"
          fi