This is what I get when run "ns doctor android"
Native Script version: 8.4.0
Java Version: 1.8
Node Version: 16.8.1
NPM Version: 8.19
I have just created a black project and I was trying to run this to emulator/real device.
This is what I get when i run "ns run android"
It keeps watching and nothing is installed on emulator.It even detects the file changes but doesn't install anything.
Related
I am trying to create a new React Native Project using npx. The whole
npx process is getting failed due to Ruby version. Check the attached
image for more details.
The Ruby version was already updated using
rbenv. You can see the Ruby version in the image attached.
I have
also added the necessary code to the .bash_profile and .zshrc files.
Restarted the terminal and system multiple times but the error is the
same.
I don't understand what I'm doing wrong.
First use rbenv for the ruby setup. I'll recommend to restart the system once done with the ruby setup. take help from here.
Then follow these steps to create the react native project.
1. npx react-native init testproject --skip-install
2. cd testproject
3. yarn install
4. cd ios
5. bundle install (For Intel Chip)
arch -arm64 bundle install (For M1 Chip)
6. bundle exec pod install (For Intel Chip)
arch -arm64 bundle exec pod install (For M1 Chip)
I just wanted to try react-native.However, after run the script "npm run ios",I got this error in the Xcode's simulator.
react-native version: v0.66.0,
platform: Mac OS Big Sur 11.6.2,
How can I fix this?
install '#react-native/normalize-color' using command line npm i #react-native/normalize-color
Try installing '#react-native/normalize-color#2.0.0' if you are using 'react-native-maps'. This worked for me. It's probably because we may be using an older version of 'react-native' which included an older version of 'normalize-color'.
I recently got noticed in the Sidekick application on mac OS that a new version of the CLI was released and that I needed to update.
I quit Sidekick and run the "sudo tns i -g nativescript#latest --unsafe-perm" command in terminal with the following results:
+ nativescript#5.1.1
updated 67 packages in 14.325s
When I try to start Sidekick I get the following error:
Sidekick prompt
I head back to terminal and run "tns doctor" with the following results:
✔ Getting environment information
No issues were detected.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 10.1.0 satisfies minimum required version 9.
✔ Getting NativeScript components versions information...
⚠ Update available for component nativescript. Your current version is 5.1.0 and the latest available version is 5.1.1.
It seems like the update are not recognized by either tns doctor or Sidekick, what should I do to fix this?
Do you have nvm? This can happen when the settings in terminal are different from the global ones. For example it is possible to use one node version in the terminal and other from globally installed Sidekick.
You shouldn't use sudo - see this blog post on details on how to resolve the issue by removing the need for superuser while doing NPM installs. Similar thread here
On tns doctor command we got this message: Getting NativeScript components versions information...
This after tried to update with: sudo npm install nativescript -g --unsafe-perm
after that we got a lot of error messages.
Solved with this simply command:
tns proxy clear
then run: sudo npm install nativescript -g --unsafe-perm
Solved!
I have uiautomator version 2 is installed in my PC.
but when the appium severs runs below command
adb -s b133582d shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg io.ionic.starter -e disableAndroidWatchers false
the it return a warning as below:
This version of UI Automator is deprecated. New tests should be written using
UI Automator 2.0 which is available as part of the Android Testing Support Library.
See https://developer.android.com/training/testing/ui-testing/uiautomator-testing.html
for more details.
How can I fix this issue?
First, update android sdk tools, check for details here
Second, reinstall appium:
npm uninstall -g appium
npm install -g appium
Third, install appium-doctor and run env setup check:
npm install appium-doctor -g
appium-doctor --android
If you get any errors, fix them. Otherwise, start your tests again
New Mac user account. I install the Trigger.io (TriggerToolkit) app for the Mac. It fires up a tab with the apps. I can run the iOS simulator from it - so it is plausibly working installation. I have installed node.js from the node.js website, using the Mac package.
I have node.js as /usr/local/bin/npm (version 1.1.43).
It is found when I type "npm" at a command line.
The path "/usr/local/bin" is on my $PATH.
"/usr/local/bin" is set in my /etc/paths file, system wide.
So the npm executable should be findable by any user, at any time (before or after login, running a terminal, etc).
When I use the web page for the web run, it's OK, until it tries to run npm.
[DEBUG] running run_web((), {})
[DEBUG] Running: npm install
[DEBUG] failed to run npm: do you have Node.js installed and on your path? while running run_web((), {})
[ERROR] failed to run npm: do you have Node.js installed and on your path?
I guess that the problem must be something to do with an assumption about the path for npm. What's the assumption? What can I symlink to make this work?
Note that npm is found by "forge run web". This is something specific to the way that TriggerToolkit.app is working.
Update: this is fixed as of v1.4.6:
http://docs.trigger.io/en/v1.4/release-notes.html#v1-4-6
Previous answer:
Unfortunately I think the error message here isn't great and reflects a general problem with starting the node app.
We are aware of one issue with dependencies which started occurring after Node 0.8. Can you check what Node version you have:
node --version
If it's 0.8, then a temporary workaround to this problem is to use the command line tools and:
forge build
Then manually update development/web/package.json to refer to express 2.5.10, then
forge run web
Sorry for the trouble, we'll report back here when that's fixed