You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I am running my app in debug mode (before building I delete hooks, node_modules and platforms folders), it builds successfully, but then the following happens:
The app keeps working fine afterwards, but it seems like it is trying to delete some temporary data and cannot, this results in ~30s more startup time, when I make changes to my app. This is android app, testing on Samsung Galaxy S5 mini.
@dxshindeo the The system failed to delete the package for an unspecified reason message is a bit cryptic, but what it means, is that the CLI attempted to delete the previous package with the same appId and failed, because no such package is present on the device. This message is harmless and can be safely ignored.
@dxshindeo commented on Thu Feb 02 2017
When I am running my app in debug mode (before building I delete hooks, node_modules and platforms folders), it builds successfully, but then the following happens:
The app keeps working fine afterwards, but it seems like it is trying to delete some temporary data and cannot, this results in ~30s more startup time, when I make changes to my app. This is android app, testing on Samsung Galaxy S5 mini.
My package.json:
@Pip3r4o commented on Thu Feb 02 2017
@dxshindeo the
The system failed to delete the package for an unspecified reason
message is a bit cryptic, but what it means, is that the CLI attempted to delete the previous package with the sameappId
and failed, because no such package is present on the device. This message is harmless and can be safely ignored.@dxshindeo commented on Thu Feb 02 2017
When updating the app, not rebuilding it, error is a bit cleaner:
@dxshindeo commented on Thu Feb 02 2017
Even did a fallback to previous rxjs module
"rxjs": "5.0.3"
, but the same story. Altough, the error is a bit shorter I think:@Pip3r4o commented on Thu Feb 02 2017
The issue appears to be related to #2469
The text was updated successfully, but these errors were encountered: