Error: xcactivitylog is not a valid xcactivitylog file about xclogparser HOT 5 CLOSED

Yes, it is a known problem. 😔 Currently I am investigating why it happens. I will give an update here if I would be able to figure out what's wrong.

from xclogparser.

Hi we also had the same issue when using the -debug-time-function-bodies and -debug-time-expression-type-checking flags with Xcode 13.x. For some reason Xcode was creating truncated log files. But somehow it's working now that we bumped to use Xcode 13.2.1. I'm pinging @aleksandergrzyb since he verified this recently, maybe he can have some insights about it.

from xclogparser.

We've noticed that in our case .xcactivitylog is invalid, because xcodebuild didn't finish creating it before exiting. Probably the process terminates, because it takes lots of time to generate .xcactivitylog in our case (it has over 50 MB). We solved this issue by executing clean action after build action to occupy xcodebuild process a little bit longer.

In your case please execute following and check if that helps:

xcodebuild \
  -scheme Neo \
  -destination "platform=iOS Simulator,name=iPhone SE (2nd generation)" \
  -resultBundlePath "$RESULT_BUNDLE_PATH" \
  OTHER_SWIFT_FLAGS="-Xfrontend -debug-time-function-bodies -Xfrontend -debug-time-expression-type-checking" \
  build clean

from xclogparser.

Interesting, that seems to work most of the time. Through sometimes it looks like the clean is removing the xcactivitylog of the build. It's not all the time though so I'm not sure if it's a race condition or if there's something else causing it.

This also meant that the xclogparser now starts grabbing the xcactivitylog from the clean since it's the newest log. I had to change our script to take the second newest file and pass it using the --file option.

But at least we've got some stats to work with now, thanks! But we're still slightly limited by another issue #148.

from xclogparser.

Closing this and moving the conversation to #148

from xclogparser.