-
-
Notifications
You must be signed in to change notification settings - Fork 197
System.err: Calling js method onCreate failed - System.err: Error: Main entry is missing. App cannot be started. Verify app bootstrap #4801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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. |
Hi, i m have same issue here, i think is bug from the new release/update |
hi, Karabillie if not; this is how i solve it:
i hope this will help you and others who are having this same issue after updating or migrating |
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). |
Please NOTE the COMMENT Section: AppModule: import { NgModule, NO_ERRORS_SCHEMA } from "@angular/core"; import { AppRoutingModule } from "./app-routing.module"; // Center SharedModules ("SharedModulesModule") that connect other modules/shared-modules import { SharedModulesModule } from './shared-modules/shared-modules.module'; @NgModule({ App-Route.Module: import { NgModule } from "@angular/core"; import { WelcomeComponent } from './welcome/welcome.component'; const routes: Routes = [
]; @NgModule({ SharedModulesModule: import { NgModule, NO_ERRORS_SCHEMA } from '@angular/core'; // Center SharedModules ("SharedModulesModule") that connect other modules/shared-modules import { ChatRoomComponent } from '../chat-room/chat-room.component'; @NgModule({ ], ], }) |
Also from this Error lines: Make sure you add "tns-core-modules" to some of your imports: |
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 |
I restarted migration again with a backup and it works well. |
@ParthMaisheri |
@Karabillie |
@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:
For typescript version, I changed from ^3.4.5 to ~3.4.5. |
@eweb9ja Hi! Sorry for the late reply. Your solution did not work for me :/ |
It seems that no
This is expecting to happen when After investigating the issue, we found that the problem is in Meanwhile, you can fix your compilation error in |
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. |
I'm facing the same issue and none of the suggestions above seems to be working |
@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. |
Environment
Describe the bug
I have a web application using Angular version 7 and decided to migrate it into a mobile application using NativeScript. After installing successfully nativescript and the schemantics plugins, I tried to run tns run android --bundle on an Android Emulator(Nexus 4 API 8), but I am getting the following error:
To Reproduce
tns run android --bundle
Expected behavior
Application should be executed successfully and show the auto-generated code.
I cannot upload the whole application, as my client does not allow me but if some parts of the application are needed, please let me know to share them.
The text was updated successfully, but these errors were encountered: