Xcode 11.4: Invalid debug info found, debug info will be stripped

I have a new warning per every target after upgrading to Xcode 11.4:


Invalid debug info found, debug info will be stripped


This has never been the case for my code base before. Anything I can do to resolve these warning? Am I safe to release to the AppStore with these warnings?


For one of the targets detailed info is:


mismatched subprogram between llvm.dbg.label label and !dbg attachment
  call void @llvm.dbg.label(metadata !137) #2, !dbg !203
label %138
double (i8*)* @"\01__hidden#1918_"
!137 = !DILabel(scope: !138, name: "zulu_time", file: !10, line: 196)
!138 = distinct !DISubprogram(name: "parseTimezone", scope: !10, file: !10, line: 161, type: !139, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !196)
!203 = !DILocation(line: 196, column: 1, scope: !100, inlinedAt: !101)
!100 = distinct !DISubprogram(name: "__hidden#1928_", scope: !10, file: !10, line: 161, type: !11, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6)
mismatched subprogram between llvm.dbg.label label and !dbg attachment
  call void @llvm.dbg.label(metadata !347), !dbg !371
label %55
i32 (i8*, ...)* @"\01__hidden#1920_"
!347 = !DILabel(scope: !348, name: "end_getDigits", file: !10, line: 140)
!348 = distinct !DISubprogram(name: "getDigits", scope: !10, file: !10, line: 109, type: !349, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !351)
!371 = !DILocation(line: 140, column: 1, scope: !315)
!315 = distinct !DISubprogram(name: "__hidden#1922_", scope: !10, file: !10, line: 109, type: !11, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6)
DICompileUnit not listed in llvm.dbg.cu
!171 = distinct !DICompileUnit(language: DW_LANG_C99, file: !7, producer: "Apple clang version 11.0.3 (clang-1103.0.32.29)", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug, enums: !12, retainedTypes: !172, imports: !180, nameTableKind: None)
ld: warning: Invalid debug info found, debug info will be stripped
!dbg attachment points at wrong subprogram for function
!126 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, s: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11)
double (%0*, i8*, %0*, i32)* @"\01__hidden#2776_"
  br i1 %41, label %42, label %90, !dbg !152, !llvm.loop !155
!156 = !DILocation(line: 283, column: 3, scope: !157)
!157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158)
!157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158)
ld: warning: Invalid debug info found, debug info will be stripped
mismatched subprogram between llvm.dbg.label label and !dbg attachment
Up vote post of staninprague Down vote post of staninprague
18k views
Posted by
staninprague
Reply
Add a Comment

Replies

Any project using the CocoaPod for FBAudienceNetwork (v5.5.1) will do this at the linking stage in release builds


We also see the same behavior in Google-Mobile-Ads-SDK as someone else pointed out


⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Answers/iOS/Answers.framework/Answers(ANSWriteEventOperation.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Fabric/iOS/Fabric.framework/Fabric(CLSMachOBinary.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBAdCrashHandler.m.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBAdKVOController.m.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBAdQualityViewabilityMeasurement.m.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBAdStaticLibAnalyzer.m.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(NSCoding+FBAdCoding.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFGLProgramUtil.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFDataBlockDistributor.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFMp4AtomManager.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFMp4StreamingParser.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFVodMp4FrameMetadataCompressor.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFDashTrackEntryContainer.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFMediaPresentationDescription.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFDecompressionHelpers.mm.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBBDSignalCollectionExecutorBuilder.m.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(unzip.c.o)


ld: ignoring invalid debug info in /Users/distiller/project/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADNativeAdViewMonitor.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADIssueHandler.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADCrashReporter.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADDataCompression.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADSafeBrowsingMonitor.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADContent.o)
⚠ld: ignoring invalid debug info in /Users/distiller/project/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADNativeAdSignalCollector.o)
Posted by
robkeepsafe
Up vote reply of robkeepsafe Down vote reply of robkeepsafe
Add a Comment

Also seeing these a lot in our project, with no third-party libraries (but with Xcode subprojects), everything compiled from source with the newest Xcode 11.4.

Posted by
tijmen
Up vote reply of tijmen Down vote reply of tijmen
Add a Comment

Seeing the same issue in Xcode Version 11.4 (11E146)

ld: warning: ignoring invalid debug info in ...../Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADNativeAdViewMonitor.o)


7 Warnings when Archiving a project.


Tried to clean, update pods, nothing helps.

Posted by
Adelmaer
Up vote reply of Adelmaer Down vote reply of Adelmaer
Add a Comment

Hi, are those issues fixed in 11.4.1?

Posted by
juraj
Up vote reply of juraj Down vote reply of juraj
Add a Comment

No. I have just tried (in a project with no third-party code).



FB7668750


Posted by
Universalis
Up vote reply of Universalis Down vote reply of Universalis
Add a Comment

Same problem Version 11.4 (11E146):


Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBAdKVOController.m.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFDataBlockDistributor.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFMp4AtomManager.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFMp4StreamingParser.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFVodMp4FrameMetadataCompressor.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFDashTrackEntryContainer.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFMediaPresentationDescription.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFDecompressionHelpersForAVC1.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FNFDecompressionSessionDebuggerForAVC1.mm.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBBDHelpers.m.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(FBBDSignalCollectionExecutorBuilder.m.o)
Ignoring invalid debug info in /Users/marco/Desktop/WOTD/Pods/FBAudienceNetwork/Static/FBAudienceNetwork.framework/FBAudienceNetwork(fbZipArchiveUnzip.c.o)
Posted by
marcotini
Up vote reply of marcotini Down vote reply of marcotini
Add a Comment

I get same issue after archiving my project, it is on Google Mobile Ads. However, I didn't get this when building the project.


Xcode: Version 11.4 (11E146)


ld: warning: ignoring invalid debug info in /Users/Chuck/Desktop/MovieWorld/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADNativeAdViewMonitor.o)
ld: warning: ignoring invalid debug info in /Users/Chuck/Desktop/MovieWorld/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADIssueHandler.o)
ld: warning: ignoring invalid debug info in /Users/Chuck/Desktop/MovieWorld/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADIssueHandler.o)
ld: warning: ignoring invalid debug info in /Users/Chuck/Desktop/MovieWorld/Pods/Google-Mobile-Ads-SDK/Frameworks/GoogleMobileAdsFramework-Current/GoogleMobileAds.framework/GoogleMobileAds(GADCrashReporter.o)
Posted by
Haibo.Zhou
Up vote reply of Haibo.Zhou Down vote reply of Haibo.Zhou
Add a Comment

Same here

Posted by
ergunkocak
Up vote reply of ergunkocak Down vote reply of ergunkocak
Add a Comment

Unfortunate, this is not possible, this product is commercial. We have the same bug

!dbg attachment points at wrong subprogram for function
!2944 = distinct !DISubprogram(name: "[function_name]", scope: !3, file: !3, line: 430, type: !1600, scopeLine: 431, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11, retainedNodes: !2945)
i32 (%struct._[struct name]*, %struct._[struct name]*)* @[function name]
  br i1 %55, label %56, label %94, !dbg !3166, !llvm.loop !3173
!3174 = !DILocation(line: 650, column: 3, scope: !3132)
!3132 = distinct !DILexicalBlock(scope: !3096, file: !3, line: 650, column: 3)
!3096 = distinct !DISubprogram(name: "[function name]", scope: !3, file: !3, line: 629, type: !3097, scopeLine: 630, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11, retainedNodes: !3099)
ld: warning: ignoring invalid debug info in /Users/user/Library/Developer/[library name]

Apple TV app project, when build Archihe, of cource bitcode enabled. XCODE Version 11.4.1 (11E503a)

Posted by
roman.netexpert
Up vote reply of roman.netexpert Down vote reply of roman.netexpert
Add a Comment

Is there any consequences distributing an app when you have those warning?

Posted by
Yoshimura
Up vote reply of Yoshimura Down vote reply of Yoshimura
Add a Comment

I have now distributed two apps with this warning, and they are working well with no evil consequences.

Posted by
Universalis
Up vote reply of Universalis Down vote reply of Universalis

  • at 99% you can submit top App Store.

    is a warningonce linked, an app is pure binary

    by the way the same for me for GoogleAds.

    quality of FB/google is far lower than Apple engineers quality, OR they deliberately don't care iOS plartfomr??

    —
    ingconti
Add a Comment

We're still seeing this error in our project when building with Xcode 11.5 GM. We're not able to provide the source code, but is there any way for us to determine what code is triggering this?


!dbg attachment points at wrong subprogram for function
!51 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11)
void (%3*, %0*, %0*, %0*, i32, %2*)* @"\01__hidden#6361_"
  br i1 %213, label %446, label %119, !dbg !83, !llvm.loop !276
!277 = !DILocation(line: 249, column: 2, scope: !278)
!278 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !279)
!278 = distinct !DISubprogram(name: "__hidden#6396_", scope: !31, file: !31, line: 215, type: !32, scopeLine: 216, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !279)
ld: warning: Invalid debug info found, debug info will be stripped
Posted by
jasonmarr
Up vote reply of jasonmarr Down vote reply of jasonmarr
Add a Comment

I can share (its obj c), please contact me via my email.

Posted by
mstr
Up vote reply of mstr Down vote reply of mstr
Add a Comment

Same here, also using Google Mobile Ads Framework.


However, the problem started AFTER I used the Product -> Analyze function. Before, no warnings, at all. After the analyze build, numerous "Invalid debug info" warnings appeared. Even after cleaning the build folder and the derived data folder, these warnings keep appearing.

Posted by
Wizfinger
Up vote reply of Wizfinger Down vote reply of Wizfinger
Add a Comment

still occuring on archive in 11.5 , has anyone had a chance to see if its fixed in 11.6 beta?

Posted by
lmDeveloper1
Post not yet marked as solved Up vote reply of lmDeveloper1 Down vote reply of lmDeveloper1
Add a Comment