Hi, to be honest, I'm not sure if this is a known bug or not. I figure that when XCLogParser tries to parse the swift file, it seems to compare it with the wrong prefix.
Basically CompileSwift does not exist anymore. It was replaced with SwiftCompile.

To reproduce:
- Create a project with Swift File inside it
- Build it
- Take a look on Report Navigator
- Export it
Try to use xclogparser, and compare it with XCLogParser results. When compiling to swift, it will categorize it as other rather than swiftCompilation.
This is json result

I also found that CompileSwiftSources prefix does not exist anymore. It was replaced like this hunk. But please do correct me if I mistook the meaning of the swiftAggregatedCompilation.
This is the file where XCLogParser tries to parse the steps by looking at the command prefix.
https://github.com/MobileNativeFoundation/XCLogParser/blob/e536e3009d391513a791e08b991d6fe413be0f9c/Sources/XCLogParser/parser/BuildStep.swift#L123C22-L123C41
Hi, to be honest, I'm not sure if this is a known bug or not. I figure that when XCLogParser tries to parse the swift file, it seems to compare it with the wrong prefix.
Basically
CompileSwiftdoes not exist anymore. It was replaced withSwiftCompile.To reproduce:
Try to use xclogparser, and compare it with XCLogParser results. When compiling to swift, it will categorize it as
otherrather thanswiftCompilation.This is json result

I also found that
CompileSwiftSourcesprefix does not exist anymore. It was replaced like this hunk. But please do correct me if I mistook the meaning of theswiftAggregatedCompilation.This is the file where XCLogParser tries to parse the steps by looking at the command prefix.
https://github.com/MobileNativeFoundation/XCLogParser/blob/e536e3009d391513a791e08b991d6fe413be0f9c/Sources/XCLogParser/parser/BuildStep.swift#L123C22-L123C41