Defaults: Xcode 13 archive error

Hey, thanks for creating and maintaining this awesome package. Using the GM version of Xcode 13 (13A233), I can compile and run my app against the iOS 15 SDK just fine, but encountering errors when archiving the app. See screenshot below for detail.

It seems rather strange… Maybe we need to do canImport(Combine) && canImport(SwiftUI) at the top of SwiftUI.swift? I got no idea

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 16 (2 by maintainers)

Most upvoted comments

This is fixed in Defaults v6: https://github.com/sindresorhus/Defaults/releases/tag/v6.0.0

I have been planning to drop some older platform versions, so this seemed like a good opportunity to do so as it also fixes this issue.

sindresorhus on Oct 12, 2021

This is caused by a known issue in Xcode 13 throughout Beta and RC. You can read more details about it in its release notes here(Search for 74120874)

It only happens in building for armv7 devices or archiving, which may possibly explain why @sindresorhus doesn’t meet the issue while others did.

The suggested workaround is lifting the deploy target up to iOS_12.

xiao99xiao on Sep 15, 2021

@igoriols Hey sorry I forgot to reply to your question, @JustinFincher got the right answer

automactic on Sep 26, 2021

The suggested workaround is lifting the deploy target up to iOS_12.

Ohhh, upon re-reading the release note, I realized the dependency needs to (temporarily) raise the deploy target to v12. I though my app needs to make this change. I forked this library, made that single change and was able to archive my app.

I tried to do the same thing, but I’m not able to import the dependency from my fork using Swift Package Manager. It always targeting the original repo. Hi, @automactic how did you import the library from your fork? Can you help me?

@igoriols I was able to resolve the issue by removing the previous Default repo link from “Recently Used” in the first place and then paste the one from @automactic. It should be pointing to the new one after that

JustinFincher on Sep 25, 2021

The suggested workaround is lifting the deploy target up to iOS_12.

Ohhh, upon re-reading the release note, I realized the dependency needs to (temporarily) raise the deploy target to v12. I though my app needs to make this change.

I forked this library, made that single change and was able to archive my app.

automactic on Sep 15, 2021

For me its the archive. my target ios is 14. i can’t upload a build to testflight because of this.

quantamrhino on Sep 15, 2021

My deployment target is iOS13 but @xiao99xiao is right.

If your built device is something like Any iOS Device (arm64), you’ll meet these bugs for no reason. The solution for now is to select a simulator other than an arm64 device in build-time. Or, you can just plug your iPhone in and debug on your own devices.

Hope this will help anybody.

RoyRao2333 on Sep 15, 2021