Skip to content

Latest commit

 

History

History
66 lines (39 loc) · 2.6 KB

troubleshooting.md

File metadata and controls

66 lines (39 loc) · 2.6 KB
nav-title title description position
Troubleshooting
Troubleshooting
Known issues with NativeScript and their workarounds
18

Known Issues and Limitations

NativeScript {{site.current-version}} is known to have the following issues and limitations.

CLI

Problem

When you attempt to run any build-related operations for Android in the NativeScript CLI, the following message appears.:

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'app_name'.
> Could not resolve all dependencies for configuration ':_debugCompile'.

Workaround: Run $ android to launch the Android SDK Manager and download the Android Support Repository 21.0.0.

Problem

On OS X systems with Node.js 0.12.0 installed, you cannot work with the NativeScript CLI 0.9.0.
For additional information, see GitHub Issue #268: OSX issue with node 0.12.0.

Workaround:
You can choose between the following workarounds.

  • Update the NativeScript CLI to 0.9.1.
  • Revert Node.js to 0.10.36.

Problem

On OS X systems with Xcode 6.1 installed, you cannot run or debug apps on iOS 8.1.3 devices.
The developer disk images provided with the iOS SDK in Xcode 6.1 are not compatible with iOS 8.1.3. The NativeScript CLI uses these disk images to work with your attached iOS devices.

Workaround:
Update to Xcode 6.1.1 or later.

Problem

The debug command times out when you attempt to debug on Android devices or emulators and the debug tools do not start.
The debug command is configured with a 30-second timeout. On slower computer configurations, the CLI might exceed this timeout when connecting to your Android devices or emulators.

Workaround:
Re-run the debug command.

Problem

On OS X systems, the debug tools for Android never launch.
The NativeScript CLI uses the opener npm package to open Chrome. The current version of the package that the CLI uses cannot open the browser.

Workaround:
Update the opener package to a newer version. If this does not resolve the issue, try modifying your local copy of the package.

User Experience

Problem

When you run your app on Android device for the first time, the app loads very slowly and might appear to be unresponsive.
The issue reoccurs on every redeployment.

Workaround:
None. Wait for the app to load.

The NativeScript team is working on improving the performance of Android apps on initial run.