History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: FB-9464
Type: Bug Bug
Status: Closed Closed
Resolution: Not a Bug
Priority: None None
Assignee: Kazue Watanabe
Reporter: Nick Collins
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Flash Builder / Flex Builder

Normal "Run" runs debug SWF

Created: 09/14/07 06:47 AM   Updated: 10/15/07 06:12 AM
Component/s: AS Debugger
Security Level: Public (All JIRA Users )

File Attachments: None
Image Attachments:

1. DirectoryList.JPG
(25 kb)

Severity: Incorrectly Functioning
Reproducibility: Every Time
Discoverability: High
Found in Version: Moxie M3 (Beta 2) - 180470
Affected OS(s): Windows - XP
Steps to Reproduce:
With a flex web project, when I "Run" the application, and it launches in the browser window, the SWF triggers the Flash Player to request "Where is the debugger or host application running?" This is triggered both on the development machine, as well as other machines that try to view it from a web server.

I noticed when I build a flex web project now, there are not two seperate SWF and HTML files, one for "Production" and one for debug, but rather just one SWF and HTML file. Is this intentional, or is it a bug?
Language Found: English
Bugbase Id: none
Regression: Yes
QA Owner: Kazue Watanabe
Resolved by: Peter Flynn
Confirmed Version: Moxie M3 (Beta 2) - 182557
Participants: Ian Ilsley, Jamie Samland, Kazue Watanabe, Matthias Dittgen, Mike Morearty, Nick Collins, Peter Flynn and tony.zheng
Eclipse Configuration: FB Standalone


 All   Comments      Sort Order:
Peter Flynn - [09/14/07 03:52 PM ]
This is intentional. To create a final, non-debug SWF, use "Export Release Version" (available on the toolbar and the Project menu). You can avoid the "Where's the debugger?" dialog box by installing the latest Flash player that is included in the Flex Builder installer.

Ian Ilsley - [10/02/07 01:26 AM ]

I have to say I find this as pretty strange behavior ..
 If I click on run I expect to run a 'production' swf , if I click on 'debug' I expect to run a debug swf .. Now I have to
do an 'export release' before I can 'test' a production swf .. 90% of the time I dont need to run a debug swf ..


Jamie Samland - [10/03/07 08:27 AM ]
I did the "Export Release Version" and my deep linking doesn't work in the swf it makes. Deep linking works fine when I hit "run", but I get the debugger dialog. Requiring all my users get the new Flash player update to avoid this is not an option.

Mike Morearty - [10/04/07 05:54 PM ]
I'm pretty sure the reason deep linking isn't working for you is because you have an older version of the debug Flash player. Since customers have the release player (not the debug one), they won't need to upgrade. Please see longer explanation here: http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=651&threadid=1303610&CFID=15877291&CFTOKEN=c21e6a5d2fa2f9ff-6CF713B0-91AF-2C3D-5E186789C1279709&jsessionid=1211ddcd8585195d3637

Jamie Samland - [10/05/07 08:49 AM ]
@Mike - You might be right, I sent a release version to the client yesterday and they said deep linking is working fine, but it isn't for my.

Matthias Dittgen - [10/15/07 03:44 AM ]
so is it possible to install the latest compatible FlashPlayer plugin without re-installing Flex3 beta2?

tony.zheng - [10/15/07 06:12 AM ]
yes, the flex bulider should install the lastest debug-version flash player for you by default, but sometimes, it does not work properly.
So you had better check the folder C:\WINDOWS\system32\Macromed\Flash to make sure it is the lastest debug version. If no, you could
install it from E:\Program Files\Adobe\Flex Builder 3 Plug-in\Player\win manually. Then that is OK