Skip to content

Release build crashes on startup but debug build does not crash #702

Closed

Description

@zahid-dapperapps

My app's debug mode builds installs and works okay on any android device but the release build just crashes on startup.

Below is my crash log that I got from adb logcat *:E

02-03 14:41:04.829 14098 14098 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x7 in tid 14098 (.sol.net)
02-03 14:41:04.880 401 401 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-03 14:41:04.880 401 401 F DEBUG : Build fingerprint: 'lge/tiger6_lgu_kr/tiger6:6.0/MRA58K/162880915f9c3:user/release-keys'
02-03 14:41:04.880 401 401 F DEBUG : Revision: '10'
02-03 14:41:04.880 401 401 F DEBUG : ABI: 'arm'
02-03 14:41:04.880 401 401 F DEBUG : pid: 14098, tid: 14098, name: .sol.net >>>
com.sol.net <<<
02-03 14:41:04.880 401 401 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7
02-03 14:41:04.893 401 401 F DEBUG : r0 ffffffff r1 0000000c r2 beeb03a0 r3 beeb1fcc
02-03 14:41:04.893 401 401 F DEBUG : r4 beeb03f8 r5 0000000c r6 00000000 r7 000045dc
02-03 14:41:04.893 401 401 F DEBUG : r8 beeb03a0 r9 beeb03f8 sl b482d800 fp beeb0350
02-03 14:41:04.893 401 401 F DEBUG : ip beeb1fdf sp beeb0330 lr 9b20b34c pc 9b2458bc cpsr 60010010
02-03 14:41:04.895 401 401 F DEBUG :
02-03 14:41:04.895 401 401 F DEBUG : backtrace:
02-03 14:41:04.895 401 401 F DEBUG : #00 pc 001498bc /data/app/com.sol.net-1/lib/arm/libNativeScript.so
02-03 14:41:04.895 401 401 F DEBUG : #1 pc 0010f348 /data/app/com.sol.net-1/lib/arm/libNativeScript.so
02-03 14:41:04.896 401 401 F DEBUG : #2 pc 0061d7f0 /data/app/com.sol.net-1/lib/arm/libNativeScript.so
02-03 14:41:04.896 401 401 F DEBUG : #3 pc 0061d874 /data/app/com.sol.net-1/lib/arm/libNativeScript.so
02-03 14:41:04.896 401 401 F DEBUG : #4 pc 0061c790 /data/app/com.sol.net-1/lib/arm/libNativeScript.so
02-03 14:41:05.153 401 401 F DEBUG :
02-03 14:41:05.153 401 401 F DEBUG : Tombstone written to: /data/tombstones/tombstone_02
02-03 14:41:05.153 401 401 E DEBUG : AM write failed: Broken pipe

  • CLI: 2.5.0
  • Cross-platform modules: 2.5.0
  • Runtime(s): 2.5.0

Below is my project's package.json

{
"description": "NativeScript Application",
"license": "SEE LICENSE IN ",
"readme": "NativeScript Application",
"repository": "",
"nativescript": {
"id": "org.nativescript.net",
"tns-ios": {
"version": "2.5.0"
},
"tns-android": {
"version": "2.5.0"
}
},
"dependencies": {
"@angular/common": "2.2.1",
"@angular/compiler": "2.2.1",
"@angular/core": "2.2.1",
"@angular/forms": "2.2.1",
"@angular/http": "2.2.1",
"@angular/platform-browser": "2.2.1",
"@angular/platform-browser-dynamic": "2.2.1",
"@angular/router": "3.2.1",
"nativescript-angular": "1.2.0",
"nativescript-angular-snapshot": "1.2.0-5.2.361-2",
"nativescript-dom": "^1.0.8",
"nativescript-drop-down": "^1.5.1",
"nativescript-iqkeyboardmanager": "^1.0.1",
"nativescript-pulltorefresh": "^1.1.10",
"nativescript-telerik-ui": "^1.6.0",
"nativescript-theme-core": "^0.2.1",
"nativescript-xmlobjects": "^1.1.4",
"reflect-metadata": "~0.1.8",
"rxjs": "5.0.0-beta.12",
"tns-core-modules": "^2.5.0"
},
"devDependencies": {
"babel-traverse": "6.21.0",
"babel-types": "6.21.0",
"babylon": "6.14.1",
"lazy": "1.0.11",
"nativescript-dev-android-snapshot": "0.0.5",
"nativescript-dev-typescript": "^0.3.2",
"typescript": "~2.0.10",
"zone.js": "~0.6.21"
}
}

Activity

  1. petekanev commented on Feb 3, 2017

    @petekanev
    Contributor

    @zahid-dapperapps The error is most likely caused because a snapshot for a previous runtime version is used.

    Please delete node_modules directory and the "nativescript-angular-snapshot": "1.2.0-5.2.361-2" entry from your package.json, followed by updating the nativescript-dev-android-snapshot plugin.

    rm -rf node_modules
    rm -rf platforms
    npm remove nativescript-angular-snapshot --save
    npm install nativescript-dev-android-snapshot --save-dev
    tns platform add android
    tns build --release .....

  2. self-assigned this
    on Feb 3, 2017
  3. petekanev commented on Feb 6, 2017

    @petekanev
    Contributor

    Closing this as resolved. Let me know if you are facing other problems regarding the upgrade 2.4 - 2.5

  4. Dimitrievskislavcho commented on Apr 26, 2017

    @Dimitrievskislavcho

    I tried that and it fixed the issue, thanks for the hint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions