[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5960
  • Last Modified:

debugging flex - Error #2044: Unhandled IOErrorEvent:. text=Error #2035: URL Not Found.

newbie to flex/flash

wondering how to properly debug flex applications. when i run my flex app, i get the following error message

Error #2044: Unhandled IOErrorEvent:. text=Error #2035: URL Not Found.

i realize this must relate to a resource url, but how am i do determine what line in the code threw this error?
i tried running the app in debug mode, and got the

"Where is the Flash debugger host running?"

message, localhost didnt work.

can someone point me to some resource about learning how to debug flex apps and perhaps help with this issue?
0
chrismarx
Asked:
chrismarx
  • 7
  • 6
1 Solution
 
bgloddeCommented:
Start with searching for "new URLRequest" in the source and inspect URLs of the resources being loaded. You also can set a breakpoint in the first function that is executed (typically triggered by creationComplete or init event in the Application tag) and step through the app (F6) until you see it throw the exception.
0
 
chrismarxAuthor Commented:
ok,
 i've got the debugger/developer version of flash installed, and now i no longer see the message about where the flash debugger is. interestingly, i also no longer see my error message, but I haven't changed anything in the app. however, i put a simple trace statement in the init() function in the main.mxml page and i dont even see that in the console. i am running the app by pressing the debug button. what am i missing?
0
 
bgloddeCommented:
Can you post the relevant parts of the code so your situation can be further clarified? init() is called by the creationComplete event right?
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
chrismarxAuthor Commented:
im using the cairngorn framework if that makes any difference. it would appear that the init method is being wired up in the application mxml
<mx:Application 
	xmlns:mx="http://www.adobe.com/2006/mxml"
	xmlns:services="vnw.services.*" 
	xmlns:control="vnw.control.*"
	xmlns:inc="vnw.view.includes.*"
	xmlns:include="vnw.view.include.*"
	xmlns:special="vnw.view.level1.special.*"
 
	xmlns:local="*"
	pageTitle="title"
	initialize="init()" 
	layout="absolute" 
	frameRate="14" xmlns:windows="vnw.view.level1.windows.*">
 
etc...then
 
<mx:Script>
	<![CDATA[
		
		import com.adobe.cairngorm.control.CairngormEventDispatcher;
		
		import flash.utils.Timer;
		import flash.events.TimerEvent;
		
		import mx.binding.utils.ChangeWatcher;
		import mx.events.PropertyChangeEvent;
		
		import mx.core.Container;
		import mx.managers.PopUpManager;
 
....etc
 
private function init() : void {
			
			//model.debug_win = PopUpManager.createPopUp(this, DebugWindow, false) as DebugWindow;
			
			//model.debug_win.debug("hello");  
			trace("hello");
			
			//Production
			model.initModel.initVO.workStreamID = Application.application.parameters.workStreamID;
			
 
			model.initModel.initVO.workStreamID = "WS100076";
 
			// create and dispatch init event
			var event : GetInitEvent = new GetInitEvent();
	  	event.dispatch();
			
			currentState = "level0";		
		}

Open in new window

0
 
chrismarxAuthor Commented:
also,
 i put in breakpoints in the init() function, and nothing ever happened (execution didnt stop at those points)-
0
 
bgloddeCommented:
There's absolutely no reason that initialize method is not fired - try an Alert.show("hello"); - I've had similar issues with the debugger before....
0
 
chrismarxAuthor Commented:
and im actually quite sure that the inti method is fired, i mean, the application is loading and working as expected. using Alert.show results in compilation error. thanks so much for helping with this-
0
 
bgloddeCommented:
You'd have to import mx.controls.Alert; to use the Alert box ;)

There is another issue that seems to rear it's ugly head on occasion with Flex Builder - the resources sometimes do not get copied to the bin and bin-debug directories. Try manually copying over your resources to those locations and see if that fixes it.
0
 
chrismarxAuthor Commented:
yeah, that worked i can see the alert, checking the bin thing now-
0
 
chrismarxAuthor Commented:
do i need to enable to console or something to see the messages? the bin folder has the images and styles folder, along with the main.swf, main-debug.swf, etc.,

i dont have any other flash debugging tools installed. on the console tab is says (on the header section)
<terminated> main[Flex Application] file:/C:/workspace/flex/bin/main-debug.html

0
 
bgloddeCommented:
Using Firefox 3? If so, take a look at this http://bugs.adobe.com/jira/browse/FB-13064.

If so - switch your debugging browser to something else and see if you get trace again. Last time mine did this, I switched it out to Safari (on XP) and things came back to life.

To change the browser, go to Window > Preferences and type in "browser". Then add and/or switch.
0
 
chrismarxAuthor Commented:
thank you!!
yes, i am using firefox 3, when im using a product for some time, i would know to check for these kinds of things, but being new to flex, i couldnt imagine that was the problem. thank you!!
0
 
bgloddeCommented:
Glad we could solve it - happy Flexing
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now