After updating my Mac OS to Catalina, Flutter is not working anymore in Android Studio. I deleted and re-installed, but still not working - bash

Please Please help. After updating the OS to Catalina, Android Studio would still open, but none of my Flutter apps will work and the emulators do not open (they say 'Loading')
I unistalled Flutter and re-installed it, but in the Terminal when I type in flutter doctor -v, it says "zsh: command not found: flutter"
Is this because I'm no longer using bin (or bash), and now using zsh?
Can someone tell me what I can do to solve this issue? Im not very good at entering Terminal commands, so what exactly would I type to fix this issue? (I'm a beginner)
When I was entering vim bash_profile in the Terminal, I entered the following as the Export Path:
export PATH="$PATH:/Users/raymondfontaine/Developer/flutter/bin"

I had the same problem and it occurred after switching from bash to zsh. A far as I know, you have three different options.
Switch your Terminal back from zsh to bash by typing chsh -s /bin/bash and restart your Terminal. Note: You can always switch back to zsh by typing chsh -s /bin/zsh and restarting your Terminal.
You can tell zsh to use the paths specified in your bash_profile file by typing source ~/.bash_profile into your Terminal. Note: You have to do this every time you open a new Terminal.
The two options above are probably not "Best Practice". The best solution would be to set environment variables for zsh as suggested by the flutter Tutorial: Update your Path.
In your case you have to type nano $HOME/.zshrc into your Terminal enter export PATH="$PATH:/Users/raymondfontaine/Developer/flutter/bin" there, save the file and restart the Terminal. After that flutter doctor -v should run as usual.
Also the emulators in Android Studio should load again. But if you still cannot start them via the Dropdown, try opening them via Tools > AVD Manager. This worked for me while they were not visible in the Dropdown Menu.

Related

oh-my-bash not launching at terminal startup

A little while ago I updated to the newest version of bash on my macbook (all went smoothly there,) and decided to try out the oh-my-bash framework. I had previously used oh-my-zsh, so I was familiar with the installation; however, I'm running into an annoying problem with oh-my-bash.
When I open the terminal the framework doesn't launch automatically. It only launches if I run exec bash in the command line. I've checked in system preferences and bash is set as default, and running bash --version confirms that I am running the correct version of bash when the terminal starts up.
It's more of an inconvenience than anything else, but I'm learning scripting and my burning curiosity wants to find the solution. I'm out of ideas short of a fresh install of the framework; what do you guys think?
My solution is this:
Run this code in terminal
mv $HOME/.bashrc $HOME/bash_profile
Restart your terminal
In linux, bash run command file is .bashrc, but in MacOS is .bash_profile.

Zprofile not found in Mac OS Terminal

I have a new mac that I have been setting up with homebrew, git, node, vs code etc. I noticed that some applications were somehow being installed on bash terminal instead of zsh terminal. Even though I was able to fix that, I now have an error message of
/Users/*****/.zprofile:1: = not found
I tried to create a z profile using
touch ~/.zprofile
How can I fix this error message?

macOS Terminal Process completed on any click

My macOS terminal is showing Process completed when I type any thing. I am not able to type or do anything on terminal (This effect my Android Studio and VsCode terminal also they just open close in an second) So all issue are causing with this terminal I try every thing restore profile etc nothing is working for me.
But one thing is strange here when I restart my Mac terminal works fine but after I work on android studio or vscode with Mac terminal (Not there default terminal because they are not working) After 1 hour same happen as I say before and as in screenshot.
On different questions solutions was to type /bin/bash -x on terminal but I can't even type single character on this.
I am finding solution for this from 1 week and not able to find any thing I need to restart me laptop every 1 hour to work.
I am using BigSur with M1 processor.
Also it was working fine before but I work on Flutter so I have set path and run commands like
Run: nano ~/.zshrc
Add: export PATH=[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin:$PATH
Run: source ~/.zshrc
And some bash commands to set path.

Running "open -a Terminal.app MyScript", opens new terminal window, but doesn't run MyScript in it

I'm on mac, and need to open a new terminal window and run a script/compiled code in it.
Before "open -a Terminal.app Myscript" would work, but now it suddenly no longer runs the script.. only opens the Terminal Window.
If i just run the script, it works. Other scripts that worked before no longer work using open -a either.
I'm running Mojave 10.14.3 Beta. And bash 5.0.0, linked through Homebrew.
If anyone else can reproduce this, please do. I'm not sure if its a bug, or just a issue with me.
console reveals following error:
/usr/bin/open subsystem: com.apple.launchservices
"Unable to load Info.plist exceptions (eGPUOverrides)"
This error is triggered everytime the command is run.
I've also searched and haven't found anyone else experiencing this problem, nor alternatives to open -a.
It works again now. Not sure if it was due to a restart, or because of another program.

my terminal can't run on mac os 10.9?

I used to install something from github,I stoped it and I can't open iterm-2 too
and I open my Bash ,it appeared
Command not found: /usr/local/bin/bash
[Could not create a new process and open a pseudo-tty.]
I can't input any words.
What should I change?
Google is full of others asking for help with this problem and half-baked solutions, including reboots (re-login should do it if env changed), reinstall (why?) etc.
Looks like a clone of I messed up my terminal environment on Mac OS X and was wondering how to fix it judging by inability to start bash from /usr/local/bin. System default should be in /bin or /usr/bin.
Your terminal (console or iterm2) may have an option to specify shell explicitly, used that.

Resources