I have installed Appium Studio and Appium Desktop, I am using a real device and have switched on developer mode on my mobile. I am even able to run and install a app from appium desktop on my mobile .
Hi Minal!
You did not share what the configuration for the device and the app looks like (you can always click âeditâ and you will see the configuration).
What I can already see is, as it seems, that the device name does not look like a real device name, it seems you copied my values.
But the device name used needs to be the name of your specific device, that you have connected, otherwise we would not know which Device you want to automate. It cannot be any random value.
If you have Android Studio installed, you can find the Device name by executing the command âadb devicesâ in the command line, e.g. like this:
And I canât see if you have configured the application you want to use in the Application section from your screenshots.
As an additional note:
You donât need to install Appium-Desktop, as it is âheavy weightâ.
The easiest way to install an Appium-Server is, if node.js is installed on your system, to simply use the command:
npm install -g appium
If Node.js is not installed, then you can simply install it from here:
Another note:
Android Studio is, in this case, only needed or useful, if you want to run the emulator that it comes with.
It is not needed for our product or for Appium.
I hope that helps a bit.
A detailed article how to connect to real and emulated local devices will follow soon.
We will also show that it is even easier when you are using a cloud farm provider, like Sauce Labs, as you donât need to install anything.
Hi Rohan!
Please send what you configured within the Mobile Device Manager. But it looks like that the adb.exe, which is the âAndroid Debug Bridgeâ is not available on the system where you started Appium and connected the device or emulator (donât know which one it is).
If you send the configuration you did within the Mobile Device Manager, I might be able to point you in a direction.
Thanks,
Bye,
Chris
Hi Minal!
The device/emulator you have connected is called âRaghav Aggarwalâ? How did you get to this name, because the Device name and the display name can be different.
One pre-requisit that Appium needs for steering Android devices is ADB, the Android Debug Bridge, as it uses this to access the device.
Please make sure that you have it on your system and it is either specified by path or configured in the environment variables. There is a lot of links online about setting up Appium - a colleague did get it to work with a tutorial he posted here:
I hope that helps.
As a functioning Appium setup is a pre-requisit for our product, I did not have the space to go into that in the above post. But I am working on a more detailed Post how to setup Appium that will be published soon.
@Christian_Mayer Is it mandatory to start the Appium server before starting\launching the application from the Mobile Device manager? right now application wonât launch if we didnât start the appium server.
Hi Anand!
I donât know if you mean starting the Mobile Device Manager from Studio, or connecting to a Device from Mobile Device Manager.
Starting the Mobile Device Manager from Studio does work without Appium started. But if you are connecting to a device, of course Appium must be started first, as there otherwise is no device to connect toâŚ
Bye,
Chris
Hi Rohan!
As it seems you have the same issue as in a post before - ADB is not present on your system, or not set in the environment variables.
You should make sure that the adb.exe is setup in the environment variables, like in my case here:
Download and Install ADB from here then add the path to My PC> Properties> Advanced> Environment variable> Under User variable for user click Path Select EDIT and then click New and paste the path of the directory to ADBâŚrun ADB Devices from command prompt.
Hi Sandeep,
Our new product, Mobile Device Automation, is only available starting 20.4, as before there was no Studio Pro Profile/License, which is a pre-requisit.
Bye,
Chris