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

How to link this as the static framework(or library) with SPM? #159

Closed
Urtaq opened this issue Jul 7, 2022 · 2 comments · Fixed by #168
Closed

How to link this as the static framework(or library) with SPM? #159

Urtaq opened this issue Jul 7, 2022 · 2 comments · Fixed by #168

Comments

@Urtaq
Copy link

Urtaq commented Jul 7, 2022

First, this is really nice & useful for me to develop with SwiftUI through SPM! Thank you for creating!!!!

Well, recently I've been trying to use the Xcode cloud(it's on the Beta status, though).
Then, there is one trouble to link the Introspect. It's below.

ITMS-90334: Invalid Code Signature Identifier. The identifier "Introspect-55554944a57ff822a61e381886dc5802237a083e" in your code signature for "Introspect_359AFEED79E48935_PackageProduct" must match its Bundle Identifier "Introspect"

Since I found out, the issue seems to be from linking the dynamic framework. It occurs, even though, the Introspect doesn't have the type property as dynamic.
(This is talking about the Package.swift's setting properties)

So, I'd like to know how to use the Introspect as the static framework through SPM.
Because they're linked as the static framework, even though some other frameworks(ex. Alamofire) doesn't have any settings for this, through SPM. Is there any specific options using frameworks or libraries through SPM?

I've had one thing to resolve this. It's the Introspect target's MACH_O_TYPE property sets the static library in the Introspect project.
It's useful & effective to avoid the trouble. So, I'm preparing the P.R for it. But, I think there could be the other awesome resolution.
So, I'd like to ask a question like this title.
Could anyone help or give an advice for this?

@seanrucker
Copy link

I've got the same problem. Did you submit a PR for this fix?

@Urtaq
Copy link
Author

Urtaq commented Sep 28, 2022

@seanrucker Wow! @krzyzanowskim has submitted the PR like my idea! Let's wait for merging the PR!!

davdroman pushed a commit that referenced this issue Feb 10, 2023
Co-authored-by: David Roman <[email protected]>
Resolves #159
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

Successfully merging a pull request may close this issue.

2 participants