2014년 12월 15일 월요일

Script errors when trying to open project.

Help!  Cannot open certain projects from a Home desktop (wireless) &(using Windows 8.1) Firefox without getting Script Errors.  I'm taking Inventing Mobile Apps at Wellesley (CS117) with Lyn Turbak as the professor.  I need to finish my project and write consecutive material with which I need to take screen shots of the blocks by Wednesday, December 17, 2014.  Any help would be greatly appreciated. 

 Any projects I made a copy from one particular project, I Cannot open at all.  Here is the script error on the first project:

  A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: http://ai2.appinventor.mit.edu/ode/5E8DF611E5F83524BF08E124C961F7CF.cache.html:2952

 Here is some background on some fixes??? Are they related to my problem?  :

UPDATE: December 13, 2014 13:40 US Eastern Time (UTC-5)
We are aware that problems are continuing. Sometimes particular assets are unavailable (they show up as zero length) and then re-appear later. We are actively investigating the problem and apologize for the inconvenience.
UPDATE: December 11, 2014 23:15 US Eastern Time (UTC-5)
We have deployed the fix so that projecs with a zero length asset should now behave properly.
UPDATE: December 11, 2014 14:00 US Eastern Time (UTC-5)
We have identified a bug in MIT App Inventor where if you upload a zero length asset (aka an empty file), your project will become corrupt. In particular you will not be able to build it, export it or checkpoint it. However you can continue to work with it.
We have a fix, which we anticipate deploying this evening. Once deployed, all projects affected by this bug will work normally again.
December 11, 2014 11:30AM US Eastern Time (UTC-5)
If you are having problems loading or exporting your projects (you see the “red bar” with an error message). This *may* be caused by a problem that appears to be in the Google Cloud Storage (which we use for storing projects). Some projects lost assets (images, sounds, etc.). When this happens the project becomes corrupt and won’t load.
Although we cannot recover any assets that were lost, we are working on a modification to App Inventor that will permit your project to load, even if assets were lost. You will have to re-upload the assets and then your project should be fine.
We apologize for this inconvenience. We will update the “splash screen” and this document when we have more information.
-The MIT App Inventor development team



Can not open the Project.   Does that mean that the project will not load on the Designer screen/Block screen   or just on your device with WIFI? 

Do you have any images or other resources stored in your Media?    Removing them might help with the issue.

Are you experiencing the image error that has been reported?    Perhaps but I suspect your isse might be something else but need more information to know for sure.

Here are some things to consider if the issue is that the projects do load on the Designer/Block screens but not on the device:

One of the following  possibly applies to your code (all may not apply to your code):

1)  You have coding errors in your blocks.  In the Blocks editor, look in the lower 
left corner of the window for the yellow and red triangle icons. If the red icon has a value larger than 0, 
you have a serious coding error.  Find the block in your code that has a red triangle and 
fix it.   Red triangles always inhibit creating an apk or running a project in the 
emulator or possibly creating an aia file.     Yellow triangles are more forgiving, 
however, sometimes, these need to be fixed because they trip an internal warning and not billing puzzle piece sockets are left un-filled.

2) Your source file (the aia file) is larger than the 5Mb limit allowed in AI2 (the aia can not be larger than 5Mb). You may have put images or other resources in your Media (resources) that you do not use in the app. 
 All the images and sounds in resources count toward the 5Mb limit along with the source code.    You can program 
apps larger than 5Mb in the browser, but the apps will not compile and might not run in the 
emulator or the project may not save as an aia. If this is the case you need to reduce 
the size of your image and/or sound files.   Most image files can be made quite small 
by resizing them using a photo manipulation program on your PC to less than 50Kb each.

3)  You might have more than 10 Screens in your app.  AI2 becomes unstable when more 
than ten screens are used.  Projects CAN be built with slightly more screen but then you should expect your app to occasionally behave erratically.

4) You might have set a Screen icon in the Designer Properties for your project that is too large. Use an image 
sizeof 48x48 px or 96x96px instead and only use jpg or png images.  *.ico files are not 
supported.  The 'icon' (actually an image) can be as large as 520x520 (I think that is the size GooglePlay apps require).  The smaller 'icons' work fine otherwise.

5) You did not code the entire project using App Inventor 2.   If you used one of the 
third-party AI2 clones,you might not be able to load a Project into the AI2 compiler or 
create an apk with the standard AI2.

6) If you incorrectly modified the project's Manifest files using a third-party tool, you may have issues.

7)  Sometimes, if you have LOTS of Layouts on a single screen,  the apk might not 
compile. How many is a lot?  I do not know, keep adding layouts and buttons, compile and try again...when the server crashes, you got a lot.

8)  The network you are using may be overloaded (possibly a school network), or you have other applications running in the background on your computer, or your virus checker is doing a scan.  Sometimes, just trying to access the MIT server a few minutes later will give you a more favorable response.

9)  If you have BlueStacks on your home 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.

10)  Are you using Sensor controls (except for the clock)?   Most Sensor controls or controls related to sms or the phone do not work in the emulators.  They need to be tested on a device.

11) If this is an issue about the Project loading slowly on your device or on the emulator:  Be aware, the more images, layouts, components you have on a screen, the longer it takes for the emulator and Companion to render the graphical screen.  How fast the emulator renders is partially a function of your hardware...how much ram you have, your cpu clock speed etc. Sometimes, with lots of graphics, the emulator will just give up.   Can you develop live using WIFI or using USB? These options almost always render faster than the emulator but will not be at lightning speed if you have lots of graphics.  Be patient.

12)  This happens too:   We have seen instances where it is probable the Google Cloud messed up; other instances where an older PC has had memory issues and caused file corruption of the Project and instances where a user is using a very slow Internet connection (like dial-up) and it is just too slow.

13)  Do you have an AVG, Eset or AVAST virus checker.  Some versions of these products have been reported inhibit running the emulator unless (in the case of AVG) the Advanced Link settings on the software are set to allow AI2 communication.



Check your blocks, see if you have any unused images etc. in the Media (resources), or if any of the above applies and take appropriate action.

Let us know if any of these allow you to open your Project.

MIT is working the issue that has affected some users but it is not solved yet.


댓글 없음:

댓글 쓰기