I recently migrated an angular 10 project to nativescript 7 and have successfully rendered the app using npm run ios or npm run android.
The problem I am facing now is when I run "npm run ios" the ios emulator automatically always displays an ipad air 3rd gen. After looking at the documentation I tried to use the --device parameter with npm run ios (i.e. npm run ios --device "iPhone 8" but have run into issues when trying to do so I get the following error:
"The input is not valid sub-command for 'run' command."
Any help with this will be greatly appreciated so I can start deciding which devices I wanna work with.
Cheers!
From spotlight search, try to write “Simulator”, which will most likely start an iPad. Go to “File->Open Simulator” and pick an iPhone. Once that has started, close the iPad and run
ns devices list
That should yield something like
┌───┬────────────────────┬──────────┬──────────────────────────────────────┬──────────┬───────────┬─────────────────┐
│ # │ Device Name │ Platform │ Device Identifier │ Type │ Status │ Connection Type │
│ 1 │ iPhone 8 │ iOS │ E3270BFF-79A5-44A9-8119-5A398A3EA7CB │ Emulator │ Connected │ Local │
└───┴────────────────────┴──────────┴──────────────────────────────────────┴──────────┴───────────┴─────────────────┘
then run
ns run ios --no-hmr --device E3270BFF-79A5-44A9-8119-5A398A3EA7CB
(the command needs the device id, not the device name)
I'm new to Mac, to macOS development and to NativeScript.
I'm trying to start a new tns project using:
sudo tns create rsrpt --ng
and I get this error all the time:
Error: EACCES: permission denied, mkdir '/Users/myUser/code/rsrpt/hooks'
Out of frustration, after 10 hours, I ran the following commands:
sudo chown -R $(whoami) ~/.local
and even this: (I hope I didn't ruin permissions on this mac)
sudo chown -R $(whoami) ~/
But nothing helped. I still get the attached detailed error. Any help on how to overcome this permission problem would be appreciated! Thanks!
> nativescript-angular#6.1.0 postinstall /Users/myUser/code/rsrpt/node_modules/nativescript-angular
> node postinstall.js
fs.js:885
return binding.mkdir(pathModule._makeLong(path),
^
Error: EACCES: permission denied, mkdir '/Users/myUser/code/rsrpt/hooks'
at Object.fs.mkdirSync (fs.js:885:18)
at Object.<anonymous> (/Users/myUser/code/rsrpt/node_modules/nativescript-angular/postinstall.js:11:12)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nativescript-angular#6.1.0 postinstall: `node postinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nativescript-angular#6.1.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/myUser/.npm/_logs/2018-08-14T00_22_47_432Z-debug.log
Command npm install failed with exit code 1
# tns create
┌───────────────┬────────────────────────────────────────────────────────────┐
│ Usage │ Synopsis │
│ Create from │ $ tns create <App Name> [--path <Directory>] [--appid <App │
│ default │ ID>] │
│ JavaScript │ │
│ template │ │
│ Create from │ $ tns create <App Name> --template typescript [--path │
│ default │ <Directory>] [--appid <App ID>] OR $ tns create <App Name> │
│ TypeScript │ --tsc [--path <Directory>] [--appid <App ID>] OR $ │
│ template │ tns create <App Name> --template tsc [--path <Directory>] │
│ │ [--appid <App ID>] │
│ Create from │ $ tns create <App Name> --template angular [--path │
│ default │ <Directory>] [--appid <App ID>] OR $ tns create <App Name> │
│ Angular │ --template ng [--path <Directory>] [--appid <App ID>] │
│ template │ OR $ tns create <App Name> --ng [--path <Directory>] [- │
│ │ -appid <App ID>] │
│ Copy from │ $ tns create <App Name> [--path <Directory>] [--appid <App │
│ existing │ ID>] │
│ project │ │
│ Create from │ $ tns create <App Name> [--path <Directory>] [--appid <App │
│ custom │ ID>] --template <Template> │
│ template │ │
└───────────────┴────────────────────────────────────────────────────────────┘
Creates a new project for native development with NativeScript.
### Options
* --path - Specifies the directory where you want to create the project, if different from the current directory. The directory must be empty.
* --appid - Sets the application identifier for your project.
* --template - Specifies a valid npm package which you want to use to create your project. If --template is not set, the NativeScript CLI creates the project from the default JavaScript hello-world template.
* --ng - Sets the template for your project to the Angular template.
* --tsc - Sets the template for your project to the TypeScript template.
### Attributes
* <App Name> is the name of project. The specified name must meet the requirements of all platforms that you want to target. For more information about the <App Name> requirements, run $ tns help create
* <App ID> is the application identifier for your project. It must be a domain name in reverse and must meet the requirements of all platforms that you want to target. If not specified, the application identifier is set to org.nativescript.<App name> For more information about the <App ID> requirements, run $ tns help create
Did you try “tns doctor”? I am not sure is it checking permissions or authority rules.
And did you try for another directory? Maybe you need to re-install complate(npm&nativescript)
I'm following the Quickstart for Mac OS X to install the cloud SDK. Following the steps exactly,
1) python -V returns "Python 2.7.10"
2) Download and extract using ./install.sh the 64bit version of the SDK in google-cloud-sdk returns...
Welcome to the Google Cloud SDK!
To help improve the quality of this product, we collect anonymized usage data
and anonymized stacktraces when crashes are encountered; additional information
is available at <https://cloud.google.com/sdk/usage-statistics>. You may choose
to opt out of this collection now (by choosing 'N' at the below prompt), or at
any time in the future by running the following command:
gcloud config set disable_usage_reporting true
Do you want to help improve the Google Cloud SDK (Y/n)? Y
Your current Cloud SDK version is: 170.0.1
The latest available version is: 170.0.1
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Components │
├───────────────┬──────────────────────────────────────────────────────┬──────────────────────────┬───────────┤
│ Status │ Name │ ID │ Size │
├───────────────┼──────────────────────────────────────────────────────┼──────────────────────────┼───────────┤
│ Not Installed │ App Engine Go Extensions │ app-engine-go │ 97.7 MiB │
│ Not Installed │ Cloud Bigtable Command Line Tool │ cbt │ 4.0 MiB │
│ Not Installed │ Cloud Bigtable Emulator │ bigtable │ 3.5 MiB │
│ Not Installed │ Cloud Datalab Command Line Tool │ datalab │ < 1 MiB │
│ Not Installed │ Cloud Datastore Emulator │ cloud-datastore-emulator │ 15.4 MiB │
│ Not Installed │ Cloud Datastore Emulator (Legacy) │ gcd-emulator │ 38.1 MiB │
│ Not Installed │ Cloud Pub/Sub Emulator │ pubsub-emulator │ 33.2 MiB │
│ Not Installed │ Emulator Reverse Proxy │ emulator-reverse-proxy │ 14.5 MiB │
│ Not Installed │ Google Container Local Builder │ container-builder-local │ 3.7 MiB │
│ Not Installed │ Google Container Registry's Docker credential helper │ docker-credential-gcr │ 2.2 MiB │
│ Not Installed │ gcloud Alpha Commands │ alpha │ < 1 MiB │
│ Not Installed │ gcloud Beta Commands │ beta │ < 1 MiB │
│ Not Installed │ gcloud app Java Extensions │ app-engine-java │ 128.1 MiB │
│ Not Installed │ gcloud app PHP Extensions (Mac OS X) │ app-engine-php-darwin │ 21.9 MiB │
│ Not Installed │ gcloud app Python Extensions │ app-engine-python │ 6.5 MiB │
│ Not Installed │ kubectl │ kubectl │ 15.9 MiB │
│ Installed │ BigQuery Command Line Tool │ bq │ < 1 MiB │
│ Installed │ Cloud SDK Core Libraries │ core │ 6.7 MiB │
│ Installed │ Cloud Storage Command Line Tool │ gsutil │ 3.0 MiB │
└───────────────┴──────────────────────────────────────────────────────┴──────────────────────────┴───────────┘
To install or remove components at your current SDK version [170.0.1], run:
$ gcloud components install COMPONENT_ID
$ gcloud components remove COMPONENT_ID
To update your SDK installation to the latest version [170.0.1], run:
$ gcloud components update
==> Source [/Users/shaneoseasnain/Desktop/google-cloud-sdk/completion.bash.inc] in your profile to enable shell command completion for gcloud.
==> Source [/Users/shaneoseasnain/Desktop/google-cloud-sdk/path.bash.inc] in your profile to add the Google Cloud SDK command line tools to your $PATH.
For more information on how to get started, please visit:
https://cloud.google.com/sdk/docs/quickstarts
3) I've restarted the terminal and run gcloud init from inside google-cloud-sdk. This returns "command not found." If I run ls, I see the following directory structure:
LICENSE completion.zsh.inc path.fish.inc
README deb path.zsh.inc
RELEASE_NOTES install.bat platform
VERSION install.sh properties
bin lib rpm
completion.bash.inc path.bash.inc
4) I've tried to run gcloud init inside bin as well, but get the same problem, command not found.
The only other suggestions I can see from the install guide are "enable command-completion in your bash shell, and/or enable usage reporting." I'm not sure how to do this but command completion and reporting don't look like they should be related to this problem. There is a lot written about command not found but they relate to other problems where, for example, gcloud has stopped working after a while or problems in older versions. Has anyone a tip how to get the cloud sdk working?
Thanks
I had the same issue. A lazy and quick fix for this is to just run:
brew install --cask google-cloud-sdk
Found by googling.
For MAC OS - Use Homebrew
brew install --cask google-cloud-sdk
and then use
source "$(brew --prefix)/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc"
source "$(brew --prefix)/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.zsh.inc"
The gcloud executable lives in google-cloud-sdk/bin–to run gcloud. You'll need to either:
Add this directory to your $PATH. In particular, adding the line source /Users/shaneoseasnain/Desktop/google-cloud-sdk/path.bash.inc to your .bash_profile file (more detail on what this file does and how to pick one) will do the trick.
Specify the full path to the gcloud executable when you run it. In your case, this is /Users/shaneoseasnain/Desktop/google-cloud-sdk/bin/gcloud. So for example:
$ /Users/shaneoseasnain/Desktop/google-cloud-sdk/bin/gcloud init
The pertinent part of the quickstart (emphasis added):
Run the install script to add Cloud SDK tools to your path, enable command-completion in your bash shell, and/or enable usage reporting:
As to why the install script didn't work, I can't say. Please file an issue and we'll investigate.
Here's on macOS. I had the same problem. I got
gcloud: command not found
After running brew install --cask google-cloud-sdk, I found that I have to install it manually.
First, you will find install.sh under directory google-cloud-sdk, and you will run
.../google-cloud-sdk/install.sh
under the terminal. For my case,
the file is under
/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk
Second, run /usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/install.sh
Third, there will be a message guide you to relaunch your terminal owing to your bash file or zsh file updated.
Fourth, gcloud -v to test if gcloud-cli work normally after you launch a new terminal.
In short:
emacs -nw ~/.zshrc
And add following line at the beginning:
# The next line updates PATH for the Google Cloud SDK.
source '/home/lesaint/GOOGLE_CLOUD/google-cloud-sdk/path.zsh.inc'
# The next lines enables bash completion in Zsh for gcloud.
autoload -U compinit compdef
compinit
source '/home/lesaint/GOOGLE_CLOUD/google-cloud-sdk/completion.zsh.inc'
The solution proposed by following article works for me:
http://www.javatronic.fr/tips/2014/10/17/installing_google_cloud_sdk_on_ubuntu_with_oh-my-zsh.html
TL;DR - follow the Interactive installer section of Installing Cloud SDK and the SDK will install correctly.
However, there is a real issue here which I believe is related to missing environment variables:
At first, I followed Quickstart for Mac OS X as well in order to install the Google Cloud SDK for the 'Mac OS X (x86_64) Platform'. This reproduced the exact same results as Shane outlined in his question above. Here are some more details:
Clean install of macOS Sierra 10.12.6 (latest) on a 2017 MacBook Pro.
Google Cloud SDK version 173.0.0. Specifically: google-cloud-sdk-173.0.0-darwin-x86_64.tar.gz which is the latest at the time of this writing and the one pointed to by the quickstart guide.
I was able to further pinpoint the problem in step 4 of the 'Before you begin' section of Quick Start for Mac OS X:
Set up the Cloud SDK for use. If you're having trouble getting the gcloud command to work, ensure your $PATH is defined appropriately. Run the install script to add Cloud SDK tools to your path, enable command-completion in your bash shell, and/or enable usage reporting:
./google-cloud-sdk/install.sh
'install.sh' invokes 'install.py' which at some point calls isatty() in order to find out whether the installation process was run from the shell which means it should be interactive and prompt the user for some information. For some reason, isatty() returns False instead of True! This causes to script to fall through non-interactively and - because 'install.sh' was invoked without arguments - Fail.
The following worked for me:
I moved the installer unzipped package to the ~ directory.
And then after running ./google-cloud-sdk/install.sh
I restarted the terminal again and ran 'gcloud init' and it worked.
Sometimes, after installation, you need just restart your terminal. that's it :)
take a look at here: Quickstart for macOS
for me that was the fix:
mkdir -p $sdk_dir/.install/
tl;dr;
It seems that the python library is locating the sdk_root by searching for an .install directory. See the config.py and the definition of CLOUDSDK_STATE_DIR
It seems like your google-cloud-sdk/bin does not appear in PATH.
copy your current PATH from:
echo $PATH
Now add your google-cloud-sdk/bin absolute path to PATH, don't forget to add a colon - ':', before you add your new path, it should be something like this:
PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/Users/user/google-cloud-sdk/bin
I ran the install and init command from the folder, i kept downloaded SDK.
One it installed and initialized, i ran the command with folder name and it worked after that.
i ran below command from directory where i kept SDK-
./google-cloud-sdk/bin/gcloud
Follow these steps:
Press Command+Space and type Terminal and press enter/return key.
Run in Terminal app:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null ; brew install caskroom/cask/brew-cask 2> /dev/null
If the screen prompts you to enter a password, please enter your Mac's user password to continue. When you type the password, it won't be displayed on the screen, but the system would accept it. So just type your password and press ENTER/RETURN key. Then wait for the command to finish.
Run
brew cask install google-cloud-sdk
Reference:
http://macappstore.org/google-cloud-sdk/
I recently updated all my tns deps:
karlis#karlis-SATELLITE-L750 ~/Projects/my-instagram/test $ tns info
All NativeScript components versions information
┌──────────────────┬─────────────────┬────────────────┬─────────────┐
│ Component │ Current version │ Latest version │ Information │
│ nativescript │ 2.3.0 │ 2.3.0 │ Up to date │
│ tns-core-modules │ 2.3.0 │ 2.3.0 │ Up to date │
│ tns-android │ 2.3.0 │ 2.3.0 │ Up to date │
│ tns-ios │ 2.3.0 │ 2.3.0 │ Up to date │
When i change something in code and save, this shows up in console. However nothing changes in the app( closing and opening the app doesn't help too ):
4:42:18 PM - File change detected. Starting incremental compilation...
4:42:22 PM - Compilation complete. Watching for file changes.
Executing before-prepare hook from /home/karlis/Projects/my-instagram/test/hooks/before-prepare/nativescript-dev-typescript.js
Project successfully prepared (android)
Transferring project files...
Successfully transferred all files.
Applying changes...
Successfully synced application org.nativescript.test on device 3d828389.
Each time i run the command tns livesync android --watch --device=3d828389 i get the full app reinstall and message showing: The application with id "org.nativescript.test" is not installed on device with identifier 3d828389. However the app IS installed on the phone.
Discuss.
The problem was in my app/App_Resources/android/Manifest and gradle.
I changed them to original ones and it worked.
I'm running into a problem with accessing Yeoman after installing it on a fresh Homestead installation. Everything seems fine during the install after npm install -g yo and yo doctor runs just fine and finds no problem during the installation. However, after I've installed yeoman, yo: command not found is the error message I'm getting on my VM.
vagrant#homestead:~$ npm install -g yo
npm WARN deprecated npmconf#2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
/home/vagrant/.node/bin/yo -> /home/vagrant/.node/lib/node_modules/yo/lib/cli.js
/home/vagrant/.node/bin/yo-complete -> /home/vagrant/.node/lib/node_modules/yo/lib/completion/index.js
> spawn-sync#1.0.15 postinstall /home/vagrant/.node/lib/node_modules/yo/node_modules/spawn-sync
> node postinstall
> yo#1.8.4 postinstall /home/vagrant/.node/lib/node_modules/yo
> yodoctor
Yeoman Doctor
Running sanity checks on your system
✔ Global configuration file is valid
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version
✔ NODE_PATH matches the npm root
Everything looks all right!
/home/vagrant/.node/lib
└─┬ yo#1.8.4
├── async#1.5.2
├─┬ chalk#1.1.3
│ ├── ansi-styles#2.2.1
│ ├── escape-string-regexp#1.0.5
│ ├── has-ansi#2.0.0
│ ├── strip-ansi#3.0.1
│ └── supports-color#2.0.0
├── cli-list#0.1.8
[[REMOVED FOR READABILITY]]
└─┬ yosay#1.2.0
├── cli-boxes#1.0.0
├── pad-component#0.0.1
├─┬ taketalk#1.0.0
│ ├── get-stdin#4.0.1
│ └── minimist#1.2.0
└── wrap-ansi#2.0.0
vagrant#homestead:~$ yo
yo: command not found
My path in ~/.bashrc says the following: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/home/vagrant/.node/lib
Is there anything else that I'm missing here that might be causing this?
Add /home/vagrant/.node/bin to your path. :)