You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: getting-started/installing-maestro/windows.md
+20-147
Original file line number
Diff line number
Diff line change
@@ -4,163 +4,36 @@ description: A step by step guide to installing Maestro on Windows
4
4
5
5
# Windows
6
6
7
-
Maestro works great on Windows computers, but there are a few unique setup steps to be aware of. This guide will walk you through the end-to-end steps for getting started with Maestro on a Windows machine.
* Run `source ~/.bashrc` to reload the bashrc file.
116
-
* To check that everything went well, do the following:
117
-
* Close and relaunch terminal
118
-
* Run `adb --version` and see that adb version is shown
119
-
* Since everything is installed fresh, your WSL 2 adb version should perfectly match with Windows ADB version that we noted down as part of the pre-requisites.
120
-
121
-
**Please follow the below steps to setup the ADB and make sure you are able to use Android emulators with your WSL2 correctly**
122
-
123
-
* Fire up your Android emulator on Windows.
124
-
* Once the Android emulator is up and running, open a PowerShell prompt.
125
-
* Run this command in PowerShell
126
-
127
-
```
128
-
adb -a -P 5037 nodaemon server
129
-
```
130
-
131
-
* This will start the adb server in the Windows host.
132
-
* Note down the IPV4 address of your Windows host PC/machine.
133
-
134
-
**TROUBLESHOOTING:**
135
-
136
-
* Sometimes you may get `smartsockets..` error when you run `adb -a -P 5037 nodaemon server` command in PowerShell. In that case, you can do the following steps:
137
-
* Open task manager and kill all `adb` related processes.
138
-
* If Android Studio is open, close it and **keep only** emulator running.
139
-
* If you see a message saying `emulator offline`, **ignore it**.
140
-
* Sometimes, the firewall stops your connection with the host machine. For that, add a firewall rule to allow the connection or check with your organization system admin if using a company machine.
141
-
* **Note: Don't close the PowerShell terminal!**
142
-
* **Now open your WSL2 terminal and run these commands.**
0 commit comments