2017년 6월 21일 수요일

Emulator stuck in white screen when running without admin rights


I got a problem with App Inventor in a class room.
The PCs are running on Windows 10 x64 and the users have no admin rights.
App Inventor is running without errors, but when launching the emulator it gets stuck in a white screen after launching a project app. You can wait several minutes but nothing happens.
When logged in as a user with administrator privileges everything works fine. The white screen can be seen for a few seconds, but then the app starts and works as intended.
It was tested with the App Inventor versions 2.7 and 3.9. Admin works fine, standard user only gets white screen in emulator.
There are some GPOs used to prevent pupils from manipulating the PCs. Is it possible that it has to do with that?
If you need additional information please let me know.
Thanks for your help!

--
Yes,  GPOs used to prevent pupils from manipulating the PCs. are probably the problem.  The adb (the emulator) needs to be installed with Admin privlidges and the PC requires access to ports 8001  and 8004 .   If one of these is blocked (I think it is 8004 if I remember) the emulator cannot communicate .

Have you read the advice here  
Particularly the first one.     Did the advice help?    Please let us know whether this information allows the students to run the emulator.  If not please tell us more and someone will try to help.

--
Based on the code flow, the App Inventor title bar with the text "Running as emulator or USB, waiting for blocks" will show until the website establishes a connection to the emulator, at which point the clear form command is issued blanking the screen in preparation for receiving the open project. So if the screen has gone blank, that should be indicative of a successful connection. One thought I have is that the connection is being established, but when the companion attempts to receive project assets there is a problem writing to disk.

Does this happen with a simple project without assets (e.g., just a button on the screen)? Or does this happen regardless of the complexity of the app?

--
thanks for providing the advices. I'll check that and tell you if it worked.
In the meantime I can provide some more information: When starting the App Inventor the first time the windows firewall asks for permission for Java. This window appears twice and I set this to allow for all network types.
The GPO doesn't have any firewall configuration, the main purpose is preventing the pupils from accessing several system settings and programs like network settings, control panel, command line, Windows Store and so on.
As the admin can run App Inventor and the standard user can't I thought about putting the pupil's users into the power users group. I tested this and noticed that now on three out of 17 PCs the App can be loaded.
The GPO is still active for the pupils after the change, so it seems on those three machines the GPO doesn't affect the App Inventor.

Edit:
I'm just gone through Help with problems connecting the emulator and have one thing differing: The App Inventor is installed on c:\AI2U as the teacher who wants to use it got a manual from another teacher who uses the App Inventor successfully where this installation location was recommended. During the installation the administrator was logged in. 

- show quoted text -

the mainly tested app was one with butterflies and flies appearing on the screen where you have to catch the flies. This app works on the three PCs I mentioned and also on the teacher's PC at home and also on my own PC where I also tested it.
The teacher also has a simple "press the button" app which provides a "button is pressed" text on the screen. This app was tested on one PC which also can't load the "butterflies" app, and this simple button app also didn't work. So the complexity doesn't seem to be the reason for the problem.

--
The installer instructions do say:
1. Download the new Windows installer package.
2. Install the new software you just downloaded. Do not change the installation directory from the default that the installer picks.

One can not change the install directory of aiStarter (that also contains the adb.exe ...the emulator).  
Also, be aware, you must have Admin privileges to do the install.  This means that if it is installed manually,  right-click on the aiStarter exe file rather than the normal left click.  Doing a right click brings up a menu .. select install as admin.  I am aware of a situation where a user indicated he was the Admin, however, he was not able to get a proper install without right clicking.


You are not able to install in a different directory then the "Program Files" directory.  If the install is in a different directory, that could cause problems.

There is a third part 'portable' version of App Inventor called ai2u   https://sourceforge.net/projects/ai2u/files/ai2u%202.4/      That version would have been installed in AI2U perhaps.   You said "The App Inventor is installed on c:\AI2U as the teacher who wants to use it got a manual from another teacher who uses the App Inventor successfully where this installation location was recommended. During the installation the administrator was logged in. "     If you installed the ai2 software on c:\AI2U   THAT COULD BE THE PROBLEM.   The software must be in the Program files directory.

aiStarter on my Win10 64 desktop is here 

The adb.exe (the emulator) is in the folder commands-for-appinventor  and is placed there by the aiStarter installation.  Remember to right click to install.

Let us know if this additional information helps.   If the adb is anywhere else, then you probably found the issue Michael.

--
thanks for this additional info.
After checking the information from your first answer I found out why the school is trying to use the AI2U portable version: There are big internet issues at the school and it's nearly impossible to get the app inventor running when there is an internet connection required. So the teacher tried to use that AI2U version to be able to run it locally.
The last time I was at this school I compared 2 PCs of which one could run the version at c:\ai2u and the other one couldn't.
I noticed a difference in the window running the dev_appserver.cmd. It seemed that the PC where the app doesn't work gets stuck at one point, but there is no error. It just looks like it is waiting for ages for something that doesn't happen.
I don't have a log of it but if it helps I can copy the contents of this window. Perhaps you can see at which point it gets stuck.

--
To get specific help with AI2U you are going to have to ask here 

AI2U - Google Groups



MIT does not support this third party stand alone version of App Inventor.   How one runs/installs the emulator works a bit different with this tool than the MIT App Inventor.
Ask your question there and you should get help getting the PCs up and running.   Be aware, a plain vanilla AI2 project might not load correctly on AI2u . Edit: Krupong attempts to keep AI2U up to date with AI2 code but sometimes lags a bit.  

I'd be glad to help but I have no experience with AI2.  Now we know the problem is an AI2U issue.

--
@SteveJG: the author of AI2U is krupong, a teacher from Thailand
Hosseins App Inventor Offline unfortunately is outdated (latest version as of June 22, 2016), see also the overview here Overview: Different App Inventor Distributions and Versions

--

댓글 1개:

  1. There's SHOCKING news in the sports betting world.

    It has been said that any bettor needs to see this,

    Watch this or quit betting on sports...

    Sports Cash System - Advanced Sports Betting Software

    답글삭제