Closed cerealexx closed 5 years ago
Hi @cerealexx, I checked your case with our sdk example, however, was unable to recreate such an issue. Can you send us a sample project, that can be used for recreating the problem?
Hey @tsonevn. Unfortunately this is production app. I cannot send the code. I already knew you wouldn't be able to recreate it just with the module code I added since it makes no sense that it doesn't work and I'm not able myself. But it's really weird that this only happens in iOS, only with this module and only after upgrading NS to use webpack. I just hoped for a clue to try to find the problem by myself providing this info. Thanks anyway.
I isolated the bug until I found there is some kind of incompatibility with the Text to Speech plugin. The error thrown was really cryptic though and seemed to had to do with module routing and webpack. Everything is good now, thanks.
Hi @cerealexx, In my opinion, we can close this issue for now. We can reopen it when we have a stable way to reproduce the problem.
Environment Provide version numbers for the following components (information can be retrieved by running
tns info
in your project folder or by inspecting thepackage.json
of the project):Describe the bug Since the project was upgraded to webpack, when navigating to a concrete module the console returns
Error: Cannot find 'ForMeModule' in '~/for-me/for-me.module'
It is a lazy loaded module, it is imported as all the other route modules which work fine and the error only happens in iOS.app.routing.ts
for-me.module.ts
for-me.routing.ts
To Reproduce
Tap on any link to for-me route.
Expected behavior
Load the view.