Apple Emails “Too many symbol files” Warning Related To FBLPromises, GoogleUtilities, and nanopb

[Jon Kantner]

I’ve been able to upload and beta test a build of my app with CocoaPods-imported AdMob (7.60). Unfortunately, Apple has been slapping me with this warning via email:

We identified one or more issues with a recent delivery for your app, "<app>" <version> (<build>). Your delivery was successful, but you may wish to correct the following issues in your next delivery:

 

ITMS-90381: Too many symbol files - These symbols have no corresponding slice in any binary [EDC10821-A168-3C8E-B1CD-ECE09E481186.symbols, 1C5E38FD-70DC-3011-8E28-AB9ABC557DA9.symbols, 11908A0B-CF19-34FC-BEE5-9F8DCF63BCEA.symbols].

 

After you’ve corrected the issues, you can upload a new binary to App Store Connect.

I’ve been trying to stop this in case an app update I plan on submitting gets rejected. I learned that the issues are related to AdMob frameworks by doing this:

1. Right-click the archive in the Xcode Organizer > Show in Finder.
   
2. Right-click the archive in Finder > Show Package Contents.
   
3. Open Terminal and cd to the dSYMs folder found in the package contents.
   
4. Run dwarfdump --uuid *

The UUIDs from the Terminal output I highlighted are the ones Apple is complaining about:

UUID: 11908A0B-CF19-34FC-BEE5-9F8DCF63BCEA (armv7) FBLPromises.framework.dSYM/Contents/Resources/DWARF/FBLPromises
UUID: 0FF3F075-3735-32C7-8994-8353813CA59F (arm64) FBLPromises.framework.dSYM/Contents/Resources/DWARF/FBLPromises
UUID: 1C5E38FD-70DC-3011-8E28-AB9ABC557DA9 (armv7) GoogleUtilities.framework.dSYM/Contents/Resources/DWARF/GoogleUtilities
UUID: 652DA9F8-65FE-316C-A74E-A1D1E303CBD3 (arm64) GoogleUtilities.framework.dSYM/Contents/Resources/DWARF/GoogleUtilities
UUID: EDC10821-A168-3C8E-B1CD-ECE09E481186 (armv7) nanopb.framework.dSYM/Contents/Resources/DWARF/nanopb
UUID: 3701E8D9-548A-34D2-A190-9BEB13AF3E99 (arm64) nanopb.framework.dSYM/Contents/Resources/DWARF/nanopb

So how do I prevent these symbols from being used? Please have a look into this for me. Thanks!

[Mobile Ads SDK Forum Advisor Prod]

Hi Jon,

Thank you for reporting this. Would it be possible for you to provide a project (or at least a test project) where you're seeing the issue? Rest assured that the shared project will be used for investigative purposes only and will not be shared externally. Kindly share the project via Reply privately to author option.

regards,
Teejay Pimentel
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q1zsTTe:ref

[Jon Kantner]

Hi Teejay,

I just wanted to stop by to learn if you had any luck solving my problem.

Thanks,

Jon

[Mobile Ads SDK Forum Advisor Prod]

Hi Jon,

I work with TeeJay and will try to assist you. This looks like a general developer issue that's not specific to the Mobile Ads SDK so your issue is out of scope for us. With that being said, I looked up on stackoverflow and found possible help for you here -https://stackoverflow.com/questions/25755240/too-many-symbol-files-after-successfully-submitting-my-apps and close to the bottom of that webpage is a discussion of warnings pertaining to armv7 architecture and how to alleviate them. A CocoPod issue in their issue Tracker here - https://github.com/CocoaPods/CocoaPods/issues/7111 also may help you. I followed your steps and found the armv7 architecture in the build as shown in the attached screenshot. This is the standard way the SDK is implemented. Most probably you aren't allowing a deploy to older iPhone models and therefore having a problem. When I modified the podfile of our sample app like this:

source 'https://github.com/CocoaPods/Specs.git'

minimum_deployment_target = 11.4

platform :ios, minimum_deployment_target

target 'BannerExample' do
use_frameworks! :linkage => :static
  pod 'Google-Mobile-Ads-SDK',:modular_headers => true  
end
post_install do |installer|
    installer.generated_projects.each do |project|
        project.targets.each do |target|
            target.build_configurations.each do |config|
                # Ensure we set all Pods to match the minimum deployment target specified by the app
                config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = minimum_deployment_target
            end
        end
    end
end


and took out of Valid Architectures in Project the armv7 architectures and selected yes to Build Active Architectures only and then archived the app the symbols for armv7 weren't there.


Kind regards,
Aryeh Baker

[Jon Kantner]

Sorry for my late reply due to other huge things going on, but I gave this a shot and succeeded in not getting the Apple complaint. I’ll see how all else works out from here. Thank you!