Closed PSchmiedmayer closed 11 months ago
@supereg This is related to the issue we are having in https://github.com/StanfordBDHG/NAMS/actions/runs/5358248972/jobs/9732017815. Should be addressed once I have manually tagged a new release.
As noted here https://github.com/StanfordBDHG/NAMS/pull/14#issuecomment-1609280691, it seems like the referenced PR (version 2.2.9) completely breaks projects depending on this ResearchKit fork.
Description
The automatically generated Info.plist does not include a proper CFBundleVersion value.
Reproduction
Create an XCFramework using Xcode 14.3:
And then inspect the binary Info.plist files using
Expected behavior
The Info.plist files should include a version bundle key as defined in the Xcode settings:
Additional context
The issue is resolved in Xcode 15. Once Xcode 15 is released we can rely on Xcode to generate the correct keys. Until then we have to manually convert the Info.plist files with:
Modify them to include
and convert them back to the binary format using
and commit these files as done in e.g.: https://github.com/StanfordBDHG/ResearchKit/commit/f677e4adc38d8ce2bdc718cd420c60d7be45a648
Code of Conduct