- CAN WE RUN THE EMULATOR ON MAC APPINVENTOR INSTALL
- CAN WE RUN THE EMULATOR ON MAC APPINVENTOR ANDROID
- CAN WE RUN THE EMULATOR ON MAC APPINVENTOR MAC
Thanks! I did confirm that I can connect to 127.0.0.1:8001 when using wireless, but not when plugged into ethernet. When you click Connect to Phone in the Blocks Editor, your app will appear in the emulator. Instead of connecting a phone to the USB port, just start the emulator program. The emulator lets you develop and test apps using a virtual phone instead of a real phone. Try some things, that you can use your laptop with WIFI is encouraging and indicative that something is probably blocking port 8001. App Inventor includes an emulator for the phone. You should be able to start it by typing aiStarter from a terminal. On GNU/Linux, this program is in /usr/local/bin. In case aiStarter somehow does need to be started manually on the Mac, find it using Spotlight, use the Finder to go to /Applications/AppInventor/ commands-for-App, and double click on aiStarter.
CAN WE RUN THE EMULATOR ON MAC APPINVENTOR MAC
On the Mac, aiStarter should start automatically, so Mac users should not have to worry about this. On Windows, there should be a button on your desktop that starts aiStarter. If it is not running, you'll get an error message saying that aiStarter does not appear to be running. Whenever you want to use the emulator or the USB cable, you need to make sure that aiStarter is running. It provides communication between App Inventor running in the browser, and other parts of App Inventor.
CAN WE RUN THE EMULATOR ON MAC APPINVENTOR INSTALL
The aiStarter program is installed on your computer when you install the App Inventor Setup software. What is aiStarter starter and how do I start it? This can be anything from a firewall, to another program using the same port. on a Mac) to launch Notepad/TextEdit with your freshly captured Iogcat.
CAN WE RUN THE EMULATOR ON MAC APPINVENTOR ANDROID
If you cannot connect to then you will have to look at what other programs on your PC may be interfering with connecting to the Companion. You can use the following steps to capture the Android log file to a text file. What you see isn’t important, it is the fact that you can see it. Note: There may only be the line “Directory /” or you may *also* see a listing of files which you should recognize as project assets (images, sounds etc.). If you get a directory listing (it will start with “Directory /”) then you are talking to the Companion. To test if this is the problem, while in this state, use your browser to go to Similarly if another program is using port 8001 the same thing can happen. If something is blocking that port, then it will not be able to receive any blocks. Instead you continue to see the “white screen” of the Companion claiming that it is waiting to get blocks.
Some people have reported getting the Emulator running and even the Companion, but then their blocks do not load.
0 kommentar(er)
