Able to build app, failed to run on device with can't remove previously installed assets error


#1

Hello there,

I am able to build the app without issue,
BUILD SUCCESSFUL
Total time: 7.754 secs
Project successfully built.

however, when I run it on device: tns run device, I couldn’t see it on my note5

i have this error on console

JS: AssetExtraction: Can’t remove previously installed assets in /data/user/0/org.nativescript.cocappng/files/app
JS: AssetExtraction: Can’t remove previously installed assets in /data/user/0/org.nativescript.cocappng/files/internal
JS: AssetExtraction: Can’t remove previously installed assets in

it says same previous installed assets unable to remove, however, when I get into the folder, I am not found the folders mentioned.

reboot my note5 device, didn’t help.

here is the package.json
{
“description”: “NativeScript Application”,
“license”: “SEE LICENSE IN “,
“readme”: “NativeScript Application”,
“repository”: “”,
“nativescript”: {
“id”: “org.nativescript.cocappng”,
“tns-android”: {
“version”: “3.0.1”
}
},
“dependencies”: {
@angular/animations”: “~4.0.0”,
"@angular/common": “~4.0.0”,
"@angular/compiler": “~4.0.0”,
"@angular/core": “~4.0.0”,
"@angular/forms": “~4.0.0”,
"@angular/http": “~4.0.0”,
"@angular/platform-browser": “~4.0.0”,
"@angular/platform-browser-dynamic": “~4.0.0”,
"@angular/router": “~4.0.0”,
“nativescript-angular”: “~3.0.0”,
“nativescript-theme-core”: “~1.0.4”,
“reflect-metadata”: “~0.1.8”,
“rxjs”: “~5.2.0”,
“tns-core-modules”: “~3.0.0”,
“zone.js”: “0.8.2”
},
“devDependencies”: {
“babel-traverse”: “6.4.5”,
“babel-types”: “6.4.5”,
“babylon”: “6.4.5”,
“lazy”: “1.0.11”,
“nativescript-dev-android-snapshot”: “^0..”,
“nativescript-dev-typescript”: “^0.4.0”,
“typescript”: “~2.2.1”
}
}


#2

Hey, I’d like to pitch in, since I was the one who put the error message to be logged in the first place - it is not something to be concerned, and perhaps it causes too much panic, when it was actually something diagnostic that I put there for my convenience.

There are likely other reasons for your app to fail on the device, and the ‘error’, (just a warning, really), does not appear to be the reason for that. It would greatly help if you posted the actual error screen or message that is output on app run.


#3

that make sense now, actually I solved the problem is irrelevant to the errors popped up. anyway, thanks for checking-in.

K


#4

That’s great to hear, thanks for following up!