Xcode 16 Crash While Validating (com.apple.root.default-qos)

Question

mmccartney OP

Created Mar ’25

Replies 5

Boosts 0

Participants 2

Hello,

We're attempting to validate our application archive through Xcode but the application is crashing during the validate step and we're not sure why.

Platform: macOS 15.1
Arch: arm64

We've confirmed that our developer agreements are up to date (a suggestion made by other posts on these forums). Other suggestions have been to downgrade Xcode but we're hoping there's another explanation.

The application is quite complex - many libraries and framework - but executes as expected during development and testing.

Crash Report

Any insight into this error would be appreciated. We're sure it's something wrong with our plist or archive structure but the crash is limiting our ability to debug.

Answered by mmccartney in 827789022

As mentioned in my ticket:

The root of the issue appeared to be with the formation of the archive. I forced the archive to include an additional directory after Products (something I noticed other archives had) and the crash no longer occurred. The code sign didn't mind the original structure but once it came time to build the zip, an assert was triggered because it was expecting an additional directory.

.xarchive/Products/MyApp.app

Vs.

.xarchive/Products/Applications/MyApp.app

I would recommend an addition to the validation tooling to check for this malformed archive and fail sooner! Let me know that I have a bad orchestration. It was a real head scratcher for days!

Boost

Answer 1

mmccartney OP

Mar ’25

Looking into the issue more, we see it crashing when attempting to zip the files after signing. Particularly any .so files that hide among the internals of the app.

Not sure if that helps locate the issue any more but perhaps it's something about compressing the files that we're using - however that makes very little sense to me.

0

Answer 2

DTS Engineer OP

Apple

Mar ’25

@mmccartney Thanks for the post, if Xcode is crashing and you have the crash file, please may I ask you to file a bug?

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?

Albert Pascual   Worldwide Developer Relations.

0

Answer 3

mmccartney OP

Mar ’25

Hey thanks for the followup. I've posted the bug on the feedback app.

Ticket: FB16709928

0

Answer 4

DTS Engineer OP

Apple

Mar ’25

Thanks, for providing the FB number. This helps a lot.-

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Albert Pascual   Worldwide Developer Relations.

0

Answer 5

mmccartney OP

Mar ’25

Accepted Answer

As mentioned in my ticket:

The root of the issue appeared to be with the formation of the archive. I forced the archive to include an additional directory after Products (something I noticed other archives had) and the crash no longer occurred. The code sign didn't mind the original structure but once it came time to build the zip, an assert was triggered because it was expecting an additional directory.

.xarchive/Products/MyApp.app

Vs.

.xarchive/Products/Applications/MyApp.app

I would recommend an addition to the validation tooling to check for this malformed archive and fail sooner! Let me know that I have a bad orchestration. It was a real head scratcher for days!

0