Styjun

Did the Americans trade destroyers in the "destroyer deal" that they would later need themselves?

What steps would an amateur scientist have to take in order to get a scientific breakthrough published?

Do 3/8 (37.5%) of Quadratics Have No x-Intercepts?

Why were contact sensors put on three of the Lunar Module's four legs? Did they ever bend and stick out sideways?

Golden Guardian removed before death related trigger

Self-deportation of American Citizens from US

What are the cons of stateless password generators?

How long until two planets become one?

Are the named pipe created by `mknod` and the FIFO created by `mkfifo` equivalent?

Can a US President, after impeachment and removal, be re-elected or re-appointed?

Should I intervene when a colleague in a different department makes students run laps as part of their grade?

(3 of 11: Akari) What is Pyramid Cult's Favorite Car?

Is it okay for me to decline a project on ethical grounds?

Move the outer key inward in an association

Is it possible to attain stream-entry if one is only following "the 5 precepts"?

Sci-fi change: Too much or Not enough

Why use the "finally" keyword?

Must a song using the A minor scale begin or end with an Am chord? If not, how can I tell what the scale is?

Is there a way to know the composition of a Team GO Rocket before going into the fight?

Reading line from terminal in expl3

This day in history III

Why is the Apollo LEM ladder so far from the ground?

Are there any unpublished Iain M. Banks short stories?

Should I accept an invitation to give a talk from someone who might review my proposal?

With Swift 5 and iOS 12.2+ should I change “Always Embed Swift Standard Libraries” to NO?

How do I specify multiple targets in my podfile for my Xcode project?Shall we always use [unowned self] inside closure in SwiftHow to distribute Swift Library without exposing the source code?Why is Swift compile time so slow?After switching to Xcode 7, app size grew from 9 MB to 60 MB, is there a fix?XCode 7.3.1 hangs on “copying swift standard libraries”Why do I get “dyld: Library not loaded: @rpath/libswiftCore.dylib” error$(inherited) is not working in xcodeSwift custom library could not be used error Library not loaded: @rpath/libswiftCoreFoundation.dylib image not foundCan I target multiple Xcode/Swift versions with a single Cocoapod?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

5

1

Somehow "Always Embed Swift Standard Libraries" for all of my targets is YES. Probably due to historical development from Swift 1 to 5.
I'm using Xcode 10.2 now, upgraded the targets and my "Swift language version" is 5 for all of them.

Out of interest I created an empty new project with Xcode 10.2 and it is created with "Always Embed Swift Standard Libraries" as NO for both Debug and Release builds.

I have a feeling that even if I leave it as it is, Apple will strip standard Swift libraries anyway as a part of thinning for iOS 12.2+?

So what's the correct default since swift 5? Any benefits from either keeping it at YES or changing to NO?

[Update] Thanks to Cœur for a comment. It really looks like that one of the CocoaPods versions did it. Project is set to NO, but all the targets using CocoadPods were YES.

ios swift xcode

share|improve this question

edited Mar 27 at 9:23

Stanislav Dvoychenko

asked Mar 26 at 19:22

Stanislav DvoychenkoStanislav Dvoychenko

89399 silver badges1212 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  While the default is NO, note that if you use a standard CocoaPods integration, some versions (like CocoaPods 1.6.1) may override ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES default value and set it to YES. This was made by github.com/CocoaPods/CocoaPods/pull/5732
  
  – Cœur
  Mar 27 at 7:42
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you for providing the possible cause of this YES value! I do use CocoaPods from the very early versions.
  
  – Stanislav Dvoychenko
  Mar 27 at 8:57
  

  
  
  
  

add a comment | 

5

1

Somehow "Always Embed Swift Standard Libraries" for all of my targets is YES. Probably due to historical development from Swift 1 to 5.
I'm using Xcode 10.2 now, upgraded the targets and my "Swift language version" is 5 for all of them.

Out of interest I created an empty new project with Xcode 10.2 and it is created with "Always Embed Swift Standard Libraries" as NO for both Debug and Release builds.

I have a feeling that even if I leave it as it is, Apple will strip standard Swift libraries anyway as a part of thinning for iOS 12.2+?

So what's the correct default since swift 5? Any benefits from either keeping it at YES or changing to NO?

[Update] Thanks to Cœur for a comment. It really looks like that one of the CocoaPods versions did it. Project is set to NO, but all the targets using CocoadPods were YES.

ios swift xcode

share|improve this question

edited Mar 27 at 9:23

Stanislav Dvoychenko

asked Mar 26 at 19:22

Stanislav DvoychenkoStanislav Dvoychenko

89399 silver badges1212 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  While the default is NO, note that if you use a standard CocoaPods integration, some versions (like CocoaPods 1.6.1) may override ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES default value and set it to YES. This was made by github.com/CocoaPods/CocoaPods/pull/5732
  
  – Cœur
  Mar 27 at 7:42
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you for providing the possible cause of this YES value! I do use CocoaPods from the very early versions.
  
  – Stanislav Dvoychenko
  Mar 27 at 8:57
  

  
  
  
  

add a comment | 

Somehow "Always Embed Swift Standard Libraries" for all of my targets is YES. Probably due to historical development from Swift 1 to 5.
I'm using Xcode 10.2 now, upgraded the targets and my "Swift language version" is 5 for all of them.

Out of interest I created an empty new project with Xcode 10.2 and it is created with "Always Embed Swift Standard Libraries" as NO for both Debug and Release builds.

I have a feeling that even if I leave it as it is, Apple will strip standard Swift libraries anyway as a part of thinning for iOS 12.2+?

So what's the correct default since swift 5? Any benefits from either keeping it at YES or changing to NO?

[Update] Thanks to Cœur for a comment. It really looks like that one of the CocoaPods versions did it. Project is set to NO, but all the targets using CocoadPods were YES.

ios swift xcode

share|improve this question

edited Mar 27 at 9:23

Stanislav Dvoychenko

asked Mar 26 at 19:22

Stanislav DvoychenkoStanislav Dvoychenko

89399 silver badges1212 bronze badges

share|improve this question

edited Mar 27 at 9:23

Stanislav Dvoychenko

asked Mar 26 at 19:22

Stanislav DvoychenkoStanislav Dvoychenko

89399 silver badges1212 bronze badges

share|improve this question

edited Mar 27 at 9:23

Stanislav Dvoychenko

asked Mar 26 at 19:22

Stanislav DvoychenkoStanislav Dvoychenko

89399 silver badges1212 bronze badges

asked Mar 26 at 19:22

Stanislav DvoychenkoStanislav Dvoychenko

89399 silver badges1212 bronze badges

asked Mar 26 at 19:22

Stanislav DvoychenkoStanislav Dvoychenko

89399 silver badges1212 bronze badges

2 Answers
2

active

oldest

votes

3

The default for new projects is NO and (as far as I know) always has been. I have never had "Always embed" set to YES, and my projects have always worked just fine. So unless there is some really good reason why this was YES, it probably shouldn't have been.

Note that the libraries are stripped out only if you are building against the 12.2 SDK and going onto a machine with 12.2 (or later). The libraries are still needed to run on a 12.1 or earlier machine.

share|improve this answer

answered Mar 26 at 19:58

mattmatt

351k5353 gold badges574574 silver badges767767 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This setting only makes a difference if your app is pure Objective-C and is using some Swift frameworks: in that case, you would want it to YES.
  
  – Cœur
  Mar 27 at 7:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Marking this as an answer. Plus comment from Cœur makes it probably 100% covered with when YES is needed.
  
  – Stanislav Dvoychenko
  Mar 27 at 9:02
  

  
  
  
  

add a comment | 

1

I came here because I've updated my development environment to :

XCode 10.2
iOS 12.2
WatchOS 5.1.3

And my apps refused to even start on the watch, with a single message to console, saying library image not found. (using Swift4 build setting)

Setting "always embed" to on makes the app install process incredibly slow on the watch.

I updated the project to use Swift5, now the app at least starts up again.

share|improve this answer

answered Apr 13 at 11:04

Alex StoneAlex Stone

20.9k4646 gold badges185185 silver badges342342 bronze badges

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55364816%2fwith-swift-5-and-ios-12-2-should-i-change-always-embed-swift-standard-librarie%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

3

The default for new projects is NO and (as far as I know) always has been. I have never had "Always embed" set to YES, and my projects have always worked just fine. So unless there is some really good reason why this was YES, it probably shouldn't have been.

Note that the libraries are stripped out only if you are building against the 12.2 SDK and going onto a machine with 12.2 (or later). The libraries are still needed to run on a 12.1 or earlier machine.

share|improve this answer

answered Mar 26 at 19:58

mattmatt

351k5353 gold badges574574 silver badges767767 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This setting only makes a difference if your app is pure Objective-C and is using some Swift frameworks: in that case, you would want it to YES.
  
  – Cœur
  Mar 27 at 7:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Marking this as an answer. Plus comment from Cœur makes it probably 100% covered with when YES is needed.
  
  – Stanislav Dvoychenko
  Mar 27 at 9:02
  

  
  
  
  

add a comment | 

3

The default for new projects is NO and (as far as I know) always has been. I have never had "Always embed" set to YES, and my projects have always worked just fine. So unless there is some really good reason why this was YES, it probably shouldn't have been.

Note that the libraries are stripped out only if you are building against the 12.2 SDK and going onto a machine with 12.2 (or later). The libraries are still needed to run on a 12.1 or earlier machine.

share|improve this answer

answered Mar 26 at 19:58

mattmatt

351k5353 gold badges574574 silver badges767767 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This setting only makes a difference if your app is pure Objective-C and is using some Swift frameworks: in that case, you would want it to YES.
  
  – Cœur
  Mar 27 at 7:40
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Marking this as an answer. Plus comment from Cœur makes it probably 100% covered with when YES is needed.
  
  – Stanislav Dvoychenko
  Mar 27 at 9:02
  

  
  
  
  

add a comment | 

The default for new projects is NO and (as far as I know) always has been. I have never had "Always embed" set to YES, and my projects have always worked just fine. So unless there is some really good reason why this was YES, it probably shouldn't have been.

Note that the libraries are stripped out only if you are building against the 12.2 SDK and going onto a machine with 12.2 (or later). The libraries are still needed to run on a 12.1 or earlier machine.

share|improve this answer

answered Mar 26 at 19:58

mattmatt

351k5353 gold badges574574 silver badges767767 bronze badges

share|improve this answer

answered Mar 26 at 19:58

mattmatt

351k5353 gold badges574574 silver badges767767 bronze badges

answered Mar 26 at 19:58

mattmatt

351k5353 gold badges574574 silver badges767767 bronze badges

answered Mar 26 at 19:58

mattmatt

351k5353 gold badges574574 silver badges767767 bronze badges

1

I came here because I've updated my development environment to :

XCode 10.2
iOS 12.2
WatchOS 5.1.3

And my apps refused to even start on the watch, with a single message to console, saying library image not found. (using Swift4 build setting)

Setting "always embed" to on makes the app install process incredibly slow on the watch.

I updated the project to use Swift5, now the app at least starts up again.

share|improve this answer

answered Apr 13 at 11:04

Alex StoneAlex Stone

20.9k4646 gold badges185185 silver badges342342 bronze badges

add a comment | 

1

I came here because I've updated my development environment to :

XCode 10.2
iOS 12.2
WatchOS 5.1.3

And my apps refused to even start on the watch, with a single message to console, saying library image not found. (using Swift4 build setting)

Setting "always embed" to on makes the app install process incredibly slow on the watch.

I updated the project to use Swift5, now the app at least starts up again.

share|improve this answer

answered Apr 13 at 11:04

Alex StoneAlex Stone

20.9k4646 gold badges185185 silver badges342342 bronze badges

add a comment | 

I came here because I've updated my development environment to :

XCode 10.2
iOS 12.2
WatchOS 5.1.3

And my apps refused to even start on the watch, with a single message to console, saying library image not found. (using Swift4 build setting)

Setting "always embed" to on makes the app install process incredibly slow on the watch.

I updated the project to use Swift5, now the app at least starts up again.

share|improve this answer

answered Apr 13 at 11:04

Alex StoneAlex Stone

20.9k4646 gold badges185185 silver badges342342 bronze badges

share|improve this answer

answered Apr 13 at 11:04

Alex StoneAlex Stone

20.9k4646 gold badges185185 silver badges342342 bronze badges

answered Apr 13 at 11:04

Alex StoneAlex Stone

20.9k4646 gold badges185185 silver badges342342 bronze badges

answered Apr 13 at 11:04

Alex StoneAlex Stone

20.9k4646 gold badges185185 silver badges342342 bronze badges