FBAudienceNetwork

Summary The published in 6.22.0 cannot be compiled by SwiftPM. Line 1 declares , but line 21 specifies . was introduced in PackageDescription 5.5, so the manifest references an API that does not exist in the tools version it opts into. Error Why it happens The platform floor was raised between releases without raising the tools-version line: Impact This is a resolution-time failure, not a compile-time one. SwiftPM evaluates every manifest in the dependency graph before it can resolve anything, so once 6.22.0 enters the graph, resolution aborts and no target builds at all. Builds and archives fail outright, and unrelated binary targets elsewhere in the graph start reporting spurious errors as a side effect of the aborted resolution. Two things make the blast radius larger than it first appears: 1. It also breaks projects that never link an FBAudienceNetwork product. Several ad-mediation SDKs depend on this package with an open-ended requirement such as , so the manifest still has to be evaluated even when no FBAudienceNetwork product is used. 2. Any project resolving without a checked-in , which is the common CI configuration, picks 6.22.0 automatically. Those builds went red today with no change on the consumer side. Reproduction fails, as does on any equivalent Xcode project. Suggested fix Change line 1 of to and republish as 6.22.1. is available from PackageDescription 5.5 onward, and 5.5 has shipped since Xcode 13, so it should not narrow the supported toolchain range in practice. Lowering the platform back to would also resolve the error, but presumably contradicts the intended minimum for this release. In the meantime the workaround for anyone hitting this is to pin to 6.21.1.

Title: Static xcframework (6.21.x) is built with , causing dsymutil warnings about missing module files Checklist [x] I've updated to the latest released version of the SDK (6.21.1) [x] I've searched for existing GitHub issues [x] I've read the Code of Conduct Environment Audience Network SDK: 6.21.1 Integration: Swift Package Manager () Xcode: 26.5 (17F42) Also reproduced with the standalone download: Description When building an app that links the static FBAudienceNetwork xcframework, the phase (dsymutil) emits a large number of warnings like: The referenced files are internal Clang module cache artifacts (system modules like CoreFoundation/UIKit/Foundation, plus the SDK's own modules such as , , ). These paths point into your internal Buck build tree and are naturally not shipped in the distributed binary, so dsymutil can't resolve them. As dsymutil's own note states, redistributable static libraries shouldn't be built with module debugging enabled. Root cause (verified) The static library ships with module debugging enabled, leaving unresolved references embedded in the binary. Inspecting the 6.21.1 standalone distribution confirms this and shows the difference between the two variants: The static binary embeds the exact paths that dsymutil warns about; the dynamic binary does not. This strongly suggests the static target is being compiled with while the dynamic one is not. Suggested fix Build the static xcframework without** Clang module debugging — i.e. drop (or the equivalent debug-info setting) from the static library's compile flags, so no module references are embedded. Given the dynamic variant already builds clean, aligning the static build's flags should resolve this without affecting functionality. Impact These are warnings, not errors — the build succeeds and the app runs. The only effect is degraded debug info for the SDK's own frames. Still, the warning volume is noisy and, per your tooling's own note, indicates an incorrect packaging configuration for a redistributable static library. Happy to provide the full build log or additional details if helpful. Thanks!

Fatal Exception: NSInternalInconsistencyException 0 CoreFoundation 0x92c60 __exceptionPreprocess 1 libobjc.A.dylib 0x14ee4 objc_exception_throw 2 Foundation 0x124c80 _userInfoForFileAndLine 3 CoreAutoLayout 0x11ec -[NSLayoutConstraint _setMultiplier:] 4 CoreAutoLayout 0x8ba8 +[NSLayoutConstraint constraintWithAnchor:relatedBy:toAnchor:multiplier:constant:] 5 *********** 0xfdf088 FBANAdMediaView.setupAutolayoutConstraints() + 27 (FBANAdMediaView+Layout.swift:27) 6 ******** 0xfe1954 FBANAdMediaView.mediaView(didLoad:) + 358 (FBANAdMediaView.swift:358) 7 ******** 0xfe1b5c @objc FBANAdMediaView.mediaView(didLoad:) 8 ******** 0xfe96f8 partial apply for closure #1 in FBANAdImageRenderer.loadMedia() + 56 (FBANAdImageRenderer.swift:56) 9 ******** 0xfd6f7c closure #1 in FBAdRemoteImageView.loadImage(_:) + 53 (FBAdRemoteImageView.swift:53) 10 ******** 0xfd702c thunk for @escaping @callee_guaranteed (@guaranteed UIImage?, @in_guaranteed URL?) -> () () 11 ******** 0x1010c94 __41-[FBAdAssetPlaceholder addResultHandler:]_block_invoke_2 12 ******** 0x10126c8 __61-[FBAdPersistentCacheImpl _assetForKey:ofType:resultHandler:]_block_invoke_2 13 libdispatch.dylib 0x63094 _dispatch_call_block_and_release 14 libdispatch.dylib 0x64094 _dispatch_client_callout 15 libdispatch.dylib 0x10d44 _dispatch_main_queue_drain 16 libdispatch.dylib 0x10994 _dispatch_main_queue_callback_4CF$VARIANT$mp 17 CoreFoundation 0x4e014 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ 18 CoreFoundation 0xb4f8 __CFRunLoopRun 19 CoreFoundation 0x1e174 CFRunLoopRunSpecific 20 GraphicsServices 0x1988 GSEventRunModal 21 UIKitCore 0x4e5a88 -[UIApplication _run] 22 UIKitCore 0x27ef78 UIApplicationMain 23 *********** 0x51ae34 main + 14 (main.m:14) 24 ??? 0x105e184d0 (缺失) SDK version 6.20.1