[flexcoders] Re: Flex Builder 3 debug builds broken, breakpoints all wrong
I agree and have seen this a few times.
One odd occurrence is with a Flex Module in my Flex Application. It
would serve up a stale build of the module unless I added a
trace("foo"); in the code, and then it would force a recompile. But
when I would SVN revert back to the version without the trace
statement, Flex would serve up the stale module SWF.
I had disabled browser caching with web developer toolbar,
cleaned/deleted bin-debug, etc.
What is the JIRA ticket(s) on bugs.adobe.com for these known issues
you guys are mentioning?
-R
--- In flexcoders@yahoogroups.com, "Troy Gilbert" <[EMAIL PROTECTED]>
wrote:
>
> > Did you check whether or not:
> > Menu:
> > Project --->
> > "build Automatically" is checked?
>
> Like I said, I've been developing with Flex for the last 18 months...
> I'm very aware of "build automatically", "clean" and all of their
> implications. It's definitely a bug in the caches...
>
> Troy.
>
Re: [flexcoders] Re: Flex Builder 3 debug builds broken, breakpoints all wrong
> On Fri, Mar 28, 2008 at 9:19 AM, Troy Gilbert <[EMAIL PROTECTED]> > wrote: >> >> I just encountered the issue again, and went through the process of >> deleting all the build stuff manually, caches, etc., and nothing >> helped. So this time I tried flushing the browser cache (actually, >> disabling it with Firefox extension Web Developer). That worked, it >> was a browser cache issue. >> >> Anyone have any ideas why once in a blue moon the browser would serve >> up a cached version of my SWF (served from my localhost, MAMP on OSX) >> while debugging? I was under the impression that the browser wouldn't >> cache documents that have queryvars (hence one reason for the >> inclusion of "?debug=true" when debugging a Flash app). Is there >> something else I need to be doing (possibly MAMP configuration?) to >> ensure that the browser always sees the latest SWF (without having to >> always disable the cache... I am loading a lot of static assets and >> its nice to take advantage of the cache for those)? Adding ?debug=true isn't enough to stop the page being cached - the page signature must change so that the browser thinks that a different page is being requested every time. In this case you could use a number to make the page signature different - the most effective way is probably to use a timestamp and pass the milliseconds value from Date() since this will always be unique. Paul >> Thanks, >> >> Troy.
Re: [flexcoders] Re: Flex Builder 3 debug builds broken, breakpoints all wrong
this is what i did for firefox's cache problems: in the location input, enter: about:config find browser.cache.disk.capacity, set it to 0 this sorted things our for me. also, you may want to use Camino for debug/development. It's much more lightweight. keith On Fri, Mar 28, 2008 at 9:19 AM, Troy Gilbert <[EMAIL PROTECTED]> wrote: > > > > > > > I just encountered the issue again, and went through the process of > deleting all the build stuff manually, caches, etc., and nothing > helped. So this time I tried flushing the browser cache (actually, > disabling it with Firefox extension Web Developer). That worked, it > was a browser cache issue. > > Anyone have any ideas why once in a blue moon the browser would serve > up a cached version of my SWF (served from my localhost, MAMP on OSX) > while debugging? I was under the impression that the browser wouldn't > cache documents that have queryvars (hence one reason for the > inclusion of "?debug=true" when debugging a Flash app). Is there > something else I need to be doing (possibly MAMP configuration?) to > ensure that the browser always sees the latest SWF (without having to > always disable the cache... I am loading a lot of static assets and > its nice to take advantage of the cache for those)? > > Thanks, > > Troy. >
Re: [flexcoders] Re: Flex Builder 3 debug builds broken, breakpoints all wrong
I just encountered the issue again, and went through the process of deleting all the build stuff manually, caches, etc., and nothing helped. So this time I tried flushing the browser cache (actually, disabling it with Firefox extension Web Developer). That worked, it was a browser cache issue. Anyone have any ideas why once in a blue moon the browser would serve up a cached version of my SWF (served from my localhost, MAMP on OSX) while debugging? I was under the impression that the browser wouldn't cache documents that have queryvars (hence one reason for the inclusion of "?debug=true" when debugging a Flash app). Is there something else I need to be doing (possibly MAMP configuration?) to ensure that the browser always sees the latest SWF (without having to always disable the cache... I am loading a lot of static assets and its nice to take advantage of the cache for those)? Thanks, Troy.
[flexcoders] Re: Flex Builder 3 debug builds broken, breakpoints all wrong
I've seen this behavior in Flex Builder 2 plenty of times. What usually works for me is a combination of cursing, cleaning, deleting the entire bin folder, and rebooting my machine. --- In flexcoders@yahoogroups.com, ivo <[EMAIL PROTECTED]> wrote: > > You beat me to the post, was just about to ask the list if anyone knew a way around this issue. Just upgraded to FB3 release and this became immediately apparent. > > What works for me tho is after I update source files I delete their swf/swc from the bin folders. > > -Ivo > > - Original Message > From: thirtyfivemph <[EMAIL PROTECTED]> > To: flexcoders@yahoogroups.com > Sent: Wednesday, March 5, 2008 10:16:03 AM > Subject: [flexcoders] Flex Builder 3 debug builds broken, breakpoints all wrong > > Okay... I'm about to throw my laptop across the room. I am burning > time trying to fix this *bug* (bug, because as a user I shouldn't be > able to break this) in Flex Builder (I've seen it in 2, now seeing it > in 3). > > I'm just happily editing my project... when all of sudden a trace > statement I add doesn't show up. Hmm... odd, let's set a breakpoint to > check it out... > > What!? I try to set a breakpoint and it skips to a different line > number, just as if I'd try to set a breakpoint on a comment. This > smells familiar. Some cached incremental build data is lingering > somewhere and junking everything up... > > So I clean and rebuild... no good. > > I clean, restart Flex Builder, rebuild... no good. > > I clean, reset my machine, rebuild... no good. > > I clean, shut down Flex Builder, manually go and clear all the cache > files from my workspace's '.plugin' folder, rebuild... no good. > > So, what's the deal? Am I missing some cache files? I find it > infuriating that explicitly choosing "clean" doesn't get me the same > result as if I checked out the source on a new machine and clicked > build... what's the point of clean if there's still some lingering > cache files? > > Can anyone help? I can't effectively move forward at this point as > every time I make a change and rebuild my source the *changes* *don't* > *show* *up* in the resulting SWF. What the f*ck!? > > Sorry if i sound a little angry... but we're trying to launch are > decently sized RIA after 18 months of work sometime in the next few > weeks so I'm a little, tiny bit antsy to get back to compiling/QA! > > Help!!! > > Troy. > > > > > > > > > >
Re: [flexcoders] Re: Flex Builder 3 debug builds broken, breakpoints all wrong
> Did you check whether or not: > Menu: > Project ---> > "build Automatically" is checked? Like I said, I've been developing with Flex for the last 18 months... I'm very aware of "build automatically", "clean" and all of their implications. It's definitely a bug in the caches... Troy.
[flexcoders] Re: Flex Builder 3 debug builds broken, breakpoints all wrong
Did you check whether or not: Menu: Project ---> "build Automatically" is checked? If not, then flexbuilder doesn't re-compile. And also note a clean doesn't necessarily re-compile unless that option is checked. D. --- In flexcoders@yahoogroups.com, ivo <[EMAIL PROTECTED]> wrote: > > You beat me to the post, was just about to ask the list if anyone knew a way around this issue. Just upgraded to FB3 release and this became immediately apparent. > > What works for me tho is after I update source files I delete their swf/swc from the bin folders. > > -Ivo > > - Original Message > From: thirtyfivemph <[EMAIL PROTECTED]> > To: flexcoders@yahoogroups.com > Sent: Wednesday, March 5, 2008 10:16:03 AM > Subject: [flexcoders] Flex Builder 3 debug builds broken, breakpoints all wrong > > Okay... I'm about to throw my laptop across the room. I am burning > time trying to fix this *bug* (bug, because as a user I shouldn't be > able to break this) in Flex Builder (I've seen it in 2, now seeing it > in 3). > > I'm just happily editing my project... when all of sudden a trace > statement I add doesn't show up. Hmm... odd, let's set a breakpoint to > check it out... > > What!? I try to set a breakpoint and it skips to a different line > number, just as if I'd try to set a breakpoint on a comment. This > smells familiar. Some cached incremental build data is lingering > somewhere and junking everything up... > > So I clean and rebuild... no good. > > I clean, restart Flex Builder, rebuild... no good. > > I clean, reset my machine, rebuild... no good. > > I clean, shut down Flex Builder, manually go and clear all the cache > files from my workspace's '.plugin' folder, rebuild... no good. > > So, what's the deal? Am I missing some cache files? I find it > infuriating that explicitly choosing "clean" doesn't get me the same > result as if I checked out the source on a new machine and clicked > build... what's the point of clean if there's still some lingering > cache files? > > Can anyone help? I can't effectively move forward at this point as > every time I make a change and rebuild my source the *changes* *don't* > *show* *up* in the resulting SWF. What the f*ck!? > > Sorry if i sound a little angry... but we're trying to launch are > decently sized RIA after 18 months of work sometime in the next few > weeks so I'm a little, tiny bit antsy to get back to compiling/QA! > > Help!!! > > Troy. > > > > > > > > > >
