30 Replies
      Latest reply on May 18, 2016 1:57 AM by vevek
      Andreas Grauel Level 1 Level 1 (0 points)

        Does anyone has a clue what Xcode is trying to tell me?

         

        "The archive did not contain <DVTFilePath:0x7f88ca959ef0:'/Users/mobileserver/Library/Developer/Xcode/Archives/2015-08-17/Project 2015-08-17 14.46.29.xcarchive/BCSymbolMaps/DCF72CBF-7889-372D-B549-2CFA181C32CA.bcsymbolmap'> as expected."

        • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
          schickling Level 1 Level 1 (0 points)

          Having the same problem. Im using Xcode 7 Beta 5. Any news?

          • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
            Andreas Grauel Level 1 Level 1 (0 points)

            I have to disable "Include bitcode for iOS targets" and the validation check works fine, but I'd like to submit with bitcode. I will investage further as soon as we have the Xcode7 GM.

            • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
              eskerber Level 1 Level 1 (0 points)

              It's likely you built your app with Enable Bitcode set to NO in build settings.

               

              Then, in the app submission window, you had "include bitcode" checked, which is now at the bottom of the window. Uncheck that and it should submit. Enable bitcode in your build settings if you want to then submit with bitcode.

              • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                desduvauchelle Level 1 Level 1 (0 points)

                Same problem here.

                  • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                    aventurella Level 1 Level 1 (0 points)

                    Exact same problem here.  I thought it might be because I am using Carthage and was not copying my dSYM files into my product. So I fixed that issue, per the carthage docs, No love still. Get the same error.

                     

                    Ah! When I uncheck the `Include Bit Code` option as mentioned here everything is fine. So I am going to assume that the problem lies in one of my dependant frameworks being complied without Bit Code enabled.

                      • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                        dhmspector Level 1 Level 1 (0 points)

                        I have the same problem -- BUT mine started when I un-checked "Enable Bitcode" in the build settings then tried to turn it back on.  Now trying to upload to iTC via Xcode fails unless I uncheck the bitcode flag in the validation menu.  If I turn it off in build settings then during validation and upload to iTC will still randomly fail unless I also uncheck the little check box in the export/upload dialog

                    • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                      ing.antonioromano Level 1 Level 1 (0 points)

                      I have the same issue, I use a private framework, but both in the framework and in the app the field "Enable Bitcode" is set to "Yes".

                      Disabling the flag "including bitcode" result in a very long period of the state "elaboration in progress" in itunes connect.

                      Any other suggestion?

                      I'm useing xcode 7.0

                      • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                        satcol Level 1 Level 1 (0 points)

                        I'm facing the exact same problem.

                         

                        I can upload only if I uncheck "Include App Symbols....".

                        However, the archive does contain DSYMs and all build settings are correct re: symbols.

                         

                        This looks like a bug.

                        • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                          drewcrawford Level 1 Level 1 (0 points)

                          A BCSymbolMap is a lot like a dSYM for bitcode.  This is why you can work around the issue by either not uploading symbols or not using bitcode.  However if you don't upload symbols, then you won't get symbolicated crashreports on iTunesConnect, and if you don't use bitcode...  then you won't have bitcode.

                           

                          The real solution is to make sure your xcarchive has 2 BCSymbolMaps for each object file (app + framework).  For example

                           

                          otool -l /Users/drew/Library/Developer/Xcode/Archives/2015-12-17/MyArchive.xcarchive/Products/Applications/MyApp.app/MyApp | grep uuid
                              uuid 8D0CCABC-FD9C-346F-A1E7-7FF1B3C0EB46
                              uuid 78D6CAC5-3B32-3A70-8808-7987D9C07667
                          
                          otool -l /Users/drew/Library/Developer/Xcode/Archives/2015-12-17/MyArchive.xcarchive/Products/Applications/MyApp.app/Frameworks/MyFramework.framework/MyFramework | grep uuid
                              uuid 27647D24-F5DE-37E6-A26D-F55FF7518994
                              uuid 636808D2-CB4D-323F-BC2E-F87EFEBF4606
                          

                           

                          Here we have 4 UUIDs, so we expect

                           

                          ls -l /Users/drew/Library/Developer/Xcode/Archives/2015-12-17/MyArchive.xcarchive/BCSymbolMaps
                          total 448
                          -rw-------  1 drew  staff  42067 Dec 16 19:25 27647D24-F5DE-37E6-A26D-F55FF7518994.bcsymbolmap
                          -rw-------  1 drew  staff  42087 Dec 16 19:25 636808D2-CB4D-323F-BC2E-F87EFEBF4606.bcsymbolmap
                          -rw-------  1 drew  staff  65639 Dec 17 00:21 78D6CAC5-3B32-3A70-8808-7987D9C07667.bcsymbolmap
                          -rw-------  1 drew  staff  65615 Dec 17 00:21 8D0CCABC-FD9C-346F-A1E7-7FF1B3C0EB46.bcsymbolmap
                          

                           

                          These BCSymbolMap files are generated when you build the associated framework/app.  If you are using a tool like Carthage/CocoaPods, you may need to trace the build chain and figure out where these files have ended up and how you can get them included in the the app archive.

                            • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                              Liron Level 1 Level 1 (0 points)

                              Do you know what you need to do to get the BCSymbolMap files included into a framework? I'm working on building a private framework to be included in other apps, and I'm hitting the same problem when including the framework into a swift app (not sure about Objective-C) that it can't submit to the app store with both boxes checked.

                               

                              Do I need to somehow include the BCSymbolMap files that get generated when the framework gets built and copy those into the application? I've never seen a cocoapod library that included BCSymbolMap files along with the framework itself.

                              • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                                Konran Level 1 Level 1 (0 points)

                                When I apply otool -l as you did it, I get a number of three uuid's for my app executable instead of only two. The file is ObjC and linked together with 3 bitcode-enabled static libraries. The executable is also bitcode-enabled.

                                 

                                Any idea, why there are 3 uuids's listed?

                                 

                                The uuid's in the BCSymbolMap files do match the list from otool. So, is that ok?

                                 

                                Anyway, I can also only validate the archive with either symbols or bitcode checked.

                                • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                                  visskiss Level 1 Level 1 (0 points)

                                  Thanks drewcrawford.

                                   

                                  I feel there is an opportunity to learn something here and would appreciate your help in diagnosing the issue.  I previously submitted to itunes without issue with both boxes checked but suddenly am stumbling upon this issue.

                                   

                                  When I use otool, I get two uuids for the app and one uuid for a separate framework which is my own and is in the same workspace.  The two uuids from the app have associated BCSymbolMap files, but the single UUID from the framework does not have an associated file.  Instead there are two further BCSymbolMap files which are a mystery.  You assistance is appreciated.

                                   

                                  EDIT

                                   

                                  Upon further inspection, it seems that xcode is embedding the incorrect binary for the framework, but the correct BCSymbolMap files.  It is taking the binary from the Build/Products/debug area, while it is taking the symbol files from build/intermediates which is the correct location for built frameworks.

                                   

                                  Ideas on how to fix?

                                • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                                  danielbm Level 1 Level 1 (0 points)

                                  Is anyone else here using Realm?

                                   

                                  I had the same problem, and I changed all sorts of crazy things to try to get it fixed, so I'm not even sure what it was that worked...

                                  First of all I removed all frameworks from my embedded frameworks and added them back.

                                   

                                  And then, when I was doing that, I noticed I skiped a step when installing Realm. Here's what it says in the documentation:

                                   

                                  1. In your unit test target’s “Build Settings”, add the parent path to RealmSwift.framework in the “Framework Search Paths” section.

                                   

                                  So I checked my unit test target, which I hadn't even looked at so far, and added the path...

                                  And then I archived my app again and it validated fine with both bitcode and symbols. o/

                                   

                                  As I said, I tried all sorts of crazy things, so I'm not even sure if what worked was reinstalling the frameworks or adding the Realm search path or something else entirely, but I thought this was worth mentioning here. I was going crazy trying to solve this!

                                    • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                                      danielbm Level 1 Level 1 (0 points)

                                      And here's something weirder...

                                      When I added my frameworks back I dragged them to ebedded binaries and they showed up at the root of the project navigator.

                                      I archived the project and validated the archived and everything worked out.

                                      Then I moved the frameworks to another group inside the project navigator. Not an actual folder, just one of those regular yellow groups. And then the same problem came back again.

                                      Then I removed the frameworks again and dragged them back to the embedded binaries and left them at the root of the project navigator. And, alas, it works again.

                                    • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                                      jonas_man Level 1 Level 1 (0 points)

                                      I fixed this!

                                       

                                      Im using carthage and i added the build script mention in the instrctions before i added the embebed binaries!

                                       

                                      So what i did was:

                                       

                                      Remove the script that carthage recomends.

                                      Make sure i added the frameworks to the "embbeded binaries" in the general tab. Not just drag and drop to the project.

                                      Added the script back to the build phases. It will run after the Embebed Frameworks copy phase.

                                      Done

                                      • Re: Missing BCSymbolMap for AppStore Submission - Xcode7B5
                                        visskiss Level 1 Level 1 (0 points)

                                        OK, so I found the issue, at least for me.

                                         

                                        I have my own framework which is in a workspace alongside the apps that it is used for.  When I added the framework to the app, it would link to an absolute path instead of a relative one.  So, I fixed the issue by right clicking the embedded binary for the framework and selecting reveal in project navigator (which is the bar on the left).  You can also just click the framework on the left (project navigator).  Then you'll see the path is absolute.  Change this to "relative to build" and it should embed properly.