Mark DiFranco

Have you registered your classes on the `SwinjectStoryboard.defaultContainer`? The `SwinjectStoryboard` will use that container by default. I personally use this container to instantiate my `Assembler` like so: ``` let assembler...

My current workaround is to let the app load via storyboard, and then call this method in `applicationDidFinishLaunching(_ aNotification: Notification)`. ``` func setupWindow() { let storyboard = SwinjectStoryboard.create(name: "Main", bundle:...

Ah that's perfect. Thank you!

Yeah I don't think this is necessary. The included `./carthage-build.sh` helps get around the build issue when not using `xcframework`s, and we'll add `xcframework` support in the next major version.

I'm noticing this bug as well, with the same setup as the example project (using a branch to specify the version of a child repo). Unfortunately the provided workaround is...

I'm still seeing this in 0.35.0. Is this an issue with how `carthage archive` creates the archive.zip, or is it a bug in Carthage's resolving logic?

You wouldn't have this issue if you used semantic versioning. You should only update the major version when there's a breaking change to your library. The fact that your one...

Ah I see. My apologies for assuming you hadn't made a breaking change. The range syntax might make sense in this case then. Or, it's not completely outrageous to force...

This is probably related to #3034

Thanks for logging, @vikrem and I will look into the issue.