Thank you so much Marwan

You're most welcome Srinivas

Most welcome

Coming soon Nitin... keep learning

@@RaghavPal Thank you sir

I will try

Navneet The error message "'appium' is not recognized as an internal or external command, operable program or batch file" indicates that the system cannot find the "appium" command in the current environment. This typically happens when Appium is either not installed or not added to the system's PATH variable. Let's troubleshoot this issue step by step: 1. Check Appium Installation: - First, ensure that you have correctly installed Appium. If not, download and install it from the official website. - Make sure you've followed the installation instructions for your operating system. 2. Add Appium to PATH: - The PATH environment variable contains a list of directories where the system looks for executable files. - To add Appium to the PATH: - Open the System Properties (you can search for it in the Start menu). - Go to the Advanced tab and click on the Environment Variables button. - In the System Variables section, find the Path variable and click Edit. - Add the path to the directory where Appium is installed (e.g., `C:\Program Files odejs`) to the list of paths. Separate multiple paths with semicolons. - Click OK to save the changes. - Restart your command prompt or terminal for the changes to take effect. 3. Verify Installation: - Open a new command prompt or terminal window. - Type `appium --version` and press Enter. - If you see the version number (e.g., "1.15.1"), then Appium is correctly installed and added to the PATH. 4. Check Node.js Installation: - Appium relies on Node.js. Ensure that Node.js is installed and also added to the PATH. - You can download Node.js from the official website and follow the installation instructions. 5. Restart Command Prompt or Terminal: - Sometimes, changes to the PATH variable require restarting the command prompt or terminal. - Close any existing command prompt or terminal windows and open a new one. 6. Check for Typos: - Double-check that you're typing the command correctly. It should be `appium`, not `Appium` or any other variation. 7. Reinstall Appium (if necessary): - If none of the above steps work, consider uninstalling and reinstalling Appium. - Make sure to follow the installation instructions carefully. Remember to verify each step

Sudheer did you add the variables in the env file and saved it. Check the names and paths again. Also after this try to check on a new terminal window. If you still face issues, send me your steps

also i have tried the bellow step Microsoft Windows [Version 10.0.22631.3672] (c) Microsoft Corporation. All rights reserved. E:\android\cmdline-tools\latest\bin>sdkmanager --list Error: LinkageError occurred while loading main class com.android.sdklib.tool.sdkmanager.SdkManagerCli java.lang.UnsupportedClassVersionError: com/android/sdklib/tool/sdkmanager/SdkManagerCli has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 60.0 E:\android\cmdline-tools\latest\bin>

Aman It seems you're encountering a couple of issues related to the Android SDK and `sdkmanager`. Let's address them step by step: 1. 'sdkmanager' is not recognized as an internal or external command: - This error occurs when the system cannot find the `sdkmanager` executable in your system's PATH. - To fix this, you need to add the correct path to the Android SDK tools directory to your system's environment variables. - Follow these steps: - Right-click on "My Computer" (or "This PC") and select "Properties." - Click on "Advanced system settings." - In the "Advanced" tab, click on the "Environment Variables" button. - Under "System variables," find the "Path" variable and click "Edit." - Add the path to your Android SDK tools directory (usually something like `C:\Users\\AppData\Local\Android\sdk\tools\bin`). - Make sure to separate multiple paths with semicolons. - Click "OK" to save the changes. - Open a new Command Prompt window and try running `sdkmanager --list` again. 2. Java Runtime Version Error: - The second error indicates that the `SdkManagerCli` class has been compiled with a newer version of Java than the one installed on your system. - You'll need to ensure that you have the correct Java version installed. - Follow these steps: - Make sure you have the latest JDK (Java Development Kit) installed on your system. - Set the `JAVA_HOME` environment variable to point to the JDK installation directory. - Update your system's PATH variable to include the `bin` directory of the JDK. - Restart your Command Prompt and try running `sdkmanager --list` again. Remember to replace `` with your actual Windows username --

Android Studio is a complete platform for android development. So if you only want to setup Android env for testing, can go with SDK tools only. In the next video i will also cover how to create Emulators without using Android Studio and with both

I will plan Sreeni

Yes Grace.. in the process

I believe it is due to ANDROID_HOME env variables is either not set or the path is not proper. Please check with the video again

Sergei Let's break down the issue step by step: Step 1: Identify the difference between the two installations The main difference between the two installations is the package name: * `appium-doctor` (old package) * `@appium/doctor` (new package) The `@` symbol in the new package name indicates that it's a scoped package, which is a way to namespace packages in npm. Step 2: Investigate the behavior of both installations The user reports that both installations allow them to use the `appium-doctor` command. However, the old installation (`appium-doctor`) fails to check the installation and PATHs for the `--android` option. Step 3: Determine the correct installation method Based on the user's experience, it seems that the correct installation method is `npm i -g @appium/doctor`. This is likely the recommended installation method by the Appium team, as it's the one that works correctly with the `--android` option. Step 4: Update the documentation As requested by the user, the documentation should be updated to reflect the correct installation method. The old article should be updated to remove the reference to `npm install -g appium-doctor` and instead recommend `npm i -g @appium/doctor`. Conclusion The correct installation method for `appium-doctor` is `npm i -g @appium/doctor`. The old package `appium-doctor` is likely deprecated and should not be used -