@xavibel Which version of the framework are you using?
The behavior that you’re describing seems similar to the one described in this issue:
I just confirmed that it’s fixed in beta.4 so the issue that you’re observing might be resolved as well (here’s a short guide on how to upgrade to beta.4).