Upon trying to archive I got funny errors preventing it

The issue was about embedding the libraries, I did not embed them any longer and the error went away. Still I'm still in the blue about what embedding or not embedding does mean.

I’m glad to hear you got this sorted out. Lemme tackle this last bit:

I'm still in the blue about what embedding or not embedding does mean.

In the context of an iOS app [1]:

• Select Do Not Embed if you want to simply record a reference to the framework. This is primarily for system frameworks, like StoreKit, where the framework exists on the OS you’re targeting, and thus your app doesn’t need to carry along its own copy [2].
• Select Embed & Sign if you want to embed the framework in your app and re-sign it as your code. This is most commonly used for frameworks that are part of a third-party SDK, where the code doesn’t exist on the target OS and thus your app needs to have its own copy.
• Select Embed if you want to embed the framework in your app. Folks typically use this with their own frameworks. For example, you might create a framework to hold some some code that’s common to your app and its app extensions. This is very like Embed & Sign, except that it skips the code signing step. This saves a little build time, and is useful when the framework is already signed correctly.

Finally, lemme point you at An Apple Library Primer, which explains a bunch of the terminology used by frameworks.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] In this, and in many other cases, macOS offers more choices (-:

[2] In reality it can’t do this because the framework in the iOS SDK doesn’t contain any code; it’s just a stub library.