Post

Replies

Boosts

Views

Activity

Comment on Static library links on device but fails on iOS Simulator
So, if I understand correctly, I should package my library as an XCFramework instead of sharing the library project itself, and then add that XCFramework to the app project that needs to use it. Also, if I follow the XCFramework approach, what exactly should I deliver to the client so they can integrate and use the library without needing access to my original library project?
Mar ’26
Comment on Static library links on device but fails on iOS Simulator
If I follow the XCFramework approach, what should I deliver to my client so they can integrate and use the library in their app without needing my library project?
Replies
Boosts
Views
Activity
Mar ’26
Comment on Static library links on device but fails on iOS Simulator
If I follow the XCFramework approach, what should I deliver to the client so they can integrate and use the library in their app without needing my library project?
Replies
Boosts
Views
Activity
Mar ’26
Comment on Static library links on device but fails on iOS Simulator
So, if I understand correctly, I should package my library as an XCFramework instead of sharing the library project itself, and then add that XCFramework to the app project that needs to use it. Also, if I follow the XCFramework approach, what exactly should I deliver to the client so they can integrate and use the library without needing access to my original library project?
Replies
Boosts
Views
Activity
Mar ’26