Skip to content

Link FoundationExtensions statically

Choose a tag to compare

View all tags
@melle melle released this 06 Sep 14:26
· 18 commits to master since this release
v0.1.13
aa46bb1
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Making FoundationExtensions the static default.

Renamed static / dynamic, make sure that packages without any suffix are static. This unifies a inconsistency in a lot of frameworks used in our products. Also, static linking is is an attempt to fix this issue while deploying to TestFlight / AppStore:

ITMS-90334: Invalid Code Signature Identifier. The identifier "FoundationExtensions-5555494443d5626ab868338a93cce6b274e34595"
in your code signature for "FoundationExtensions" must match its Bundle Identifier "FoundationExtensions"

This fixes SwiftUI previews in Swift Packages as well.

FoundationExtensions is the default now, the dynamic product is FoundationExtensionsDynamic.

Assets 2
Loading