There are several reasons for every single point, I will try to summarize them up:
- I use NativeStorage since I've read many articles that recommended to actually use native over hybrid where possible. In this case, the migration from Storage to NativeStorage is significantly easier than what it may look like, since I use a wrapper logic which is indipendent from the type of driver or the type of module used.
- Providers are not declared in the app module because I have two different core of the current applications, and each of them uses different services, so the app component is injecting the common providers only, while other components are injecting the other necessary providers, this reduces loading times by a whole lot.
- I'm instantiating Promises manually because I'm used to program in this way, it's far easier to mantain the code if there is any change in an external library, because (again) the wrapper is still the same, so the changes that needs to be applied to mantain the code are minimal.
- I was unable to use git in this case, hence I was forced to copy and paste the project. This should have no impact though, because a brand new project was created, and relevant files were copied to it, and each step that was done in windows was replicated in MacOSx.
So, is there any relevant reason why constructor seems not to be even called? Is there any other solution other than migrating back to the regular Storage module?
It's not an heavy change, I'm just not getting why it doesn't even tell me why it's not working. No console error is shown, and constructors are not being called whatsoever in iOS, while in every single android device everything is being called and logged aswell.