Skip to content
Discussion options

You must be logged in to vote

We've rolled out an update to the build machines that should resolve the issue, so the suggested workaround should no longer be necessary.

Could someone please run another build using Xcode 16.3 to confirm that everything is working as expected now?

Replies: 4 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@Toasbi
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by dam-ease
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
5 participants