AlexeyPoldeo

Correct behaviour: 

``` @interface AppAssembly : TyphoonAssembly + (AppAssembly *) create { AppAssembly *assembly = [[AppAssembly new] activated]; NSUserDefaults *userDefaults = [NSUserDefaults standardUserDefaults]; [assembly inject:[userDefaults rac_channelTerminalForKey:@"currentUserId"] withSelector:@selector(currentUserIdDefault)]; return assembly; } ```

For test purposes I've put **[AppAssembly create]** into **viewDidLoad** and inside this method everything works fine. But In the other method (button press callback) I can see reference to **AppAssembly**...

When I checking assemblies created in **PocketForecast** sample app, I see that it has **TyphoonBlockComponentFactory** instance class. Mine's are **TyphoonAssemblyAccessor**. I'm really confused...

With all my respect, but I see too many limitations in comparison to Dagger 2. It's possible to name it as features, but they are not... Senior developers, who are...

Thank you for details, Jasper, but I didn't got what I did wrong... I've created assembly and it's fabric died after finishing the enclosing method. Example: @property (nonatomic) TestAssemply *assembly;...

Very useful patch, thanks! You need to publish your fork on cocoapods...

In my case it was version conflict with another copy included as a dependency for SnappyDB

No reaction on this critical issue upsets... Can SnappyDB be considered as production having such flaw? I've just hit something similar on instrumental testing. Trying to guess why it shouldn't...