Emulator Won't Start

[McG]

Cannot get the emulator to work after upgrading when Companion was out of date.

"The application CompanionUpgradeHelper etc. has stopped unexpectedly.  Please try again" keeps coming up.

Happening on mac and PC (with Windows 7) installed.  Big problem with all of my classes due to use this today.

[Chris Ward]

Hello McG

It is a big problem and I am experiencing the same myself. When that message is displayed in the Emulator, there is an orange button "Force Close" - click that button and the process will try again.There is a good chance that the process will then complete. Make sure that AI is the only web page running (and don't run any other browser at the same time either), to avoid the possibility of an interruption.

Please let us know how you get on. 

[McG]

No joy with any of that Chris.  Emulator still producing the above issue.  Happening with a few of my students as well which is a real problem.

[Chris Ward]

Owch, sorry to hear that McG.

We have been testing a setup tools update, which should fix this problem. Hopefully the fix can be released soon.

Is it possible for your students to test their work on real devices? Most Android devices have a "Developer Mode" which will allow you to test un-certified apps on them (by installing an APK file). The Developer Mode is hidden from the casual user, different manufacturers have different methods of enabling the mode which often entails tapping the same button/menu item several times. For example:

http://www.samsung.com/uk/support/mobile-devices/how-do-i-turn-on-the-developer-options-menu-on-my-samsung-galaxy-device

[William Petry]

Here too on Windows 10. Multiple iterations of intuitive problem-solving explorations ended dismal failure. 

[nrcs_2018]

Hi - I can't it to work either. I had the emulator working on the weekend, but now it goes into an infinte loop trying to run the update. The install is successful but it keeps trying and trying then gives a fatal error. Please help! I was planning to use this software to teach a high school class starting tomorrow but I am doubtful that anyone will be able to use the emulator. In a classroom setting the emulator is really necessary as all the students wouldn't own an android device.

[Abraham Getzler]

I'm not sure posting to an old thread assigned to MIT

will get into their mailbox.

Just to be sure, I recommend starting new threads,

for a new assignment.

Seeing you're under time pressure, here are

some work arounds ...

the Companion and Emulator FAQ section at

https://groups.google.com/forum/#!msg/mitappinventortest/wqJin0qO8M0/8xUafdROAgAJ

Spin offs of AI2 (one way trips, no backward compatibility) ...

thunkable.com

appybuilder.com

makeroid

(see Forums section of FAQ for links)

ABG

[Chris Ward]

Hi

A fix for this issue is to be released soon.

Another workaround is to try a 3rd Party Emulator which runs on Windows just like the AI one does. BlueStacks is popular and free:

BlueStacks Emulator Install

1) Download BlueStacks https://www.bluestacks.com/download.html#gref

2) Install BlueStacks on Windows. Note: Like App Inventor, Bluestacks requires the User's Google Account for login.

Testing an App Inventor App on BlueStacks

1) In App Inventor, select Build, App (save .apk to my computer)

2) Run BlueStacks, click "My Apps"

3) Drag and Drop your App Inventor App .apk onto BlueStacks - it will self install

[Abraham Getzler]

@chris,

Have you tried the Companion connect operation against BlueStacks?

On GenyMotion, it has to be done via the Connect->USB option

after aistarter.exe is running and the MIT Companion.apk is running

in the emulator of choice.

ABG

[Chris Ward]

Hi ABG

Just tested - it's not the USB option, it's the Companion Option, but unfortunately the Companion does not run correctly in BlueStacks, it gets as far as prompting for the 6-char code but does not budge from that point.

GenyMotion is a completely different animal but might be a good investment for some schools given it's capabilities.

[Christine Shock]

I am experiencing the same problems with the emulator. Even turned off the firewall, nothing is helping. Everything loads fine until the companion and I either get the "Force Close or Wait"  or Not Parsing error. The App companionupgradehelper process .edu.mit.appinventor.aicompanion has stopped unexpectedly.

I have several students who were thinking about going to MIT now thinking about not going to MIT because of the problems with this software.

Platform = Windows

AppInventor tools located here: "C:\Program Files"

Bottle server starting up (using WSGIRefServer())...

Listening on http://127.0.0.1:8004/

Hit Ctrl-C to quit.

127.0.0.1 - - [19/Jan/2018 15:55:49] "GET /ping/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:54] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:54] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:54] "GET /start/ HTTP/1.1" 200 0

127.0.0.1 - - [19/Jan/2018 15:55:54] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:55] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:55] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:55] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:56] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:57] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:58] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:55:59] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:00] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:01] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:02] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:03] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:04] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:05] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:06] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:07] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:08] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:09] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:10] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:11] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:12] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:13] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:14] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:15] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:16] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:17] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:18] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:19] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:20] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:21] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:22] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:23] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:24] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:25] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 15:56:26] "GET /echeck/ HTTP/1.1" 200 67

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 15:57:18] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 15:57:48] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 15:58:01] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 15:58:20] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 15:58:34] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 15:58:40] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Killed adb

Killed emulator

127.0.0.1 - - [19/Jan/2018 15:59:20] "GET /reset/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:06] "GET /ping/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:11] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:11] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:11] "GET /start/ HTTP/1.1" 200 0

127.0.0.1 - - [19/Jan/2018 16:01:12] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:12] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:12] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:12] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:13] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:14] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:15] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:16] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:17] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:18] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:19] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:20] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:21] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:22] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:23] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:24] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:25] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:26] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:27] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:28] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:29] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:30] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:01:31] "GET /echeck/ HTTP/1.1" 200 67

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:02:19] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:02:47] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:03:01] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:03:18] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:03:30] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Killed adb

Killed emulator

127.0.0.1 - - [19/Jan/2018 16:04:45] "GET /reset/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:28] "GET /ping/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:33] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:33] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:33] "GET /start/ HTTP/1.1" 200 0

127.0.0.1 - - [19/Jan/2018 16:05:33] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:34] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:34] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:34] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:35] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:36] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:37] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:38] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:39] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:40] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:41] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:42] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:43] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:44] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:45] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:46] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:47] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:48] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:49] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:50] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:51] "GET /echeck/ HTTP/1.1" 200 40

127.0.0.1 - - [19/Jan/2018 16:05:52] "GET /echeck/ HTTP/1.1" 200 67

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:06:41] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:01] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:11] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:20] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:26] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:32] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:37] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:42] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

Device = emulator-5554

127.0.0.1 - - [19/Jan/2018 16:07:48] "GET /replstart/emulator-5554 HTTP/1.1" 200

 0

[Chris Ward]

Hello Christine

It is a known App Inventor issue. A fix has been defined and will be released in the near future. You could try the work-around I have given in my earlier response.

 I have several students who were thinking about going to MIT now thinking about not going to MIT because of the problems with this software.

I'm very sorry to hear that. However, a big part of developing software is about solving problems, wherever they might spring from. If we gave up everytime we hit a problem, where would mankind be? Still living in caves! :)

[Abraham Getzler]

@Chris, if you have a BlueStacks implementation, you're in a position

to try copying BlueStack's adb.exe over the AI2 adb.exe file.

It was a necessary step for GenyMotion connection,

as described in the MIT Genymotion install doc in my FAQ,

and as experienced by me.

ABG

[McG]

Chris, you don't know when "the near future" is do you?  We have option choices coming up for pupils and the problems they are having here could influence whether they pick computing science next year.

I want to at least be able to tell them "don't worry, this will be fixed by ....".

Thanks for your help here.  Appreciate it.

[Chris Ward]

Hello McG

All I can say is that we are currently testing an update, perhaps you could try out the test version:

https://groups.google.com/forum/#!category-topic/mitappinventortest/specific-programming-issue/IbS83H9ktLs

You can also try BlueStacks, see my earlier posting.

[Chris Ward]

Hi ABG

Tried that, but it didn't work.

[SteveJG]

@ Chris   ... Blue Stacks is more of a problem then a help in many instances.  Once upon a time, this was true:

Do you have BlueStacks on your PC (BlueStacks is a special emulator that allows Android apps to run on a PC)?  The Google emulator on AI2 cannot run unless BlueStacks is disabled and all of the BlueStacks processes are shut down.  On a Windows PC, you use the Task Manager to 'kill' running processes.

I think it is still true.  I tried BS several years ago and this was the case and it did interfere.  Others had a similar problem, when BlueStack processes were active, the Google basic emulator refused to work properly.  Perhaps BS no longer causes issues, only you can tell.

--- Steve

[Abraham Getzler]

Note to schools needing immediate alternative servers -

See the App Inventor Versions section of FAQ

https://groups.google.com/forum/#!msg/mitappinventortest/wqJin0qO8M0/8xUafdROAgAJ

for AI2 spinoffs.

ABG

[Chris Ward]

Hi Steve

BlueStacks is a completely different kettle of fish now. OS Compliant (when closed no processes are left running), User friendly (drag and drop apk), generally more advanced/stable than the AI Emulator. Not perfect, especially since it has moved a bit away from being an emulator and more towards a game player, but pretty good.

[SteveJG]

@ Chris ....good to know.  Thanks for the update on BS.

[McG]

@Chris, still no joy with the emulator although I saw another thread that suggested an update to fix the issue had been released.  Not for me in school on PC or at home on mac.

I've not downloaded Bluestacks (which will give me headaches with getting it installed on school machines).  However I'm guessing that BS would be best for using a final version of a program and not for the constant program a bit, test a bit that the working emulator provides?

[SteveJG]

@ McG      If your mac is has High Sierra, the emulator fix MIT provided the other day will not work.  That is a known issue, the emulator will not work with High Sierra.    

Regarding a PC at school, make sure the IT department has not blocked ports 8004 or 8001.  Port 8004 is required to talk to aiStarter 

When you attempt to upgrade on the PC, did you use  Connect>Hard Reset before you attempt to run the emulator?

Try again and let us know.  The latest fix seems to have helped virtually all other emulator users attempting to update so we would like to help figure out why you are still in the dark.

Regards,

steve

[Evan Patton]

@McG: Are you continuing to experience issues with the emulator upgrade process? The bugfix release on Jan 24th should have addressed this issue.

Regards,

Evan