NativeScript: Unable to get application path on device. For tns run ios --emulator

Please, provide the details below:

When running tns run IOS --emulator, the project builds successfully, however, it presents the error Unable to apply changes on device: EC3591F5-20AE-495D-93A2-E8347F03D15D. Error is: Unable to get application path on device.

Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo?

Yes, this is a real problem.

Tell us about the problem

Which platform(s) does your issue occur on?

iOS

Please provide the following version numbers that your issue occurs with:

CLI: (run tns --version to fetch it): 3.4.3
Cross-platform modules: (check the ‘version’ attribute in the node_modules/tns-core-modules/package.json file in your project): 4.0.0
Runtime(s): (look for the "tns-android" and "tns-ios" properties in the package.json file of your project) 3.4.1
Plugin(s): (look for the version number in the package.json file of your project) Unknown

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 30 (11 by maintainers)

Most upvoted comments

In the iOS Simulator, try: Hardware > Erase All Content And Settings…

+52

nodro7 on Apr 28, 2018

Hi @mcaustin1, Can you check if this error is reproducible with the latest CLI and iOS runtime? To do that you can follow the below-attached steps:

npm uninstall nativescript --g
npm install nativescript --g
tns platform remove ios
tns platform add ios then delete the node_modules folder. Restart the simulator and build the project again tns run ios.

tsonevn on Apr 24, 2018

@gordonboyle Thanks a lot that was really really helpful… unable to apply changes on device

divyachandana on Jul 21, 2018

What I’ve found is when I get into this situation, just delete platforms dir and run again.

rynop on Jan 16, 2019

Deleting “platforms” folder worked for me too. Thanks!

asoufi on Apr 13, 2020

Thanks Mahmood. Yes, this is a good fix to keep developing, but it adds about an extra minute to the dev cycle per change. That’s totally unacceptable and needs to be actually fixed.

On Nov 10, 2018, at 6:50 AM, Zahid Mahmood notifications@github.com wrote:

I am also able to consistently reproduce this on macOS High Sierra on multiple test projects. The issue occurs for me when:

I copy a project as described by @alexziskind1, or I run tns run ios --bundle in directory A, create a new project with the same name in directory B and run ins run ios --bundle I solved this by resetting my Xcode 10 simulator device (or specifying a new one). Reset by opening the simulator device Hardware > Erase All Content and Settings. I did not need to reinstall nativescript globally.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

alexziskind1 on Nov 10, 2018

I’m able to consistently reproduce this on MacOS high sierra. When I’m running a project in a simulator and live syncing, if I go out to Finder and copy the project folder to another location (just copying using the UI, not moving), the app immediately crashes in the sim and restart attempts lead to this error. Maybe this will help troubleshoot

On Nov 8, 2018, at 2:52 AM, Nikolay Tsonev notifications@github.com wrote:

Hi all, We were able to recreate the issue on one of our machines. Currently, we are working on identifying what is causing it. Follow up issue #4095.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

alexziskind1 on Nov 8, 2018