I think there used to be a bug (might still be?) where Xcode didn’t 
automatically strip out the x86 simulator slices when you were archiving.

Saagar Jha

> On Apr 5, 2018, at 07:29, Alex Zavatone <z...@mac.com> wrote:
> 
> 
>> On Apr 5, 2018, at 4:19 AM, Redler Eyal <e...@mellel.com> wrote:
>> 
>>>> 
>>>>> 2. (More importantly) It makes the client's binary larger since it will 
>>>>> have to include our full library, including simulator code. (correct me 
>>>>> if I'm wrong)
>>>> 
>>>> No, you should ask your client to remove the simulator slice before 
>>>> submitting to the App Store.
>>> 
>>> This is controlled in the build settings for release builds.  Compiled 
>>> Simulator code is not packaged and should not be packaged in a release 
>>> build.
>> 
>> My understanding is that the dynamic lib is copied as a resource and not 
>> processed automatically that way.
>> 
> 
> 
> But when it is built, it is built as Release or Debug, unless you have added 
> other build configurations.  When Archive is selected, that uses Release.
> 
> Why would a Simulator i386 architecture be used in a release build?  You can 
> check the configuration and see if that architecture is even there in the 
> build config.
> 
> - Alex Zavatone
> 
> _______________________________________________
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/saagar%40saagarjha.com
> 
> This email sent to saa...@saagarjha.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to