1.9 produces "missing a dependency on IssueReportingPackageSupport" warning

[alexito4]

Description

I've updated from 1.5.2 to 1.9.0 and started getting this Xcode build warning, I think is from Xcode's explicit module dependency scanner:

'IssueReporting' is missing a dependency on 'IssueReportingPackageSupport' because 
dependency scan of Swift module 'IssueReporting' discovered a dependency on 
'IssueReportingPackageSupport'

Note that the build and tests still succeed (but in our case the warning surfaces as an error in strict CI reporting tools).

[stephencelis]

@alexito4 I haven't seen this in projects depending on 1.9.0...can you share a project that reproduces with instructions on how to reproduce? Xcode version, etc.

[alexito4]

@stephencelis took a while to reduce cause our project is quite big and complex but here it is. Used a bit of AI to explain the situation, hopefully it helps.

IssueReportingWarningRepro.zip

Running in Xcode Version 26.2 (17C52)

xcodebuild build-for-testing \
    -project IssueReportingWarningRepro.xcodeproj \
    -scheme IssueReportingWarningRepro \
    -destination "platform=iOS Simulator,name=iPhone 17" \
    -skipPackagePluginValidation \
    -skipMacroValidation

Results in

...
warning: 'IssueReporting' is missing a dependency on 'IssueReportingPackageSupport' because dependency scan of Swift module 'IssueReporting' discovered a dependency on 'IssueReportingPackageSupport'
** TEST BUILD SUCCEEDED ** [8.455 sec]

[mbrandonw]

Hi @alexito4, do you know why you are depending on XCTestDynamicOverlay in the app target and IssueReporting in the test target? That doesn't seem right, and if you fix that by only depending on IssueReporting in the app target (and nothing in the test target) then it compiles without warnings.

[alexito4]

Thanks @mbrandonw , let me investigate further what's going on and how that change in the example project would transfer to our real project. I'm pretty sure I tried something similar and wasn't able to compile so there must something else going on. Thanks for the guidance, I will come back with better information. 🙏🏻

[candiun]

Hi @mbrandonw, we've been investigating this issue further. While the fix you mentioned did the trick for this example project, we've been still stumbling upon this issue in our real application.

After some digging, what I suspect to be the issue is that by importing TCA in the app target & SnapshotTestingCustomDump in the test target, we are including IssueReporting transitively (via CustomDump) in both targets, resulting in the same issue as above.

I'm attaching the minimal project

IssueReportingWarningReproClean-2.zip

xcodebuild build-for-testing \
  -workspace IssueReportingWarningReproWorkspace.xcworkspace \
  -scheme IssueReportingWarningRepro \
  -destination "platform=iOS Simulator,name=iPhone 17" \
  -skipPackagePluginValidation \
  -skipMacroValidation

It's worth noting that the warning doesn't appear on consecutive builds with the derived data being up to date.

[scogeo]

I'm experiencing this issue as well. In my case, the warning appeared when I introduced an .xcframework that contains IssueReporting. There seems to be an Xcode tooling issue in transitive SPM library resolution when used with non-SPM targets such as .xcframework or .xctest bundles.

I have submitted a PR for a similar issue sqlite-data. In that case, I was getting link failures, not just warnings.