lukearoberts

When checking that web link, it shows device is ok, except for the standard students and a test student account that has got command prompt script proccessing enabled, which gets a message saying could not connect to the server, connection refused. It does however show device ok for another test student account that does have access to the command prompt enabled.

Thanks for the quick reply, but I have added the proxy to the launcher application xml file and is working for all other users types but not students, and have tried with a test student account that does have access to command prompt and it works then.

Thanks, the OS is loading up now after remaking the package. However now I have another issue, but it might not be one you can fix. With a student user on the standard RM CC4 user policy the App Inventor website doesn't seem to recognise that the emulator is running, when you click to connect to the emulator it says please run the aistarter and try again, even though the emulator is already running. I have done some testing and have found that it is the policy that disables use of command prompt for standard student users. In you benefits section on the package download page you state that no command prompts are required, could I have done something wrong with the package or could it simply be that even though no command propt windows open the user still needs access to it?

I have downloaded and followed your instructions for your CC4 package for the App Inventor emulator. I have imported the package to the RMMC and assigned it out to a couple of machines but when I click on the Start Android Emulator button the emulator loads up but just gets stuck with the word Android and flashing line and goes no further, it doesn't load up the Android OS. It does this for for all user accounts. Any help would be appreciated