If you ever got into the following error (see bellow after this paragraph) you must know how you can overcome it.

The error is triggered only in debugging. No trace of it in the normal run. But if you need to debug and get this error it will pause the debug session and even after lots of resume pressed you’ll won’t get over it because is a cyclic error.

undefined
	at flash.events::EventDispatcher/dispatchEvent()
	at mx.effects::Effect/effectStartHandler()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\Effect.as:1310]
	at flash.events::EventDispatcher/dispatchEventFunction()
	at flash.events::EventDispatcher/dispatchEvent()
	at mx.effects::EffectInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\EffectInstance.as:580]
	at mx.effects.effectClasses::CompositeEffectInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\CompositeEffectInstance.as:172]
	at mx.effects.effectClasses::SequenceInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\SequenceInstance.as:150]
	at mx.effects::EffectInstance/finishRepeat()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\EffectInstance.as:685]
	at mx.effects.effectClasses::SequenceInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\SequenceInstance.as:156]
	at mx.effects::EffectInstance/finishRepeat()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\EffectInstance.as:685]
	at mx.effects.effectClasses::SequenceInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\SequenceInstance.as:156]
	at mx.effects::EffectInstance/finishRepeat()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\EffectInstance.as:685]
	at mx.effects.effectClasses::SequenceInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\SequenceInstance.as:156]
	at mx.effects::EffectInstance/finishRepeat()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\EffectInstance.as:685]
	at mx.effects.effectClasses::SequenceInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\SequenceInstance.as:156]
	at mx.effects::EffectInstance/finishRepeat()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\EffectInstance.as:685]
	at mx.effects.effectClasses::SequenceInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\SequenceInstance.as:156]
	at mx.effects::EffectInstance/finishRepeat()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\EffectInstance.as:685]
	at mx.effects.effectClasses::SequenceInstance/play()
	[C:\autobuild\3.x\frameworks\projects\framework\src\mx\effects\effectClasses\SequenceInstance.as:156]

The error is triggered by Sequence and the code looks like this…

<mx:Sequence id="movement" repeatCount="0" startDelay="{delay}">
    <mx:Move id="movementUp" target="{this}" duration="{interval}" 
        yTo="0" />
    <mx:Move id="movementDown" target="{this}" duration="{interval}" 
        yTo="{_startYPos}" />
</mx:Sequence>

What’s the problem? After trying different things on the code I noticed that instead of setting the target property of the Sequence I did set up the target of each Move item. So by removing the target from each Move and adding one to Sequence may fix the problem.

Another thing to check is that the sequence is called only once for the target object. If the same effect is called twice or more on the same object and the previous effect did not finished their job a conflict appears. That means that starting the effect on a event that triggers more than once (ex: updateComplete, addedToStage) will end in this error also. Try use creationComplete event instead.

It is important to tell you that the Flex SDK I used to test this are 3.4 and 3.5 from Adobe Nightly Builds.

Hope this helps you.

The last week I have been working on a Flash/Actionscript 3 project and everything worked well. The project got in an 75% finalized. Meanwhile I needed to install a software product and it crashed my Windows Vista. Saved the important data and tried to fix it without having to reinstall the whole OS and all my needed applications but no success. The inevitable has occurred – must reinstall the OS.

After re-installation I returned to my Flash/Actionscript 3 project. At a point in my development needed to delete an mp3 file but deleted the wrong one. So I wanted to add it back to the project’s library but I had a big surprise – an error occurred:

One or more files were not imported because there were problems reading them.

It was the same file that I added to the project before the windows’ crash but this time could not add it to the library. Tried all kinds of ways to add it but no success. Tried to modify its bit-rate also without success.

Started googling about the problem and found this on Adobe’s site:

Flash does not internally support MP3 files with a bitrate over 160kbps. Importing sound files over this size will cause Macromedia Flash to ask Quicktime to handle the import via Quicktime’s audio subsystem.

Although Adobe is saying that if the mp3 having a bit-rate lower than 160kbps will not be affected by this I can say that I tried to lower the bit-rate to that file and than import it in the library but didn’t work. It seems that the problem is not the bit-rate only.

Truly I didn’t reinstalled the Apple Quicktime after the crash (but had it installed before the crash). So out of my curiosity and because I wanted to get over this issue as faster as possible I installed Quicktime. And the import worked like a charm.

It seems that Flash authoring tool is – in a small measure – dependent on the system codecs.

So if you get into this problem install Quicktime and you should not have the problem anymore. If you already have Quicktime installed Adobe’s advice is to uninstall it and install the latest version by downloading it from quicktime.com.

Wish you won’t get this error.

I’ve been playing with Tweensy these days. Tried to understand how it works and how to create effects using particles generator. At some point I run into an error like the following one:

ReferenceError: Error #1065: Variable Box is not defined.
at global/flash.utils::getDefinitionByName()
…

What triggered it is this part of code:

var myClass:Class = getDefinitionByName("Box") as Class;

The error is saying that the it cannot retrieve the class code because the class is not compiled with the application. Even though you put something like

import mx.containers.Box;

the class is not compiled with the application because the linker and the compiler do not add classes that are not referenced in the code.

What is the solution… Pretty simple and straight forward:

private var _dummyVarToAddBoxToAppCompilation:Box;

Even though you’ll never use the _dummyVarToAddBoxToAppCompilation variable it is necessary to use that line to instruct the compiler to include mx.containers.Box in the compilation.

You’ll find the same answer on multiple blogs and forums but still needed to make an article on it. More is always better and easier to find.

Today I managed to find this error twice. It is happening in AIR applications. I had the same application in Flex and then I ported it to AIR. The error that appeared is this:

SecurityError: Error #3015: Loader.loadBytes() is not permitted to load content with executable code.

The error is saying that you’re no more allowed to load executable byte arrays.

To resolve it just use allowLoadBytesCodeExecution property of LoaderContext class like this:

var myLoaderContext:LoaderContext = new LoaderContext();
myLoaderContext.allowLoadBytesCodeExecution = true;
 
var mySwfLoader:SWFLoader = new SWFLoader();
mySwfLoader.loaderContext = loaderContext;
mySwfLoader.addEventListener(Event.COMPLETE, handleLoadComplete);
mySwfLoader.addEventListener(HTTPStatusEvent.HTTP_STATUS, handleLoadFault);
mySwfLoader.load(myByteArray);

This is all. Hope this helps you.

I think some of you may encountered this “wonderful” runtime error, mostly when you work in a team, building different applications that will load in another one.

Shortly the application is telling us that parts are build using different versions of Flex SDK. In my case the main application was build using Flex SDK version 3.1.0 and the application to be loaded was build using Flex SDK 3.2.0

This are some possible errors:

VerifyError: Error #1053: Illegal override of removeChildBridge in mx.managers.SystemManagerProxy.

ReferenceError: Error #1065: Variable _*_mx_managers_SystemManager is not defined.

VerifyError: Error #1014: Class ISWFLoader could not be found.

ReferenceError: Error #1065: Variable _SWFLoaderStyle__embed_css_Assets_swf___brokenImage_1003344314 is not defined.

To get rid of these errors compile your application’s parts with the same Flex SDK.

You can download Flex SDK from here: http://opensource.adobe.com/wiki/display/flexsdk/Download+Flex+3.

Also you can update your Flex Builder to the last version which includes also the last version of Flex SDK: http://www.adobe.com/support/flex/downloads_updaters.html.

These day I’ve been fighting with this issue: trying to get the Flexer XML feed from FeedBurner into a Flex application. As many of you may know FeedBurner serves the XML with an XSL and browsers that know XSL will parse it and display it in a nicer way that a simple xml.

The problem is that I use IE 7 for development and debugging which is not the best thing to do. So I did a small application to read a feed from an specified URL.

At run-time in IE I always got this error (is displayed after clicking on Get HTTPService button with format=”xml” unchecked – ONLY IN IE) :

Error #1085: The element type “link” must be terminated by the matching end-tag “</link>”.

When I did look in the message.body property of the fault event I was shocked to see that what I get is a HTML page – NOT an XML one. HTML pages do have tags that do not close like “link” tag used to add CSS to the page.

I tried every property of HTTP service, some headers and content types, I also made a URLRequest approach but the same thing.

In the other browser the things were different. Everything was OK. I was requesting for an XML I got an XML. That is great! But I still need to make it work in IE.

It seems that IE is different… It parses everything before sending it to the flash player. I’m not a hundred percent sure if is correct what I am saying but that is how I explained it. Then a “brilliant” colleague of mine found the needed thing – in the request add format = “xml” as request. It seems that when format = “xml” is set FeedBurner sends another header back to IE browser which will tell the browser not to parse the XML with XSL. So, I did it like below (starting with line 11 in the whole code):

testGetUrl.send((useFormat.selected ? {format:'xml'} : {}))

Notice {format:”xml”} object which holds our request parameter.

Here is the whole code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" 
    layout="absolute" width="370" height="310">
    <mx:HTTPService id="testGetUrl" 
        fault="handleFault(event)"
        result="handleResult(event)"
        resultFormat="e4x"
        url="{geturl.text}">
    </mx:HTTPService>
    <mx:Button x="10" y="40" label="Get HTTPService" 
        click="testGetUrl.send(
            (useFormat.selected ? {format:'xml'} : {})
        )"/>
    <mx:Button x="137" y="40" label="Get URLRequest" 
        click="handleGetUrlRequest(event)"/>
    <mx:CheckBox id="useFormat" x="10" y="70" 
        label="Use format=&quot;xml&quot;"/>
    <mx:TextInput id="geturl" x="10" y="10" 
        width="350" text="http://feeds.feedburner.com/flexer/"/>
    <mx:TextArea id="geturlresp" x="10" y="96" 
        width="350" height="204"/>
    <mx:Script>
        <![CDATA[
            import mx.rpc.events.ResultEvent;
            import mx.rpc.events.FaultEvent;
 
            private function handleFault(e:FaultEvent):void
            {
                var temp:String = e.fault.faultString.toString() + 
                    "\n\n" + e.message.body.toString();
                geturlresp.text = "HTTPSERVICE FAULT!\n\n" + temp;
            }
 
            private function handleResult(e:ResultEvent):void
            {
                var temp:* = e.result;
                geturlresp.text = "HTTPSERVICE RESULT!\n\n" + 
                    e.result.toString();
            }
 
            private function handleGetUrlRequest(e:MouseEvent):void
            {
                var urlReq:URLRequest = new URLRequest(geturl.text + 
                    (useFormat.selected ? "/?format=xml" : ""));
 
 
 
                urlReq.method = URLRequestMethod.GET;
                var urlLoader:URLLoader = new URLLoader(urlReq);
                urlLoader.addEventListener(
                    Event.COMPLETE, handleUrlRequestComplete);
            }
 
            private function handleUrlRequestComplete(e:Event):void
            {
                var tmp:* = e.currentTarget.data;
                geturlresp.text = "URLREQUEST COMPLETE!\n\n" + 
                    tmp.toString();
            }
        ]]>
    </mx:Script>
</mx:Application>

I made also a URLRequest option so you can see that is something that is not happening only when using HTTPService.

Again… I want to specify that the error appears only on IE.

We may write new articles on this as we will found more about it. So keep reading us.

In the previous article found here we reverted to 9.0.28 flash player because we still need the debugging version of flash player for Flex Builder 2. The approach is working and the debug is working again but sometimes in bigger application where a lot of actionscripting is involved some runtime errors are arising. It seems that the player found in “Player Backup/debug” is not the same with the last player (and in deed it seems to be the player from Flex Builder 2.0.0 not the one from the 2.0.1 update) and because of that some errors will appear. To solve this issue i found Archived Flash players available for testing purposes where different versions of flash player can be downloaded for testing purposes. I’ve downloaded “Flash Player 9 (debugger versions) (61.0 MB)” and from there installed the 9.0.28 version also as simple debug version and also as ActiveX. From now on the runtime error didn’t appeared anymore.

These days I ran into a problem. I updated the flash player (from 9.0.28) to the last version (9.0.47 – moviestar) and after that the debug didn’t want to work anymore. The error that Flex Builder 2.0.1 displays is:

C:\Program Files\Mozilla Firefox\plugins\NPSWF32.dll

Flex Builder cannot locate the required version of the Flash Player. You may need to install Flash Player 9.0 or reinstall Flex Builder. Do you want to try to run your application with the current version?

I searched the internet but nothing helped me but the ultimate version was to backup all my projects and uninstall the whole Flex Builder 2.0.1 application together with the plugins installed to help me in development (like Subversion).

The very funny thing was that after finishing uninstall I noticed some folders left in Flex Builder 2 program file folder… and among those was Player Backup\debug where a lot of backups for problems with flash players. Next time after updating your flash player if you need to use the Flex Builder’s own flash player (which has debug) go to C:\Program Files\Adobe\Flex Builder 2\Player Backup\debug and run “Install Flash Player 9.exe” to get back to the old version.