Some symbols are missing

[kkebo]

When building a-Shell with Xcode, sore Swift symbols are missing. When I run grep within the repository, nothing comes up, so I wonder if the author forgot to commit any files.

• Xcode 26.2
• macOS 26.2

webAssemblyCommandOrder

a-Shell/SceneDelegate.swift:1368:33 Cannot find 'webAssemblyCommandOrder' in scope

finishedPreparingWebAssemblyCommand

a-Shell/ExtraCommands.swift:83:9 Cannot find 'finishedPreparingWebAssemblyCommand' in scope
a-Shell/SceneDelegate.swift:1394:13 Cannot find 'finishedPreparingWebAssemblyCommand' in scope
a-Shell/SceneDelegate.swift:1444:9 Cannot find 'finishedPreparingWebAssemblyCommand' in scope

aliasesAsArray (only on the SwiftTerm2 branch)

a-Shell/SceneDelegate+TerminalView.swift:75:34 Cannot find 'aliasesAsArray' in scope

[holzschu]

Thanks for the report. These symbols are all defined in iOS_system, but (at least for the first two), I'm sure they've been in iOS_system for a long time. I need to check which version of iOS_system is being used by a-Shell.

[kkebo]

@holzschu I'm sorry for the delayed report. Actually, I've been observing this issue for a long time. (for >= 1 year)

[kkebo]

This ios_system seems old. 3.0.2 was released in 2022.

a-shell/xcfs/Package.swift

Line 25 in 0c416a3

url: "https://github.com/holzschu/ios_system/releases/download/v3.0.2/ios_system.xcframework.zip",

[kkebo]

As you said, the first two symbols can now be resolved if I upgrade ios_system from 3.0.2 to 3.0.4.

diff --git a/xcfs/Package.swift b/xcfs/Package.swift
index 9eac38d2..ade337af 100644
--- a/xcfs/Package.swift
+++ b/xcfs/Package.swift
@@ -22,8 +22,8 @@ _ = Package(
         ),
         .binaryTarget(
             name: "ios_system",
-            url: "https://github.com/holzschu/ios_system/releases/download/v3.0.2/ios_system.xcframework.zip",
-            checksum: "f8e1364037de546809065ecdf804277fa7b95faffc32604e91ecb4de44d6294e"
+            url: "https://github.com/holzschu/ios_system/releases/download/v3.0.4/ios_system.xcframework.zip",
+            checksum: "6973c1c14a66cdc110a5be7d62991af4546124bd0d9773b5391694b3a93a5be0"
         ),
         .binaryTarget(
             name: "awk",

[holzschu]

Yes, I've pushed a revised version of Package.swift with the checksums for v3.0.4.
To update to v3.0.5, I need the github actions for ios_System to work, and for now I get a weird "Process completed with exit code 137." (https://github.com/holzschu/ios_system/actions/runs/21598037217/job/62236352095)

[kkebo]

Thank you so much!

To update to v3.0.5, I need the github actions for ios_System to work, and for now I get a weird "Process completed with exit code 137."

Upgrading Xcode version and runner's macOS version could solve the issue.

[holzschu]

Thanks for the help. There isn't much about how to fix this "exit code 137" in the available documentation.
I'm running on macOS-latest, and xcodebuild -version tells me that the CI is running on "XCode 16.4, Build version 16F6", which seems to be the maximum XCode version available for github CI.

Setting verbosity levels to the maximum everywhere hasn't helped. The action stops immediately after starting to execute the command swift run --verbose --package-path xcfs build, and outputs:

/Users/runner/work/_temp/a16d0823-5019-40e1-b06a-84d05a562f23.sh: line 1:  2058 Killed: 9               swift run --verbose --package-path xcfs build
Error: Process completed with exit code 137.

I'm stuck, for the moment.

[kkebo]

@holzschu

I'm running on macOS-latest, and xcodebuild -version tells me that the CI is running on "XCode 16.4, Build version 16F6", which seems to be the maximum XCode version available for github CI.

It's not the maximum Xcode version. It's too old.

For example, you can choose the following combinations:

• macos-26 & Xcode 26.2 (default)
• macos-latest (macos-15) & Xcode 26.2
  • The default selected Xcode version is 16.4, but you can change it with run: sudo xcode-select -s /Applications/Xcode_26.2.app or DEVELOPER_DIR: /Applications/Xcode_26.2.app/Contents/Developer. The latter is preferred if you plan to use self-hosted runners in the future.

[holzschu]

Thank you for your help! (I could not imagine that macos-latest would not be the latest macOS).
That should now be fixed.