After I upgraded to macOS Ventura (13.0) nextjs and any npx command stuck - npm

After I upgraded to macOS 13. I found a problem with command in nextjs first. I tried to run my project with: npm run dev
This is result:
> dev
> next dev
It stucked on this log very very long time.
and I tried to create another project using:
npx create-next-app#latest
Result same to nextjs
About my computer:
Macbook pro 2018 13-inch 4 ports
I used Oh My Zsh on terminal
my node.js version is 16.18.0 (16.9.1 on this question created)
UPDATED 27/10/22
After I asked in this community. I tried many way to solve this issues.
This is way I tried:
Reinstall macOS Ventura and not working
Change node.js version to 16.18.0 => 19.0.0 and downgraded to 16.18.0 and not working
And now this problem is still. I still can't resolve this problem :(

I also had the same problem when I tried to run the nestjs application. Also failed to install packages, I got this error every time
It turned out that this could be a problem related to the IPv6 configuration. I disabled this setting and everything started working fine
Maybe it will also help you.
UPDATES
You can find this settings

Updated 28/10/2022 This problem I can resolved!!!!!
Today, I tried to clean install macOS Ventura (by backup internal storage => erase internal storage => install macOS Ventura by bootable drive and recovery data from backup hard disk)
All commands worked normally!
If you found a problem like this, you can resolve by clean install macOS!

Related

VSCode WSL - Installing VS Code Server for x64 - FAIL

Can anyone decode the following for me?
WSL was working perfectly on C++ a few weeks back.
Switched to try to run older Python under windows (not WSL) and it seems all twisted up now.
Can't get Win10 nor WSL to run. Keeps trying and failing to update. I re-ran the WSL and updated VSCode on the windows side. I AM behind a proxy but as far as I know, I've update all the files that google searches pointed me at. Pretty frustrated and would appreciate any help there is.
"
Request downloadRequest failed with message: getaddrinfo ENOTFOUND update.code.visualstudio.com. Will try to download on WSL side."
"
[2022-02-10 13:51:09.374] Setting up server environment: Looking for /home/ubuntu/.vscode-server/server-env-setup. Not found.
[2022-02-10 13:51:09.374] WSL version: 4.4.0-19041-Microsoft Ubuntu-20.04
[2022-02-10 13:51:09.374] Updating VS Code Server to version d6ee99e4c045a6716e5c653d7da8e9ae6f5a8b03
[2022-02-10 13:51:09.374] Removing previous installation...
[2022-02-10 13:51:09.674] Installing VS Code Server for x64 (d6ee99e4c045a6716e5c653d7da8e9ae6f5a8b03)
[2022-02-10 13:51:09.674] Downloading:
[2022-02-10 13:52:43.314] VS Code Server for WSL failed to start. No messages received for 90s
[2022-02-10 13:52:43.314] For help with startup problems, go to
[2022-02-10 13:52:43.314] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
[2022-02-10 13:52:43.328] WSL Daemon exited with code 0
"
I'm not 100% which step fixed it however I was able to proceed after.
Launching C++ project in wsl also tried to update and failed. The difference being that the install button did actually install the wsl server update w/o fail. So that error was gone.
I then launched another VSCode session with the Python project and the cmd terminal. I then had to use this help (https://github.com/pypa/pip/issues/9216#issuecomment-741836058) to adjust the proxy.
I could then proceed to reinstall ipykernel which is what had stopped working and was blocking me.
I'm pretty sure my environments are conflicting with each other. I'm afraid I don't understand VSCode environments well enough and very likely caused this problem for myself.

Running Big Commerce's Stencil CLI on Windows 10

I can not get Stencil to run for the life of me. I am using NVM to mange my version of node - I tried both 10.16 and 10.19.
I have reinstalled Stencil 2 or 3 times now and ever time I get the same error:
WTF? Has anyone got this to successfully run on a Windows 10 machine? We originally had node 13.9 installed but I was getting the same errors so I figured it was because it was outside their "approved" versions. I spoke to their customer support and they told me that it should work with newer version but that they can't give it proper approval until it's goes through some process.
So I can't get this to work on any version......
Any help would be very much appreciated!
Before installing nvm was a previous version of node installed? You'll need to uninstall nvm and node before installing nvm which can cause this. You can confirm which version of node is installed using node --version

An internal error occurred during: “Computing SDK Info…” When Starting Titanium Studio

Since upgrading TitaniumStudio, I am getting a java error when starting the TitaniumStudio application. Full error message is:
An internal error occurred during: "Computing SDK Info...".
java.lang.NullPointerException
When I try to create a new project, I get
Unable to locate the CLI executable. Please restart Studio or use Help > Check for Titanium Updates to install Titanium CLI.
I have no idea how to bypass this error. I tried installing and reinstalling the application, installing and reinstalling CLI via command line with no luck.
I am running osx with Yosemite.
Titanium 3.4.1
Node v0.10.33
npm 1.4.28
Any suggestion on where else to look in order to solve this error?
Thanks
I had the same problem. I switched from using node 0.12 to 0.10.13. Here are the two commands:
npm install -g n
n 0.10.13
then restart titanium studio
I know I'm answering this 3 months after the question was asked, but the solution provided by #turtle above didn't work for me.
I was getting the exact same error with a brand new install of Titanium (SDK 3.5) on OS X 10.10.2 and the latest version (0.12) of Node already installed. This happened on 3 separate Macs. I compared with a 4th Mac that already had Titanium installed and found out that reverting Node from 0.12 to 0.10.13 made the error go away, solved the problem on all 3 Macs!
Do a complete reinstall of titanium studio git and noe.It will solve your problem.

Geny motion failed to import OVA

Suddenly, i lost all Geny motion emulators (maybe after upgrading to Geny motion 2.2, not sure) and when ever i download a new virtual machine or emulator i get the "failed to import OVA" error and i can't use the virtual machines i downloaded at all in Geny motion, however they work in virtual box!
and i have cleared the cache and deleted old OVAs and re-downloaded other emulators again and again, but it's no use!
any clue what's going on?
is there a way to re-import emulators i already downloaded by Geny motion to Geny motion again instead of keeping downloading new emulators and getting the same error?
I solved the problem for myself. In my case, I had the same problem after defragmenting my computer. Deleting the ova and deploying files did not work (neither did reinstalling help). Solved it by clearing the cache in the app itself:
Settings>Misc>Cache Usage>Clear Cache
Try to see if that helps. If it doesn't then I can't help.
So I upgraded to the latest version of Genymotion 2.6.0. Tried to install the new Virtual Devices and I got the same error.
I tried to clear the cache as suggested above but it didn't help instead it removed the downloaded .ova file of the device and I had to download again.
I checked for update on VirtualBox and it shows that you're on the latest build. I checked the version and it showed 4.2.x.
Checked the latest version on the site and damn... It was version 5.0 available on the website.
Upgraded the VirtualBox to the latest 5.0 and here you go... Everything was back in place and my Genymotion Virtual Device was imported and is running fine.
So do check the versions of VirtualBox and see if it is the latest available on the website.
Deleting the Genymotion cached .ova file, deleting the corrupted deployed image, redownloading the image, and reinstalling it addressed the issue for me.
Note that the deployed images are under: ~/.Genymobile/Genymotion/deployed
the cached ova files are under: ~/.Genymobile/Genymotion/ova
this link : Unable to create Genymotion Virtual Device
Update :
Settings>Misc>Cache Usage>Clear Cache
Try to upgrade VirtualBox to the latest release, this solved the problem for me.
UPDATE
Some VirtualBox version are not compatibles with genymotion: review FAQ Genymotions in https://www.genymotion.com/help/desktop/faq/#compatible-virtualbox-versions
If you see the log file of Genimotions you'll find this:
VBoxManage.exe: error: 'Linux_64' is not a valid Guest OS type
The problem is the version of Virtual Box, I thought I had the last version (4.2) because virtual box said me that it was the lastest version, but it wasn't true: The last version actually is 5.0.20
I've installed the last version (5.0.20), and ova is ok
If you're using Windows:
The folder left after uninstallation is located at:
C:\Users\Your_User_Name\AppData\Local\Genymobile\Genymotion\
Before proceeding, in the OVA folder, save the ova files in there if you do not want to redownload the images all over again.
Clear the Genymotion cache, and then uninstall Genymotion (and Oracle VBOX if needed)
Remove the whole Genymotion folder in the above path
Reinstall genymotion and VirtualBox
Copy back the ova files into the ova folder.
Re-add the virtual device accordingly (the ova files name should be identifiable easily enough)
Genymotion will then verify the integrity of the stuffs and should now works fine.
I just Run Genymotion with Administrator right (run as Administrator)! It work perfect!
I had the same issue and also tried deleting the Genymotion cached .ova file and old images but to no avail.
To get my Genymotion working again in my environment I completely uninstalled VirtualBox and Genymotion using the TrashMe app to ensure no trace was left on my system. You can achieve the same result with the free app App Cleaner.
I then completely deleted the ~/.Genymobile directory as this seems to get left behind when deleting/uninstalling Genymotion. I think this is the only thing I did differently this time.
I then re-downloaded the latest versions of VirtualBox and Genymotion and installed them in that order. (Versions at time of writing: VB - 4.3.13 r93733 / GM - 2.2.2)
I then launched Genymotion, connected to my account, added a new device and I am now back up and running.
Hopefully that helps..
I encountered this error when my hard drive was almost full. It looked like it had enough space for the emulator, but Genymotion still failed with failed to import eva
Solved by freeing up a couple Gigs on disk.
Updating VirtualBox to the latest version, Worked for me
I deleted all the virtual devices and cleared Cache. After that I added the device again. Worked for me.
I had the same problem, I fixed it with uninstalling, reinstalling and running Gennymotion with Admin rights. Make sure you not upgrade Oracle VM and use the one you installed with Genymotion. Also at installing Genymotion make sure you reinstall VM too. It should work, I lost my devices too and this method only solve the OVA problem. If you run the virtual device and get an error, reboot computer, if you didn't do after installing Oracle VM. Hope it helped.
it turns for me I restored the system from the backup
Click geny settings->virtualbox tab, have to correct the folder to keep the VM
I had deleted /Users//.Genymobile/ directory and Genimotion started work fine
make sure you choose the correct android sdk
in Linux
just delete
home/user/.config/Genymobile/Genymotion.conf
and it's work
I downloaded ova that match with version i want (example android 5)
http://fatihcamuz.com/2015/04/download-links-of-genymotion-ova/
then add ova file to genymotion
https://www.youtube.com/watch?v=0MiYhVUv4KE

Facing 'Unable to locate the CLI executable' on Windows

I just installed Titanium and I'm not really familiar with this IDE. I added Android SDK to start my first application and everything looks cool until I tried to see my application in Android Emulator. I'm getting Unable to locate the CLI executable. Please restart Studio or use Help > Check for Titanium Updates to install Titanium CLI. and Check for Titanium Updates Says No Titanium updates available. and restarting the studio multiple times didn't work too. I cannot even preview my application in web browser. What am I doing wrong?
I'm using Titanium Studio, build: 3.1.0.201304151600 on Windows Server 2008 R2 Everything is up to date Node.js, Android SDKs, etc. I'm trying to create a web-based application frt Android 2.2+ and mobile web.
Farid,
There are several things you can try.
1.Type titanium in your command line and hit enter.If it gives 'not recognised as an internal or external command',it means Titanium package is not properly installed.
2.Try uninstalling just the Titanium node.js package using npm titanium uninstall command.
3.Once uninstalled,open Titanium studio.It will prompt you for installing Titanium CLI.Follow the steps and install Titanium CLI.
4.If these steps do not work,then uninstall node and install everything from the studio itself,rather than from the command line.
Sometimes installing Titanium CLI from command line fails.
EDIT:Before you try all this type node in your command prompt and see if node command is being recognised.If it is not you will have to set it to the PATH variable.
Thanks to 'Mukund Samant' with useful workarounds, I managed to fix this problem [although I faced another problem] by removing node.js and installing an older version (0.8.22) and then installing node.acs package manually by runnig this command: npm -g install acs. Now Titanium won't give me any errors or update messages on startup.
Note that I found out I have to run Titanium Studio as Administrator!