Since swinject has SPM support, this should have it also

I'm using Swinject 1.1.1. I really want to be able to inject a reference to my UIViewController which has been registered for storyboard injection. I currently have a SpriteKit app where class GameViewController: UIViewController is injected into Main.storyboard via registerForStoryboard(). Creating this view controller causes creation of a bunch of SKScene's one of which needs a reference to the original GameViewController in order to be able to call presentViewController to show settings. I tried to resolve the GameViewController in the initComplete (to avoid a circular reference) but it comes back as nil. Am I missing something? Can this be made to work and if not, what's the underlying issue?

Version 1.1.2 doesn't compile for XCode 9.2 / Swift 4 as the type of the identifier of NSStoryboard changed from String to NSStoryboard.SceneIdentifier.
…
#elseif os(OSX)
/// Instantiates the view/Window controller with the specified identifier.
/// The view/window controller and its child controllers have their dependencies injected
/// as specified in the Container passed to the initializer of the SwinjectStoryboard.
///
/// - Parameter identifier: The identifier set in the storyboard file.
///
/// - Returns: The instantiated view/window controller with its dependencies injected.
public override func instantiateController(withIdentifier identifier: NSStoryboard.SceneIdentifier) -> Any {
SwinjectStoryboard.pushInstantiatingStoryboard(self)
let controller = super.instantiateController(withIdentifier: identifier)
SwinjectStoryboard.popInstantiatingStoryboard()
…

Following along with the tutorial, I created a storyboard with 2 view controllers of the same type, I gave one of them a swinjectRegistrationName as described in the README, and then I created an assembly with storyboardInitCompleted implemented for both the named and the unnamed registration.

When I run the app, SwinjectStoryboard isn't able to set the swinjectRegistrationName in the object and instead this error is printed in the console

2017-12-05 14:52:41.010112-0800 SwinjectStoryboardBug[29435:2586579] Failed to set (swinjectRegistrationName) user defined inspected property on (SwinjectStoryboardBug.ViewController): [<SwinjectStoryboardBug.ViewController 0x7f862ed13c30> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key swinjectRegistrationName.

and upon placing breakpoints in:

    private func injectDependency(to viewController: UIViewController) { ... }

the swinjectRegistrationName is indeed nil.

After doing some tracking down on the internets, it looks like the protocol RegistrationNameAssociatable needs to be @objc-ified.

When I replace with this:

@objc internal protocol RegistrationNameAssociatable: AnyObject {
    var swinjectRegistrationName: String? { get set }
}

all is well and the swinject registration name is non-nil again.

The workaround is to compile SwinjectStoryboard as Swift Version 3.2.

Here is my assembly:

import Foundation
import Swinject
import SwinjectStoryboard

class MyAssembly: Assembly {
    public func assemble(container: Container) {
        container.storyboardInitCompleted(ViewController.self, name: "InitialViewController") { r, c in
            print(c)
            print(r)
        }

        container.storyboardInitCompleted(ViewController.self) { r, c in
            print(c)
            print(r)
        }
    }
}

and I create the view controller like:

    let container = SwinjectStoryboard.defaultContainer
    private func createViewController<T: AnyObject>(_ type: T.Type, _ storyboardName: String, _ storyboardIdentifer: String, container: Container) -> T {
        let bundle = Bundle.main
        let storyboard = SwinjectStoryboard.create(name: storyboardName, bundle: bundle, container: container)
        return storyboard.instantiateViewController(withIdentifier: "InitialViewController") as! T
    }

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
        let viewController = createViewController(ViewController.self, "Main", "InitialViewController", container: container)
        self.window = UIWindow(frame: UIScreen.main.bounds)
        self.window?.rootViewController = viewController
        self.window?.makeKeyAndVisible()

        return true
    }

Currently it is not possible to resolve in a standard way circular dependencies containing UIViewControllers from storyboard. A hack described in Swinject #245 gave me an idea: What if we "temporarily" registered an UIViewController instance during instantiation from storyboard?

Something like:

public func storyboardInitCompleted<C: Controller>(_ controllerType: C.Type, name: String? = nil, initCompleted: @escaping (Resolver, C) -> ()) {
    let factory = { (_: Resolver, controller: Controller) in controller }
    let wrappingClosure: (Resolver, Controller) -> () = { r, c in 
        (r as! Container).register(Controller.self) { _ in c } // Register an instantiated view controller to the container
        initCompleted(r, c as! C) 
    }
    let option = SwinjectStoryboardOption(controllerType: controllerType)
    _register(Controller.self, factory: factory, name: name, option: option)
        .initCompleted(wrappingClosure)
}

This might enable a standard way of resolving circular dependencies:

container.storyboardInitCompleted(ViewController.self) { r, vc in
    vc.presenter = r.resolve(Presenter.self)   
}

container.register(Presenter.self) { _ in Presenter() }
    .initCompleted { r, p in p.view = r.resolve(ViewController.self) }

Obviously, this would only work if ViewController is the entry point to object graph, and might have other restrictions. My fear is that providing a feature which resembles "normal" Swinject usage but has some restrictions might cause confusion for the users (but then again, there already are such restrictions in SwinjectStoryboard usage).
@yoichitgy What do you think? Is it worth pursuing something like this?

SwinjectStoryBoard Version: 1.1.1

Hi!

I am using Swinject for several projects and I really enjoy that project! :)
Now I just want to try out a ViewController registration with name, because I need the same ViewController type but with different dependency (view model) instances. Unfortunately this dependency is never set and the initCompleted closure from storyboardInitCompleted is never called.

Maybe I am using it in a wrong way? Here is some example code extract of my current project.

ViewController Storyboard Ids
2 Storyboard ViewControllers of class MyViewController

1. Storyboard ID: "active"
2. Storyboard ID: "inactive"

ViewController registration

container.storyboardInitCompleted(MyViewController.self, name: "active") { resolver, vc in
            vc.viewModel = resolver.resolve(MyViewModelType.self, name: "active")
}

container.storyboardInitCompleted(MyViewController.self, name: "inactive") { resolver, vc in
            vc.viewModel = resolver.resolve(MyViewModelType.self, name: "inactive")
}

ViewModel registration

container.register(MyViewModelType.self, name: "active") { resolver in
            return MyViewModel(filter: .active)                  
}

container.register(MyViewModelType.self, name: "inactive") { resolver in
            return MyViewModel(filter: .inactive)                  
}

ViewController Instantiation

let activeViewController = storyboard.instantiateViewController(withIdentifier: "active")
let inactiveViewController = storyboard.instantiateViewController(withIdentifier: "inactive")

activeViewController.viewModel  // <- nil
inactiveViewController.viewModel // <- nil

In SinjectStoryBoard.injectDependency there is nil in registrationName (Line 94 in File ViewController+Swinject.swift). Maybe that causes the problem?

Thank you and kind regards
Phillipp

Hi,

How can I set module for a storyboard programmatically and also for all of its UI content?

The reason is because the storyboard itself is in an app that references a framework which contains the viewcontroller.

So looking at this screenshot I can tell the storyboard to point to the Presentation Framework. I'd like to know if there is a better and easier way to set the module programmatically.

Thank you for Swinject!

Would it be possible to install SwinjectStoryboard via Cocoapods like Swinject?

Hi, I have a question about dependent injection in Unit Test.
I use SwinjectStoryboard as follows to inject dependency to top viewController.

extension SwinjectStoryboard {
    class func setup() {
        
        defaultContainer.storyboardInitCompleted(TopViewController.self){ _, c in
            c.repository = Repository()
        }
    }
}

In normal target, injection is success. But, injection is failure in tests target.
I think that there is a issue about controllerType of SwinjectStoryboardOption.
In registration phase, controllerType is 'AppNameTests.TopViewController. But, in resolving phase, controllerType is 'AppName.TopViewController'.

Is there any solution about this?

Env

Swinject branch master (using CocoaPods)
SwinjectStoryboard branch master (using CocoaPods)
Xcode 8.1 Swift 3.0
iOS 10.1 Device

After upgrading to Xcode 9.4.1, we're getting EXC_BAD_ACCESS when deploying to device. Any clue what's going on?

github "Swinject/Swinject" "2.4.1"
github "Swinject/SwinjectAutoregistration" "2.1.1"
github "Swinject/SwinjectStoryboard" "2.0.2"

Thanks!

I have a controller with a custom initialiser:

class MyController: UIViewController {
    private let obj: MyObj! // This MUST exist, it cannot and should not be optional
    init(withObject obj: MyObject) {
        self.obj = obj
    }

    // Looks like I have to have this here...
    required init?(coder aDecoder: NSCoder) {
        super.init(coder: aDecoder)
    }
}

How can I use SwinjectStoryboard to create this controller with the initialiser called? I can't find the documentation on this exact use case. The required init is the one that's called.

Working on AppKit project using SwinjectStoryboard.

Upgraded to High Sierra GM candidate and the line above seem to cause problems. According to the comment in the code, the container box was placed in as a workaround for previous Xcode versions.

I will try to investigate the problem and report back.

It looks good to rename registerForStoryboard to injectOnInstantiationByStoryboard or something else to avoid misunderstanding that resolve method (especially with arguments) can be used as a pair with registerForStoryboard.

Related issue:
Swinject/Swinject#153

Segmentation fault happens when using SwinjectStoryboard and Swinject (swift4 branch). Have anybody investigated that?

That happens if we pass the controller as protocol (ProjectsListViewInputProtocol).

container.storyboardInitCompleted(ProjectsListViewController.self) { (r, controller: ProjectsListViewInputProtocol) in
            let presenter = r.resolve(ProjectsListPresenterProtocol.self, argument: controller)!
            controller.presenter = presenter
}

Ignore...

Yes it is doable just change the storyboard module to point to the framework module.

Posted by @mrkd: Swinject/Swinject#238

Objective-C class method 'initialize', which is not guaranteed to be invoked by Swift and will be disallowed in future versions

Xcode - Version 8.3 (8E162), Swift 3.1

• Swinject (2.0.0)
• SwinjectStoryboard (1.0.0):
  • Swinject (= 2.0.0)

/Pods/SwinjectStoryboard/Sources/Storyboard+Swizzling.swift:25:30: Method 'initialize()' defines Objective-C class method 'initialize', which is not guaranteed to be invoked by Swift and will be disallowed in future versions

I'm working on an app that uses Swinject via the Assembly approach to managing injection. I'm looking at adding support for storyboard injection.

Since we're currently instantiating the window and main view controller from the storyboard, I think I need to use SwinjectStoryboard.setup() to manage storyboard injection. But the defaultContainer used there isn't the same as the container argument passed to my Assembly subclass. Also, setup() is called early enough that I don't think I can create my assembly objects before setup() is called.

Is there some way I can use SwinjectStoryboard to manage a dependency on an object that's created in an Assembly? It's possible I haven't grasped Swinject well enough to see the obvious approach here.

Hello, so I have the following view controller class, which is actually my initial view controller in storyboard:

class RootViewController: UIViewController {
    var presenter: RootPresenter?
}

On the "SwinjectStoryboard" extension, I do the following:

class func setup() {
    let childContainer = Container(parent: defaultContainer)
        childContainer.registerForStoryboard(RootViewController.self) { (resolver, controller) in
            let presenter = resolver.resolve(RootPresenter.self)
            controller.presenter = presenter
        }
        childContainer.register(RootPresenter.self) { _ in
            RootPresenter()
        }
}

Resolver closures are never called, could you please help me understand why?

Note: When I register directly on "defaultContainer" (not on a child of it), it works ok.

Thank you in advance,
Alin

Hi,

I really love the feature of Swinject where I can add additional arguments when I call resolve:
Declaration:

func resolve<Service, Arg1>(
        _ serviceType: Service.Type,
        argument: Arg1) -> Service?

Usage:
r.resolve(OfferSettingsViewModeling.self, argument: "Some Argument")

I wonder if we could implement a similar thing when instantiating view controllers from SwinjectStoryBoard:
Something like:
func instantiateViewController<Arg1>(withIdentifier identifier: String, arg1: Arg1)
And use it like this:

let storyboard = SwinjectStoryboard.create(name: "Main", bundle: nil, container: container)
storyboard.instantiateViewController(withIdentifier "MainViewController", arg1: 123)

and then I can catch it on storyboardInitCompleted like this:

container.storyboardInitCompleted(MainViewController.self) { r, c, arg1 in
            c.viewModel = r.resolve(MainViewModeling.self, arg1: arg1)!
        }

I think this would be really helpful for use cases where you want to instantiate a view controller with a given context, mostly relevant in master/detail stories, where the detail view controller's view model need to be instantiated with an identifier regarding the chosen detail on the master view controller.

What do you think?

This is an enhancement request
In case of inheriting from SwinjectStoryboard There should be overridable method which accepts Container.Controller and ResolverType as parameters, so subclass could check for controller protocol conformance and alter resolve process.

use case:

protocol ViewModeleledView: NSObjectProtocol {
    associatedtype ViewModel
    var viewModel: ViewModel! {get set}
}
private protocol ViewModelResolvableView {
    func resolve(resolver: ResolverType)
}
private extension ViewModeleledView: ViewModelResolvableView  {
    func resolve(resolver: ResolverType) {
        viewModel = resolver. resolve(ViewModel.self)
   }
}
class AltStoryboard: SwinjectStoryboard {
    override func resolve(controller: Container.Controller, with resolver: ResolverType) {
        if let controller = controller as? ViewModelResolvableView {
            controller. resolve(resolver)
        } else {
            super. resolve(controller, with: resolver)
        }
    }
}

With this I can omit registration of ViewModeleledViews in container

Hi guys,

I have been using SwinjectStoryboard for a long time and didn't have any issues. Now I have some problem with High Sierra and want to know maybe you have some solution for this issue.
After latest changes (tag 1.1.2) setup() class method is invoke, but doesn't invoke closure in storyboardInitCompleted method.
I've checked problem and found the method swinject_storyboardWithName:bundle: that not invoke.

Should enhance the document for users to reduce learning cost of SwinjectStoryboard. Both of the following topics need some investigation for documentation.

• Availability with Storyboards and XIBs.
• Combination with Assembler.

Swinject/Swinject#95

Hello,
So I'm having a project written in Swift 3.1 and tried to add the Swinject and SwinjectStoryboard with Cocoapods like this:

pod 'Swinject', '~> 2.1.0'
pod 'SwinjectStoryboard', '~> 1.0.0'

I'm getting the following error when running "pod install". I'm guessing it's a compatibility issue.

[!] Unable to satisfy the following requirements:

- `Swinject (~> 2.1.0)` required by `Podfile`
- `Swinject (= 2.0.0)` required by `SwinjectStoryboard (1.0.0)`

Using Swinject 2.0.0 works fine, but I'm getting the 2 warnings regarding the 'initialize()' functions 🙂 (because of Swift 3.1).

Thanks,
Alin

Hey guys, for the past week I’ve been having a real issue trying to get an embedded view controller to have a property injected into it by the container.

All the VCs exist in the storyboard. They are subclasses of UIVC.

• I have the initial VC initialised programmatically in AppDelegate. This is great as it is resolved from the container.
• The container view with an embed segue to VC2 does not automatically have its properties resolved.

Can the embedded VC2 have its properties resolved as well, even if it is also designed in the storyboard? I must be d

Apply the same change made to Swinject v1 branch.
Swinject/Swinject#109

Just for clarity: registerForStoryboard has been replaced with storyboardInitCompleted. And it's just a straight swap, no additional code or other changes needed?

When I try to update the Carthage I have this error:
*** Fetching SwinjectStoryboard Failed to check out repository into /Users/user/Library/Caches/org.carthage.CarthageKit/dependencies/SwinjectStoryboard: No object named "swift4" exists (Error Domain=CarthageKit.CarthageError Code=22 "(null)")

I'm using a SwinjectStoryboard extension to set up injection for my main VC. That's working fine. I added the following to set up injection for another VC in the same storyboard. This view controller is reached by a segue from the initial view controller:

defaultContainer.storyboardInitCompleted(DetailViewController.self) { (r:Resolver, c:DetailViewController) in
    c.bar = "Injected bar"
}

[I'm trying out SwinjectStoryboard with Xcode's default master/detail view app template, in case that's not obvious.]

Here's the thing: With the above code, injection works, but the closure is called twice with different instances of DetailViewController. The first is when setup() is called, and the second is when the DetailViewController appears on the screen. If I set a breakpoint in the closure, c is a different instance in the second call, and it's the second one that appears. I don't know why the first is created or what happens to it.

Why do I get two calls to this closure with different instances, and how would I avoid that?

Should add a better and simpler example project for users to reduce learning cost of SwinjectStoryboard.

Swinject/Swinject#95

Hi guys,

im doing sample OSX project and i have huge problems with Swinject Storyborad initialization - i was using it for iOS and never had any issues.

I've tried both: Implicit and Explicit Instantation and none of them works

• Implicit crashes entire app -i assume because of all dependencies are resolved after app startup and after Initial View Controller is loaded (which expect all dependencies to be resolved before launch)
• Explicit (removing initial storyboard in plist and trying to set up in NSApplicationDelegate's applicationDidFinishLaunching) causes app never to launch. applicationDidFinishLaunching is never called when entry from plist is removed. Where to put initialization code?

I also found that when i use Implict initialization storyboardInitCompleted is never called:

extension SwinjectStoryboard{
    public static func setup() {
        defaultContainer.register(PlayerVCViewModelling.self){
            c in
            PlayerViewModel()
        }

        defaultContainer.storyboardInitCompleted(PlayerViewController.self){
            r,c in
            c.playerViewModel = r.resolve(PlayerVCViewModelling.self)
        }
    }
}

Can anyone please explain or give any tips how to properly instantiate Swinject Storyboard for OSX project?

Thanks

The README mentions you can do something like this in iOS apps to explicitly load your root view controller from SwinjectStoryboard:

let window = UIWindow(frame: UIScreen.mainScreen().bounds)
window.makeKeyAndVisible()
self.window = window

let storyboard = SwinjectStoryboard.create(name: "Main", bundle: nil, container: container)
window.rootViewController = storyboard.instantiateInitialViewController()

Is there an equivalent practice for macOS?

Hello,

I'm using the Library right now and during the last days I was doing some UI-tests retrieving some data market as Singleton from the SwinjectStoryboard instance.

The thing is that when I try to retrieve an unique instance from the library:

override func setUp() {
		accountStore = SwinjectStoryboard.defaultContainer.resolve(AccountStore.self)!
		super.setUp()
	}

The instance is not the same that I have on my ViewController, even when the Scope is ObjectScope.container :

class AccountStoreAssembly: Assembly {
    func assemble(container: Container) {
        container.register(AccountStoreController.self) { _ in
            AccountStoreController(dispatcher: container.resolve(Dispatcher.self)!,
                    repository: container.resolve(LumiereService.self)!)
        }.inObjectScope(ObjectScope.container)

        container.register(AccountStore.self) { _ in
            AccountStore(controller: container.resolve(AccountStoreController.self)!,
                    dispatcher: container.resolve(Dispatcher.self)!,
                    repository: container.resolve(LumiereService.self)!)
        }.inObjectScope(ObjectScope.container)
    }
}

This is normal? There is no way to keep the same instance for both places? Tests and normal application controllers? Is this an issue or it works as designed?

Thank you so much in advance!

From @gilgol on April 9, 2018 11:40

I'm trying to dynamically resolve a protocol ViewModeling that 2 different view models are conforming to..
I am able to do it on the service level (one protocol that 2 services are conforming to, and 2 different viewModel that each consume a different service can resolve the required one using a specific name)

I'm struggling with doing this on the viewController level, trying to inject the same view controller a specific viewModel (both conforms as mentioned to the same protocol).

I believe the issue is with SwinjectStoryboard that doesn't let me instantiate a view controller using its storyboard id (like I would normally do), and in addition define few different names that will be resolved on runtime.

Am I missing something?

Just realised it might be more appropriate as a stackoverflaw post, so here is a link to the post:
https://stackoverflow.com/questions/49732300/how-to-inject-the-right-viewmodel-to-a-single-viewcontroller

Copied from original issue: Swinject/Swinject#345

SwinjectStoryboard cannot hold reference to object or it resolves nil object when block of storyboardInitCompleted finished. That's why all objects in my ViewController are nil, it makes my app crash in Swift 4. But in Swift 3.3 is working fine. please help me to solve this problem.

Hi There i am getting the following compilation error. I added the library via CocoaPods

I'm following VIPER principles. And there are circular dependencies, for example between View(UIViewController)<->Presenter, Presenter<->Interactor.

How to resolve circular dependencies between UIViewController, for example

class LoginViewController: UIViewController, LoginViewInput {    
    var output: LoginViewOutput?

    override func viewDidLoad() {
        super.viewDidLoad()
        output?.didTriggerViewDidLoad();
    }

    func say(message: String?) {
        print(message)
    }
}

class LoginPresenter: LoginViewOutput {
    weak var view: LoginViewInput?

    func didTriggerViewDidLoad() {
        print("Did trigger View Did Load")
        view?.say(message: "Hello")
    }
}

I'm trying this way but it doesn't work

import Swinject
import SwinjectStoryboard

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

    var container: Container = {
        let container = Container()

        container.registerForStoryboard(LoginViewController.self) { r, c in
            c.output = r.resolve(LoginViewOutput.self)
        }
        container.register(LoginViewOutput.self) { _ in LoginPresenter() }
            .initCompleted { r, c in
                let presenter = c as! LoginPresenter
                presenter.view = r.resolve(LoginViewController.self)
        }

        return container
    }()


    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
        let window = UIWindow(frame: UIScreen.main.bounds)
        window.makeKeyAndVisible()
        self.window = window

        let storyboard = SwinjectStoryboard.create(name: "Main", bundle: nil, container: container)
        window.rootViewController = storyboard.instantiateInitialViewController()
        return true
    }
}

There is some discussion here
Thanks

Hi, I saw the similar question here but we can unite them later.
I'm trying to cook Swinject with VIPER and struggling the issue with registerForStoryboard on child container.
Here is the structure of how I'm trying to implement this. I want to achieve having one AssemblyType and Assembler per module.
Two modules:

class TabBarAssembler {
    
    let assembler: Assembler
    
    init(parentAssembler: Assembler) {
        assembler = try! Assembler(assemblies: [TabBarAssembly()], parentAssembler: parentAssembler)
    }
}

class TabBarAssembly: AssemblyType {
    
    func assemble(container: Container) {
        container.register(SketchesListAssembler.self) { r in
            let parentAssembler = r.resolve(TabBarAssembler.self)!
            return SketchesListAssembler(parentAssembler: parentAssembler.assembler)
        }
        container.registerForStoryboard(TabBarViewController.self) { (r, controller: TabBarViewInputProtocol) in
            let presenter = r.resolve(TabBarPresenterProtocol.self, argument: controller)!
            controller.presenter = presenter
        }
        container.register(TabBarInteractorInputProtocol.self) { _ in
            TabBarInteractor()
        }
        container.register(TabBarPresenterProtocol.self) { (r, view: TabBarViewInputProtocol) in
            let interactor = r.resolve(TabBarInteractorInputProtocol.self)!
            let router = r.resolve(TabBarRouterInputProtocol.self)!
            let presenter = TabBarPresenter(view: view, interactor: interactor, router: router)
            interactor.presenter = presenter
            return presenter
        }
        container.register(TabBarRouterInputProtocol.self) { r in
            let router = TabBarRouter()
            router.sketchesListAssembler = r.resolve(SketchesListAssembler.self)
            return router
        }
    }
}

class SketchesListAssembler {
    
    private let assembler: Assembler
    
    init(parentAssembler: Assembler) {
        assembler = try! Assembler(assemblies: [SketchesListAssembly()], parentAssembler: parentAssembler)
    }
    
}

class SketchesListAssembly: AssemblyType {
    
    func assemble(container: Container) {
        container.registerForStoryboard(SketchesListViewController.self) { (r, controller: SketchesListViewInputProtocol) in
            let presenter = r.resolve(SketchesListPresenterProtocol.self, argument: controller)!
            controller.presenter = presenter
        }
        container.register(SketchesListInteractorInputProtocol.self) { _ in
            SketchesListInteractor()
        }
        container.register(SketchesListPresenterProtocol.self) { (r, view: SketchesListViewInputProtocol) in
            let interactor = r.resolve(SketchesListInteractorInputProtocol.self)!
            let router = r.resolve(SketchesListRouterInputProtocol.self)!
            let presenter = SketchesListPresenter(view: view, interactor: interactor, router: router)
            interactor.presenter = presenter
            return presenter
        }
        container.register(SketchesListRouterInputProtocol.self) { _ in
            SketchesListRouter()
        }
    }
}

registerForStoryboard is used in both of them. And as you can see I'm passing Assembler to SketchesListAssembler as part of parent/child relationship. Resolver clusures are called in TabBarAssembly but never called in SketchesListAssembly.

The question is how to implement this in a proper way and to get SketchesListAssembly closures called?

Versions:
'Swinject', '2.0.0-beta.2'
'SwinjectStoryboard', '1.0.0-beta.2'

I am having trouble understanding how to combine different assemblies/assemblers with SwinjectStoryboard. I am using the implicit storyboard extension, but I want to separate assemblies for clean code.

Here is an example:

extension SwinjectStoryboard {
    public static func setup() {
        defaultContainer.register(ColorRandomizer.self) { _ in
            DefaultColorRandomizer()
        }
        defaultContainer.register(NameGenerator.self) { _ in
            DeveloperNameGenerator()
        }
        defaultContainer.storyboardInitCompleted(ViewController.self) { r, c in
            c.colorRandomizer = r.resolve(ColorRandomizer.self)
            c.nameGenerator = r.resolve(NameGenerator.self)
        }
    }
}

This works for the initial view controller, but let's say I have another assembly that I want to assemble. Am I supposed to do this?

let assembler = Assembler([SomeAssembly()], container: SwinjectStoryboard.defaultContainer)

Also I understand that I need to maintain a strong reference to the assembler, so should I have only 1 assembler, and apply assemblies when I need them? Should the assembler be in the AppDelegate?

When I try to implement extension for SwinjectStoryboard (with my own types of course), I get a compilation error "Value of type 'Container' has no member 'storyboardInitCompleted' "

I have created a subclass of UICollectionView and assigned this custom class into storyboard's collection view. I have to inject a shared object in that custom class.

// ViewController
class BZConnectSocialAcccountViewC: BZSignupWizardBase {

    @IBOutlet weak var collectionView: BZConnectSocialListView!
    
    required init?(coder aDecoder: NSCoder) {
        super.init(coder: aDecoder)
    }
    
    override func viewDidLoad() {
        super.viewDidLoad()

        // Do any additional setup after loading the view.
    }
}

// Sub Class
class BZConnectSocialListView: UICollectionView {
    
    var connectSocialAccountViewModeling: BZConnectSocialAccountViewModeling?
}

// View Model
protocol BZConnectSocialAccountViewModeling {
}

class BZConnectSocialAccountVM: BZConnectSocialAccountViewModeling {

 private var objApiManager: APIManagerModeling?
    init(_ apiManager: APIManagerModeling) {
        
        self.objApiManager = apiManager
    }
}

// API Manager

protocol APIManagerModeling {
}
class APIManager: SessionManager, APIManagerModeling {
}

// Injection

container.register(APIManagerModeling.self) { _ in
            APIManager()
        }.inObjectScope(.container)


container.register(BZConnectSocialAccountViewModeling.self) { r in
            BZConnectSocialAccountVM(r.resolve(APIManagerModeling.self)!)
        }

container.register(BZConnectSocialAcccountViewC.self) { r in
            
            return self.viewControllerFor(storyboard: self.storyboardSettings(className: BZConnectSocialAcccountViewC.self), identifier: BZConnectSocialAcccountViewC.className) as! BZConnectSocialAcccountViewC
            
            }.initCompleted { r, c in
                
                c.collectionView.connectSocialAccountViewModeling = r.resolve(BZConnectSocialAccountViewModeling.self)
                
        }

c.collectionView in getting nil

Hello,
I am just starting a new project today and have been having an issue with this error:

Cannot convert value of type 'Container.Controller' (aka 'UIViewController') to closure result type 'Any'

It's at line 108 in SwinjectStoryboard.swift.

Is this a known issue?

Thanks.

Xcode 9.2
Swift 4
pod 'SwinjectStoryboard', '1.1.2'

Update the project to support Swift 3 and follow the Swinject core repository:
Swinject/Swinject#113

Hello,

I'am starting a new project on Xcode 9 beta 5 (and tested today on beta 6) and the static function setup() is no longer called automatically. I need to call it manually in AppDelegate. But the issue with this workaround, the initial view controller is not injected only the next are injected.

Anybody have the same issue ?

Thank for helping.

Hi,
How can I register controllers which are instantiated by segues and especially, how they are resolved?

Next version of Cocoapods add static library support for Swift.

In SwinjectStoryboard+SetUp.m I have 'SwinjectStoryboard/SwinjectStoryboard-Swift.h' file not found.

Hi,
I'm wondering if i should use SwinjectStoryboard in my production code, this project has only 1 release 2 months ago, when will be production-ready version?

I'm facing with: No such module SwinjectStoryboard trying to use version 1.0.0 - Swift 3.

I'm getting the following errors when I try and build SwinjectStoryboard.framework after cloning with Carthage:

The file “Debug.xcconfig” couldn’t be opened because there is no such file. (/Users/mpdifran/Sandbox/Speedometer/Carthage/Checkouts/Swinject/Carthage/Checkouts/xcconfigs/Base/Configurations/Debug.xcconfig)
The file “iOS-Framework.xcconfig” couldn’t be opened because there is no such file. (/Users/mpdifran/Sandbox/Speedometer/Carthage/Checkouts/Swinject/Carthage/Checkouts/xcconfigs/iOS/iOS-Framework.xcconfig)
Build setting PRODUCT_NAME undefined

The SwinjectStoryboard.xcodeproj is included in my project as a sub-project. I'm also noticing that the Nimble and Quick subprojects are missing within SwinjectStoryboard.xcodeproj.

I am running the following Carthage command:

carthage update --use-ssh --platform iOS --no-use-binaries --no-build

I have recently upgraded a project to Xcode 9 and Swift 4.

The SwinjectStoryboard.setup() method is no longer firing.

also, UIViewControllers are not invoking their associated storyboardInitCompleted calls

This seems to be finally removed in Swift 4. Any suggested workarounds? This is a compile error in Storyboard+Swizzling.swift

... /Pods/SwinjectStoryboard/Sources/Storyboard+Swizzling.swift:25:30: error: method 'initialize()' defines Objective-C class method 'initialize', which is not permitted by Swift
    open override class func initialize() {