I've created a Swift Package with some shared code to be my core for some projects. I am creating an iOS app, so I have a workspace with the iOS app project in it. The core package is a remote dependency of the app. At this point, everything is setup and working great.
I've created a new framework project to add to the same workspace. I wanted to do another Swift Package, but I need some assets, so I'm doing a framework for now until SPM works with assets. I also need some of the core functionality in this framework, so I added the package as a dependency to it as well. The framework is then linked to the iOS app project.
At this point, everything builds fine, and I can use code from core in both the app and framework projects. I can also use code from the framework in the app. However, when I build and run in the simulator, I get console warnings about some of the classes in the core being implemented multiple times and which one being used is undefined.
The app still works properly, so it seems it's just the console output that is the issue. The two classes being warned are set to internal in the package. All the public objects seem to be fine. Is there a proper way to link the dependency between the framework and app to make things continue to work properly but without the console warnings?