platform-tools | A toolchain to build and compile native dependencies | Build Tool library

you flutter channel is unknown .

the version is unknown and seems to be on web developer mode so

if you are using it for android devices , it is better to switch to

Could you try to

• Quit you IDE
• Move or remove the ~/.android/debug.keystore and ~/.android/debug.keystore.lock file
• Use the flutter clean method
• Recompile your app

You downloaded flutter using the zip link instead of git clone. At least that I suppose with that message

Try go to the folder:

I am answering my own question.

Where I made wrong is, decompressing to wrong directory and using wrong --sdk_root. As said in here, I have to create a dir called cmdline-tools and decompress in it. Now we will have another cmdline-tools dir. We have to rename it to the respective commandline tool version we are using. In my case it is 3.0.

Finally my script should be look like below.

Run adb root && adb remount first.

I simply did a System Restore to a time before I started port forwarding to TCP 5554, and started adding new firewall rules. ADB daemon started at TCP port 5037 and that was it.

Answer my own question for future seekers.

Android Studio installed the adb under /home/$USER/Android/Sdk/platform-tools on Deepin, while Expo tutorial gives the recommendation of export PATH=/home/$USER/Library/Android/Sdk/platform-tools.

1. There is no Library folder in the path
2. the Sdk has been capitalized

Good luck on your journey :)

You should run it like ./adb shell cmd appops set com.whatsapp RUN_IN_BACKGROUND ignore i.e. without package:

You have a system-installed python3 (probably 3.8.2 if you are on Big Sur) in /usr/bin/python3 and a Homebrew-installed one in /usr/local/bin/python3 which is a symlink to the real location where brew installed it. This is all quite normal, though if the system-installed Python 3 was sufficient for your needs, installing another copy with Homebrew was redundant as such. But this is all quite normal; your system needs a particular version to exist, and you should not touch that, but you are free to install a non-system version in parallel and use that for your personal needs if you want to.

You can use the explicit paths to run any particular version (try /usr/bin/python3 --version and /usr/local/bin/python3 --version) but usually you don't want or need to. Out of the box, your PATH is ordered so that /usr/local/bin takes precedence over /usr/bin, so that locally installed versions shadow the system default versions in regular use.

As an aside, you have the Visual Studio Code path added twice, and you don't need to export PATH multiple times (or actually at all, as the system startup files will already have marked this variable for export).