Looks like this has been fixed as of Xcode 26.1

Just checking in that this is still occurring on the public release of Xcode 26. Is there a fix planned for this?

Thanks! That seems to be a big help in deterministically finding which required reason APIs each library uses. However, one thing I'm observing is anything that is not a dynamic XCFramework seems to be causing an error when uploading to App Store Connect, even if that library has its own privacy manifest. It seems that when importing a framework that implicitly depends on another framework (which itself uses required reason APIs and contains its own privacy manifest), even if the explicitly imported framework does not use any such APIs, we are receiving errors.