System.err: Calling js method onCreate failed - System.err: Error: Main entry is missing. App cannot be started. Verify app bootstrap #4801

Activity

1. Karabillie commented on Jul 3, 2019

   

   Karabillie

   on Jul 3, 2019

   Author

   More actions

   The STRANGEST of all is that when I run the application for the first time, it shows the error. When I change smt and then save it with hot reloading feature, it is shown perfectly.
2. eweb9ja commented on Jul 20, 2019

   

   eweb9ja

   on Jul 20, 2019

   More actions

   Hi, i m have same issue here, i think is bug from the new release/update
   any help please?
3. eweb9ja commented on Jul 20, 2019

   

   eweb9ja

   on Jul 20, 2019

   Last edited by eweb9ja

   More actions

   hi, Karabillie
   i hope you have to solve the problem?
   "System.err: Error: Main entry is missing. App cannot be started. Verify app bootstrap."

   if not; this is how i solve it:
   i think the problem is coming from the lazy_route_resource, and maybe other module was loaded up before AppModule, as a result, blocking it to load/bootstrap.

   • so i use normal routing
     *and i created a center shared Module to load all the modules; instead of adding the other Components to the AppModule and it works

   i hope this will help you and others who are having this same issue after updating or migrating
4. Karabillie commented on Jul 21, 2019

   

   Karabillie

   on Jul 21, 2019

   Last edited by Karabillie

   Author

   More actions

   Hi. Thanks for the reply. Unfortunately, it does not work. Can you provide your code sample of this solution? Thanks.
5. ParthMaisheri commented on Jul 22, 2019

   

   ParthMaisheri

   on Jul 22, 2019

   More actions

   Hi. Thanks for the reply. Unfortunately, it does not work. Can you provide your code sample of this solution? Thanks.

   having similar issue after migrating to 6.0.0 (on Android).
6. eweb9ja commented on Jul 22, 2019

   

   eweb9ja

   on Jul 22, 2019

   More actions

   Please NOTE the COMMENT Section:

   AppModule:
   /////////////////////////////////////////////////////////////////////////////////////////////////

   import { NgModule, NO_ERRORS_SCHEMA } from "@angular/core";
   import { NativeScriptModule } from "nativescript-angular/nativescript.module";
   import { NativeScriptUISideDrawerModule } from "nativescript-ui-sidedrawer/angular";

   import { AppRoutingModule } from "./app-routing.module";
   import { AppComponent } from "./app.component";

   // Center SharedModules ("SharedModulesModule") that connect other modules/shared-modules
   // With this, you can avoid over loading the AppModule; therefor allowing the AppModule run first

   import { SharedModulesModule } from './shared-modules/shared-modules.module';

   @NgModule({
   bootstrap: [
   AppComponent
   ],
   imports: [
   AppRoutingModule,
   NativeScriptModule,
   NativeScriptUISideDrawerModule,
   SharedModulesModule
   ],
   declarations: [
   AppComponent
   ],
   schemas: [
   NO_ERRORS_SCHEMA
   ]
   })
   export class AppModule { }

   App-Route.Module:
   /////////////////////////////////////////////////////////////////////////////////////////////////

   import { NgModule } from "@angular/core";
   import { Routes } from "@angular/router";
   import { NativeScriptRouterModule } from "nativescript-angular/router";

   import { WelcomeComponent } from './welcome/welcome.component';
   import { ChatRoomComponent } from './chat-room/chat-room.component';
   import { LoginComponent } from "./login/login.component";

   const routes: Routes = [

   // Make sure you run the redirectTo using a non-lazy router
   // i guess the lazy route loads the Other Modules before the AppModule
   
   { path: "", redirectTo: "/welcome", pathMatch: "full" },
   { path: 'welcome', component: WelcomeComponent },
   
   // These are the lazy_route from default SideDrawer installations
   
   { path: "home", loadChildren: "~/app/home/home.module#HomeModule" },
   { path: "browse", loadChildren: "~/app/browse/browse.module#BrowseModule" },
   { path: "search", loadChildren: "~/app/search/search.module#SearchModule" },
   { path: "featured", loadChildren: "~/app/featured/featured.module#FeaturedModule" },
   { path: "settings", loadChildren: "~/app/settings/settings.module#SettingsModule" },
   
   // The non-lazy route Component
   
   { path: 'chatroom', component: ChatRoomComponent },
   { path: "login", component: LoginComponent },
   

   ];

   @NgModule({
   imports: [NativeScriptRouterModule.forRoot(routes)],
   exports: [NativeScriptRouterModule]
   })
   export class AppRoutingModule { }

   SharedModulesModule:
   /////////////////////////////////////////////////////////////////////////////////////////////////

   import { NgModule, NO_ERRORS_SCHEMA } from '@angular/core';
   import { CommonModule } from '@angular/common';
   import { NativeScriptCommonModule } from "nativescript-angular/common";
   import { HttpClientModule } from "@angular/common/http";

   // Center SharedModules ("SharedModulesModule") that connect other modules/shared-modules

   import { ChatRoomComponent } from '../chat-room/chat-room.component';
   import { WelcomeComponent } from '../welcome/welcome.component';
   import { LoginComponent } from "../login/login.component";

   @NgModule({
   imports: [
   CommonModule, NativeScriptCommonModule,
   HttpClientModule
   ],
   declarations: [
   ChatRoomComponent,
   WelcomeComponent,
   LoginComponent

   ],
   providers: [
   // LoginService,

   ],
   schemas: [
   NO_ERRORS_SCHEMA
   ]

   })
   export class SharedModulesModule { }
7. eweb9ja commented on Jul 23, 2019

   

   eweb9ja

   on Jul 23, 2019

   More actions

   Also from this Error lines:
   System.err: Frame: function:'push.../node_modules/tns-core-modules/ui/frame...

   Make sure you add "tns-core-modules" to some of your imports:
   e.g:
   import { topmost } from "tns-core-modules/ui/frame";
   import { Page } from "tns-core-modules/ui/page";
   import { screen } from "tns-core-modules/platform";
   import * as app from "tns-core-modules/application";
   import { Color } from "tns-core-modules/color";
   etc
8. Fatme commented on Jul 24, 2019

   

   Fatme

   on Jul 24, 2019

   Contributor

   More actions

   @Karabillie,

   Angular CLI has a strict requirement for the version of typescript, meaning if your typescript version is not in the supported range, an error will be thrown and no javascript files will be produced. However, NativeScript CLI will not stop the command execution on this error and the application will be installed on device. When trying to start the application on device, an error will be thrown due to the missing javascript files.

   In order to check if this is the case with your project, can you please ensure that no errors are shown from webpack compilation - just scroll in your terminal till the beginning of the command and check for red messages.
9. ParthMaisheri commented on Jul 25, 2019

   

   ParthMaisheri

   on Jul 25, 2019

   More actions

   I restarted migration again with a backup and it works well.
10. eweb9ja commented on Jul 25, 2019

    

    eweb9ja

    on Jul 25, 2019

    More actions

    @ParthMaisheri
    good to hear that, wish you the best !
11. Fatme

    added

    needs more info

    on Jul 25, 2019
12. eweb9ja commented on Jul 25, 2019

    

    eweb9ja

    on Jul 25, 2019

    More actions

    @Karabillie
    what is the progress now ? i hope you have sort it out?
13. Karabillie commented on Jul 26, 2019

    

    Karabillie

    on Jul 26, 2019

    Author

    More actions

    @Fatme Hi! Sorry for the late reply. I also migrated to new new version of NativeScript but nothing changed. The only strange error that I am getting is:

    ERROR in e2e/app.e2e-spec.ts(12,45): error TS2345: Argument of type '"Welcome to app!!"' is not assignable to parameter of type 'Expected<Promise>'.

    For typescript version, I changed from ^3.4.5 to ~3.4.5.
14. Karabillie commented on Jul 26, 2019

    

    Karabillie

    on Jul 26, 2019

    Author

    More actions

    @eweb9ja Hi! Sorry for the late reply. Your solution did not work for me :/
15. Fatme

    self-assigned this

    on Jul 29, 2019
16. Fatme commented on Jul 30, 2019

    

    Fatme

    on Jul 30, 2019

    Contributor

    More actions

    @Karabillie,

    It seems that no .js files are emitted due to the error you mention.

    ERROR in e2e/app.e2e-spec.ts(12,45): error TS2345: Argument of type '"Welcome to app!!"' is not assignable to parameter of type 'Expected'.

    This is expecting to happen when noEmitOnError: true is set in your tsconfig.json file.
    We're trying to set it to false - noEmitOnError: false and expecting that .js files will be emitted and this will resolve the issue. However, this didn't help us and still no.js files were emitted.

    After investigating the issue, we found that the problem is in AngularCompilerPlugin and the way it handles typescript's compiler errors and options. We opened a PR in angular-cli repo fixing the described behavior - angular/angular-cli#15199.

    Meanwhile, you can fix your compilation error in e2e/app.e2e-spec.ts file in order to workaround this issue.

    👍React with 👍1Reacted by Antigoni Karavasili
17. KristianDD

    assigned

    DimitarTachev

    on Aug 5, 2019
18. DimitarTachev commented on Aug 8, 2019

    

    DimitarTachev

    on Aug 8, 2019

    Contributor

    More actions

    Hi @Karabillie,

    I'm closing the issue as we've isolated the problem and the issue with not pausing on Webpack errors is already logged.

    👍React with 👍1Reacted by Antigoni Karavasili
19. DimitarTachev

    closed this as completedon Aug 8, 2019
20. job111 commented on Aug 10, 2019

    

    job111

    on Aug 10, 2019

    More actions

    I'm facing the same issue and none of the suggestions above seems to be working
21. DimitarTachev commented on Aug 12, 2019

    

    DimitarTachev

    on Aug 12, 2019

    Contributor

    More actions

    @job111, please open a new issue following the issue template and providing the required versions and logs in order to allow us to investigate it further.