Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The generated IR folder is massive on v0.5.1 #80

Open
ertjr opened this issue Dec 4, 2024 · 0 comments
Open

The generated IR folder is massive on v0.5.1 #80

ertjr opened this issue Dec 4, 2024 · 0 comments

Comments

@ertjr
Copy link

ertjr commented Dec 4, 2024

At my org, we tried moving from v0.4.3 to v0.5.1 in our CI pipeline, but noticed a couple issues.

First, the build started failing with message:
Error: nonexistentCache("Couldn't find cache at: .. /Library/Developer/Xcode/DerivedData/projectname/Build/Intermediates.noindex/XCBuildData/PIFCache. Ensure a clean build AND ensure xcodebuild clean happens separately from xcodebuild archive command")

So I moved xcodebuild clean to happen separately before the build (previously we used fastlane gym with clean: true option to both clean and archive).

This change made gen-ir complete successfully, but the IR folder in the resulting archive was much much larger than before (10gb vs 1gb). The new larger IR folder has all the same feature modules as before, but now each module folder contains not only the module files .bc, but now they also contain hundreds of other files. Every module has these same files, which seems to be where the 10gb size comes from. Here's some examples of these duplicated files in each module:

  • _DequeBuffer.bc
  • _HashTable.bc
  • AnyDecoder.bc
  • BundleType.bc
  • ... many more

Previously, these files appeared once - the swift-collections files like _DequeBuffer.bc and _HashTable.bc in Archive.xcarchive/IR/OrderedCollections, the Datadog (a third party library we use) files like AnyDecoder.bc and BundleType.bc in Archive.xcarchive/IR/DatadogInternal

It seems our libraries are being duplicated and included in each of our feature modules. Anyone know what's going wrong here or what's causing the duplicating behaviour? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant