Warning during archive. App with iOS 8 extension in Xcode 6

I have a problem archiving my application.

I created a new goal for the expansion of iOS 8.

When I archive the application, I get a warning.

Warning

"PBXCp warning", "warning: skipping the copy phase strip, binary code signed: / Users / Library / Developer / Xcode / DerivedData / App / assemblies / intermediates / ArchiveInter mediates / AppName / IntermediateBuildFilesPath / UninstalledProducts / AppExtappex / Appe x"

The application is in Objective-C.

+54
ios objective-c xcode ios8 ios-app-extension
Sep 20 '14 at 13:06
source share
9 answers

In the Xcode destination settings, check the option "Debug debugging while copying". His statement is that it cannot output debugging characters, since the extension has already been signed.

+24
07 Oct '14 at 22:09
source share

If you create a completely new sample project and Today Extension in Xcode 6.2, the default values ​​are set to NO to remove debugging characters.

enter image description here

+8
Mar 24 '15 at 10:22
source share

Copied from: stack overflow

“Compiled code usually contains debugging information. It’s useful for checking the current code in the debugger, but even more so for the optimized code that you would send in distributions. Therefore, it gets striptease during the assembly of the archive.

The problem is that PBXCp cannot disable debugging symbols from signed binaries, as this will lead to a signature. Therefore, if you have a project that was created before Xcode 6.3, you will get a warning similar to this.

To fix the warning, simply change both values ​​to NO. Deleting them does not work, because the default value is still YES for both. Project templates shipped with Xcode 6.3 are disabled by default. Only projects that were started with old templates still have a YES release string.

Source: https://www.cocoanetics.com/2015/04/skipping-copy-phase-strip/

+8
May 26 '15 at 1:18
source share

The frame / extension is already split and the code is signed by default. The application project cannot detect that the structure has already been stripped and generates a harmless warning. You must not disable it or your application will not be deleted.

+6
Apr 23 '15 at 13:10
source share

There seems to be some confusion surrounding the Strip Debug Symbols When Copy effect, I recommend reading this article for more information: Skipping the phase of the copy phases .

Here are my key findings from studying this issue:

  • When creating a new project with Xcode 6.2 or later values ​​in the project file, NO for both default parameters (Debug and Release) for this parameter.
  • Setting the YES value in the Release setting and executing the Product Archive does not affect the generated binary size of the application (I recommend that you check this using the test for your own projects).
  • Debugging symbols used for Sybolication reporting iOS crashes from an external .dsym file that is separate from the application so I did not expect the symbol table to be included in the binary.
+3
May 08 '15 at 10:57
source share

Check the "Strip Style" option in the Xcode build setup. If it is Non-Global Symbols, change it to All Symbols. this may solve the problem, but I don’t know if there are other problems caused by this change.

+1
Oct. 16 '14 at 16:27
source share

In the "Deployment" section in the assembly setup of your object, find the Strip Debug Symbols During Copy and set it to YES for any production assemblies.

enter image description here

+1
Mar 26 '15 at 15:41
source share

What worked for me was the following:

I edited the circuit that I archived. In this window, I selected "Run" and then the "Information" tab. In Build Configuration, I changed it to Release. I just changed it to "Debug" (the default option) and this warning went away.

Hope this helps.

0
Sep 03 '15 at 11:26
source share

This is probably because you are archiving using the DEBUG schema. If you select the RELEASE scheme, then the "strip debug symbols while copying" option is set to YES, and you do not have this warning.

I suggest archiving with the DEBUG settings for beta testing, but with the RELEASE settings for publishing to the App Store.

-2
Mar 19 '15 at 23:35
source share



All Articles