-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
App crashes #358
Comments
Most crashes are on GalleryApp on Android Api18 default emulator. Here is what happens after 3-4 back navigations:
|
and one more:
|
Most of the failures are after 8th Feb 2016. |
This comment was marked as abuse.
This comment was marked as abuse.
As far as I can tell this seems to be a problem of x86 emulators with the GPU and/or GL/EGL support. I need more time to confirm it though. |
+1 |
This issue happens only on Api18 x86 emulators, can not reproduce on Api18 Arm devices and emulators. I'm not sure if there is a real device with Api18 and x86 CPU. |
If I use enableProdMode() in Angular I'm getting this error, also |
@hypery2k can you provide more details what emulator or device you use? Also, any logs from |
Getting this via logcat
The weird thing is on some devices it's working. It's only happening in a release build |
This comment was marked as abuse.
This comment was marked as abuse.
@hypery2k does this occur when you build in |
i'm using this to generate a release build for PlayStore:
|
@hypery2k it would help if you could share the CLI log from the moment you type in the command. What versions of the runtimes, modules, nativescript CLI are you using? |
Here's my package.json: "prerelease": "npm run buildnumbering && npm run changelog && git add CHANGELOG.md && git add package.json && git add app/App_Resources/Android/AndroidManifest.xml && git commit -m 'Release version' || echo'' && npm run clean",
"release": "cross-env NODE_ENV=production TNS_ANDROID_SNAPSHOT=1 KEYSTORE_PATH=$KEYSTORE_PATH KEYSTORE_PASS=$KEYSTORE_PASS npm run build-android-bundle -- --release --key-store-path $KEYSTORE_PATH --key-store-password $KEYSTORE_PASS --key-store-alias sample --key-store-alias-password $KEYSTORE_PASS",
"postrelease": "git checkout package.json && npm run buildnumbering",
"version-and-push": "git push origin master && git push origin --tags",
"release:major": "npm version major && npm run release && npm run version-and-push",
"release:minor": "npm version minor && npm run release && npm run version-and-push",
"release:patch": "npm version patch && npm run release && npm run version-and-push",
"start-android-bundle": "npm run ns-bundle --android --start-app",
"start-ios-bundle": "npm run ns-bundle --ios --start-app",
"build-android-bundle": "npm run ns-bundle --android --build-app",
"build-ios-bundle": "npm run ns-bundle --ios --build-app"
},
"nativescript": {
"id": "de.sample.app",
"tns-ios": {
"version": "2.5.0"
},
"tns-android": {
"version": "2.5.0"
}
},
"dependencies": {
"@angular/common": "2.4.9",
"@angular/compiler": "2.4.9",
"@angular/core": "2.4.9",
"@angular/forms": "2.4.9",
"@angular/http": "2.4.9",
"@angular/platform-browser": "2.4.9",
"@angular/platform-browser-dynamic": "2.4.9",
"@angular/router": "3.4.9",
"@ngx-translate/core": "6.0.0",
"@ngx-translate/http-loader": "0.0.3",
"nativescript-angular": "1.4.1",
"nativescript-appinfo": "0.3.1-develop-16",
"nativescript-barcodescanner": "2.4.0",
"nativescript-cardview": "1.3.2",
"nativescript-couchbase": "1.0.17",
"nativescript-drawingpad": "1.1.2",
"nativescript-fabric": "0.2.1",
"nativescript-loading-indicator": "2.2.2",
"nativescript-ngx-fonticon": "1.9.0",
"nativescript-permissions": "1.2.2",
"nativescript-plugin-firebase": "3.10.1",
"nativescript-pulltorefresh": "1.1.10",
"nativescript-theme-core": "1.0.2",
"nativescript-toast": "1.4.5",
"nativescript-urlhandler": "0.3.0-develop-19",
"ng2-validation": "3.8.0",
"reflect-metadata": "0.1.9",
"rxjs": "5.0.1",
"tns-core-modules": "2.5.1",
"tns-core-modules-widgets": "2.5.0",
"zone.js": "0.7.2"
},
"devDependencies": {
"@angular/compiler-cli": "2.4.9",
"@angular/tsc-wrapped": "0.5.0",
"@ngtools/webpack": "1.2.10",
"@types/jasmine": "2.2.29",
"@types/source-map": "0.1.26",
"@types/uglify-js": "2.0.27",
"babel-traverse": "6.11.4",
"babel-types": "6.11.1",
"babylon": "6.8.0",
"chai": "3.5.0",
"chai-as-promised": "5.3.0",
"codelyzer": "^2.0.0-beta.1",
"conventional-changelog-cli": "1.3.1",
"copy-webpack-plugin": "3.0.1",
"cross-env": "1.0.8",
"css-loader": "0.26.0",
"extract-text-webpack-plugin": "2.0.0-beta.4",
"filewalker": "0.1.2",
"fs": "0.0.2",
"htmlparser2": "3.9.2",
"jasmine-core": "2.4.1",
"jsonlint": "1.6.2",
"karma": "1.3.0",
"karma-coverage": "1.0.0",
"karma-jasmine": "1.0.2",
"karma-junit-reporter": "1.1.0",
"karma-nativescript-launcher": "0.4.0",
"karma-typescript-preprocessor": "0.3.0",
"lazy": "1.0.11",
"nativescript-css-loader": "0.26.1",
"nativescript-dev-sass": "0.4.2",
"nativescript-dev-typescript": "0.3.6",
"nativescript-dev-webpack": "0.3.5",
"nativescript-media-generator": "0.2.4-develop-32",
"nativescript-unit-test-runner": "0.3.4",
"node-sass": "4.5.0",
"raw-loader": "0.5.1",
"resolve-url-loader": "1.6.0",
"rimraf": "2.6.1",
"sass-loader": "6.0.2",
"tslint": "4.0.1",
"tslint-eslint-rules": "1.3.0",
"typescript": "2.1.6",
"webpack": "2.2.1",
"webpack-sources": "0.1.3",
"xml2js": "0.4.16"
},
"license": "UNLICENSED",
"engine-strict": true,
"engines": {
"node": ">= 6",
"npm": ">= 3"
} And here the build log
|
@hypery2k it appears to be unrelated to snapshots failure as initially suggested. I would like to ask you to do something for me, so a better stacktrace is output in release. remove platform, install platform, navigate to |
here it comes:
|
@hypery2k that looks like a different crash to what you posted originally. It's an SQLite error, not sure which plugin causes it. You might have to open a new issue so that it's reviewed as its own separate case. |
that's strange, because not using sqlite at all. We're using couchbase. This issue occurs on Samsung and Nexus device, but on HTC device it's working. Very strange. |
maybe this helps more:
|
strange, it's working if I run the build twice. So these are the steps I'm doing seems to succeed:
If I omit step 3 I get the above error |
@hypery2k the stacktrace you shared shows that the application cannot initialize because an exception is thrown while bootstrapping the JS engine. Probably unrelated to your code, but somehow caused by the steps you perform to build the app. Please open a new issue with a minimal sample project and steps to reproduce so that we may get to the bottom of the problem. Thank you! |
I will try to setup a sample project to reproduce this issue |
@hypery2k did you manage to create a simple project to reproduce the issue? |
Currently, I'm looking at why do we crash and burn instead of giving a proper readable exception, when the fabric plugin isn't configured correctly. Thank you for providing the repo, it was very useful to us. |
Glad to help |
@Plamen5kov I'm the author of the fabric plugin. Could you at details here to guide me to solution for this? Would be great if you give me hint to resolve it. |
@hypery2k, what you're trying to do is add a classpath to the gradle configuration and then include dependencies you need for your plugin. You can take a look at the nativescript-firebase-plugin which does everything you need and more. |
but why is the build itself working, but the app is crashing? |
Because the dependency isn't added properly, so it's not included in the build. That doesn't cause compile errors because the types are used in javascript which does not get compile and you're using the dependencies run-time. |
@Plamen5kov do you have an idea? I changed the build according to your suggestions, but it's still failing: https://travis-ci.org/hypery2k/nativescript-fabric/builds/315409300 |
sorry, the logcat output is in saucelabs:
|
I've found the error. I have to alter the existing buildscript entry in build.gradle. It's no enough to just add another. I think I can publish a fixed version of my plugin tomorrow. Thanks for your support. BTW: Is it possible to make add more debug logging to find such errors? |
Strange, now getting a new error:
you try yourself with my demo app here and adding Update: If I do an additional |
@Plamen5kov Any suggestion on how to fix this? |
@hypery2k I'll investigate and get back to you. |
@Plamen5kov thanks. Glad to hear from you |
@hypery2k I get the error:
which is caused by a missing file The steps that I try to reproduce the issue are:
Please tell me if I'm doing something wrong, so I can investigate further. |
you could give this a try:
|
@hypery2k When I follow your steps the application builds and I don't find any build or runtime errors, is there a way to check if the plugin is working or not? |
ah forgotten, did you switch to branch bugfix/android? |
@hypery2k will give it a try today. Edit: After trying the updated steps the plugin asks for:
|
@Plamen5kov: Could you please update your cloned repo and retry? |
@hypery2k I managed to reproduce the issue and after some manual changes I managed to run the application:
Currently, you're trying to add a subproject that does these changes, but although that might work for applying the As I suggested earlyer, you can take a look at the nativescript-plugin-firebase plugin to see exactly how to do this automatically. I wouldn't recommend to change the Hope this helps! |
thanks for the feedback. I thought I already applied all of the firebase plugin. I will take a look |
@Plamen5kov I still having issues:
I pushed my changes again to the branch. If you could have a look at it |
@hypery2k, everything is ok now, but because we have a bug in the 3.3.0 tns-android template, your plugin is not getting applied. As a temporary workaround I can suggest putting the |
@hypery2k I managed to reproduce the problem. There's one more thing necessary that I mentioned: |
thanks for the hint. I’ve solved the build issue and will now focus on app start issue |
Various app crashes reported from QA team
http://nsbuild01.telerik.com:8080/build/view/Stable/view/App%20Cuteness/job/integration-tests-stable-cuteness-android-api18-emulator/251/
The text was updated successfully, but these errors were encountered: