Issues when using package indirectly

[gus-eulalio-bilue]

Describe the bug
In a current project of mine, I have added jose-swift to a package which is used by the main app.
When I try to build the app for testing, it complains that the package can't be found. It isn't building the PackageProduct files (or is misplacing them).

To Reproduce
Steps to reproduce the behavior:

1. Add jose-swift as dependency to a package.
2. Add package as dependency to app
3. Build for testing
4. See error

Expected behavior
Build succeeds

Smartphone (please complete the following information):

• Device: iPhone 14 (simulator)
• OS: iOS 17/18/26

Additional context
Built on:

• Xcode 16.0.1
• MacOS 15.7.2

cc: @christiankm

[beatt83]

Hi @gus-eulalio-bilue. How are you?

I dont have all the context but could it be that you didn't link the frameworks in the test target? It seems you added it correctly on the app target but not on the test target. I should look like the example screenshot below in Frameworks & Libraries section.

If you have explicit code from the library in your tests you always need to link the library to your tests as well. You cannot just do import JSONWebSignature without the linking.

[gus-eulalio-bilue]

Hi @beatt83. I tried that too, but no success.
As it turns out, jose-swift isn't even used in those tests. It's only used internally in the package.

[christiankm]

@beatt83 Thanks for your quick replies!

The problem occurs when you have an Xcode project, which depends on a package, which then itself depends on your package. Or rather, not jose-swift specifically, but I think it's connected to some of the dependencies of jose-swift itself, and how they're bundled. Based on our research, this could be an Xcode bug itself.

I have a shell sample project that highlights this issue, which I'll also use to open a Feedback report to Apple.

XcodeSPMTransientPackage.zip

In short, we don't believe jose-swift itself has a problem, but for us to use it in our setup, we need to be able to dynamically link it, i.e. for jose-swift to provide that option (see #58)

[christiankm]

This problem is also reported to Apple as FB21314909.

[beatt83]

Hey @christiankm and @gus-eulalio-bilue .
Sorry for my late response but I had to actually give some time to assess this issue.

@christiankm the repository you gave me, I can see the error and see what is the problem, it is very possible that is a circular dependency problem and as you said you already reported.

I dont know if this will help but instead of making jose-swift dynamic. On your XcodeSPMTransientPackage project I made your MyLibrary as dynamic and it worked without any issue.

[christiankm]

Thanks @beatt83, that would probably work as well. Though I am still curious what is happening in the first place.

[beatt83]

My 2 cents.

When you dont provide the type (.static, .dynamic) by Apple documentation it will pick for you the most appropriate, its probably automatically setting as static, since it doesn't detect other frameworks with same dependencies in the App target.

Probably what's happening is it gets confused since the App Test target inherently will have the frameworks from the app target and then your linking on that test target as well the MyLibrary-TestSupport which depends on MyLibrary that has the same framework dependencies. He must get confused, and thats the reason you need to add the .dynamic, in your library, probably on the MyLibrary-TestSupport is enough.

I didn't go deep but I guess this is what's happening.

Im going to close this now since I don't think the problem its with this library, and you can fix it without touching this library package apparently. But if you need more help please say :)

[christiankm]

Thanks for your help!We’ve reached the same conclusion as well, and I do think you’re right in what happens. It’s a problem of diamond-shaped dependency graphs, and seems to be an Xcode/clang bug, cause the same thing does not happen in a pure Swift Package setup with the same structure.Agree on closing for now, thanks!ChristianDen 19. dec. 2025 kl. 21.10 skrev Gonçalo Frade ***@***.***>:beatt83 left a comment (beatt83/jose-swift#57) My 2 cents. When you dont provide the type (.static, .dynamic) by Apple documentation it will pick for you the most appropriate, its probably automatically setting as static, since it doesn't detect other frameworks with same dependencies in the App target. Probably what's happening is it gets confused since the App Test target inherently will have the frameworks from the app target and then your linking on that target as well the MyLibrary-TestSupport which depends on MyLibrary that has the same frameworks. I didn't go deep but I guess this is what's happening. Im going to close this now since I don't think the problem its with this library, and you can fix it without touching this library package apparently. But if you need more help please say :) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>