But now and the I need to do some work from my windows machine.Im ok with that because the mac and windows are two different machines.On your windows machine open up an Android Adb Command Prompt and try to connect with the command.After some googling I wasnt surprised to find a solution on the Xamarin website itself.
And when the firewall of your mac is enabled youll get a pop-up to ask if its ok to change its settings. In some cases, it can stay that way for as much as several minutes while the emulator program starts up. To use the emulator, choose Emulator from the Connect dropdown menu. The emulator should start on your computer, and connect to App Inventor so you can test your app and do live development. Emulator Connected To Bgb Software Running OnThere are many things that can go wrong, such as unexpected configurations, restrictions on the network you are using, or other software running on your computer that interferes with App Inventor. For school computers, weve seen several issues that interfere with App Inventor, including firewalls on school networks, restrictions on software the the machines can run, and ports being blocked. Symptoms you might encounter include the emulator starting up and then freezing, or not starting at all, or App Inventor displaying unable to connect messages. This gives a step-by-step procedure for attempting to isolate and ifix issues. This procedure is for Windows. Emulator Connected To Bgb Mac Version OfThe issues are the same for MacOS and we will be publishing a Mac version of this document soon.). Please go through this procedure before filing an issue on the App Inventor forum. If you eventually file an issue, first search on the forum to see if others have experienced similar problems. When you post to the forum, describe the results of the steps you tried, so that people who want to help you will have more information about where to begin. Please submit an issue and include the project source (aia) file. On the other hand, if the emulator wont start for any of your projects, then continue with the debugging steps here. An intermediate case is when you have a large project that has many images or sounds, or many screens. In that case, try reduced versions of the project that have fewer screens or assets to see how large things before the problem occurs. The current App Inventor 2 software can handle only a single device and will get confused if more than one device is connected. Similarly, App Inventor will get confused if there is more than one emulator running. Kill any running emulators before trying to start another one. The setup software wont find the emulator support if its in a different location. If you are running this or something similar, youll need to turn it off, or configure it to not block the App Inventor connections. To do this, use the emulator on the computer screen: press the (image of the) menu key, and then the button to kill the app. If the Companion tarts up again, asking about a QR code, press the menu key and kill it again. Now select emulator again from the App Inventor connect drop-down menu. Restarting the Companion might not solve your problem (there might be another underlying cause) but it is a good first step. When the emulator starts, it first appears as a black screen with the word Android in the middle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |