Export Release Build on Flash Builder 4 Beta 2

Hi Everyone,
I have a Flex 4 project that is organized as a main app project with several related projects that are linked in, along with several libraries that get included (I use granite dataservice and tweener, among others). The project runs fine when I do a normal build, I have deployed the resulting swf independently on a web server and its working fine.
Now, whenever I try to do 'Export release build' from the Project menu, the resulting release build doesnt run at all, and it crashes with weird errors, like for example, it first crashes because of a null reference in the partAdded method in one of the components I created, when I removed that component completely it crashed because of a type coercion error on one of the data service objects, and this goes on with all sorts of errors that never existed in the normal 'debug' version not built with the export option.
So I have two questions:
Does anyone have any clue what might be wrong? I would have posted examples but it looks to me like an application-wide anomaly, maybe because of it not loading the libraries or the resources correctly? I tried both build path options or merging sdk libraries into the code or using runtime libraries, didnt work, not sure if it is related.
What exactly does 'Export release build' add for me? is the release build faster than the normal one?
Thanks a lot.

Hi,
A release build optimises the compile,(no debugging code etc). The swf will be a little quicker and a lot smaller. If you are getting null pointers and data service issues maybe something in your create order is a bit out. If you have an idea of what the offending component may be see if you can set its creation policy. This would be my first thought the other could possibly be some sort of local versus network issue on the release build.
David.

Similar Messages

Workaround for using the latest nightly SDK 4.0 builds with Flash Builder Beta 2

The latest builds of SDK 4.0 have been updated in preparation for including playerglobal.swc for Flash Player 10.1. Flash Builder Beta 2 can not find playerglobal.swc due to the addition of the {targetPlayerMinorVersion} variable found in the flex-config.xml file.
When using recent nightly SDKs with Flash Builder Beta 2, please modify them as follows:
1) Rename the folder <nightly sdk location>/frameworks/libs/player/10.0 to "10"
2) Edit the file <nightly sdk location>/frameworks/flex-config.xml and remove ".{targetPlayerMinorVersion}" and save
When you restart Flash Builder, we will now find a correct location for playerglobal.swc, allowing for code hints and many other features to work properly.
Jason San Jose
Quality Engineer, Flash Builder

Bump.
As people continue to have problems with the nightly SDK 4 builds and Flash Builder Beta 2, please remember to use the workaround described at the top of this thread. Also see http://blogs.adobe.com/jasonsj/2010/02/workaround_for_using_the_latest_nightly_sdk_40_buil ds_with_flash_builder_beta_2.html.
Jason San Jose
Quality Engineer, Flash Builder

Is there any release plan for Flash Builder?

Hi,
does anybody know when Adobe plans to release Flash Builder 4 (at least aproximately)? Should it be this year 2010?
Thanx,
pyso

Adobe wrote:
Adobe is not yet disclosing the final release date for Flash Builder 4
Wikipedia wrote:
Adobe has announced that Flex 4.0 (code named Gumbo) will be released in early 2010.

Flex Builder 4 == Flash Builder 4

I've seen a ton of blogs discussing Adobe's decision to rename Flex Builder to "Flash Builder" for version 4.0, and wanted to see what you all think.
Personally I agree with many of the blog comments that it is a bad move.
Flex apps are not Flash apps (thankfully), they just happen to run in the same runtime (Flash Player). AIR apps are not Flash apps as well.
I still think Flex will succeed, but are you all looking forward to working in Flash Builder 4?
I for one hope Flex continues to succeed despite this move.

Just recently re-infuriated by this terrible decision on Adobe's part so I located this thread.
On Adobe labs they use this as the reasoning:
If you are new to the Flash Builder beta, the first thing that you’ve already noticed is that we are renaming Flex Builder to Flash Builder. This name change will create a clear distinction between the free open-source Flex framework and the commercial IDE.
So instead of developers (most of which have already learned the distinction by now after TWO versions) having to know the difference between an SDK and an IDE (what kind of idiot developers can't understand this???), now Flash designers (many more of those) and programmers also need to understand the difference between Flash Builder and Flash Professional. They aren't the same product in the least and are barely related, but Flash "newbies" won't know that from the names. Meanwhile Flex newbies will still be confused by the Flex SDK/Flash Builder mismatch.
You would think that Flex devs (many of which come from the Java world which has exactly the same concept of SDK/IDE) who are familiar with software engineering (unlike your typical Flash developer), would be able to overcome this "confusion" more easily than the much larger number of Flash devs.
So now this change is needed, to add even more confusion for everybody involved:
When Flash Builder 4 is released for purchase, the current plan is to name the full-featured edition Flash Builder 4 Premium edition. This change is being made to reduce any risk of confusion between Adobe Flash Professional and Adobe Flash Builder.
If it's already realized that you're just replacing the confusion of Flex newbies with the confusion of both Flex AND Flash newbies... why do it?
Was this some over-paid executive's knee jerk solution to an almost insignificant problem? Given that it seems almost nobody thinks this change is a good idea, perhaps they should have asked (here or elsewhere) their customers what they thought of such a change before simply announcing it and passing it off as a big marketing improvement?
But more importantly: Is it too late to reconsider this idiocy? (I can't wait till Google searches start mixing up Flash Pro and Flash Builder information making it just that much harder to find relevant links!)
If you really want to eliminate the confusion of "Flex Builder" vs "Flex SDK" for the mentally challenged, why not simply rename Flex Builder to a more creative and unique name similar to what Java has in Eclipse/JDK? Heck even calling it FX Builder would have been better than Flash Builder! The marketing dept here needs a serious wake up call IMO.

[svn:fx-trunk] 10317: In ASDoc comment, change reference of "Flex Builder" to "Flash Builder"

Revision: 10317
Author:   [email protected]
Date:     2009-09-16 12:56:03 -0700 (Wed, 16 Sep 2009)
Log Message:
In ASDoc comment, change reference of "Flex Builder" to "Flash Builder"
QE notes: -
Doc notes: -
Bugs: -
Reviewer: -
Tests run: - checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/netmon/NetworkMonitor.as

Flex Builder 4.6 app runs fine in builder - exported release Air app flashes and dies

I have tried exporting release build on more than one computer.
I have successfully exported release builds of other projects.
if I open the application's .exe file and scroll down I see this kind of stuff:
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.
      R6033
- Attempt to use MSIL code from this assembly during native code initialization
This indicates a bug in your application. It is most likely the result of calling an MSIL-compiled (/clr) function from a native constructor or from DllMain.
R6032
- not enough space for locale information
      R6031
- Attempt to initialize the CRT more than once.
This indicates a bug in your application.
R6030
- CRT not initialized
R6028
- unable to initialize heap
    R6027
- not enough space for lowio initialization
    R6026
- not enough space for stdio initialization
    R6025
- pure virtual function call
   R6024
- not enough space for _onexit/atexit table
    R6019
- unable to open console device
    R6018
- unexpected heap error
    R6017
- unexpected multithread lock error
    R6016
- not enough space for thread data
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
   R6009
- not enough space for environment
R6008
- not enough space for arguments
   R6002
- floating point support not loaded
    Microsoft Visual C++ Runtime Library
... <program name unknown> Runtime Error!

I have tried exporting release build on more than one computer.
I have successfully exported release builds of other projects.
if I open the application's .exe file and scroll down I see this kind of stuff:
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.
      R6033
- Attempt to use MSIL code from this assembly during native code initialization
This indicates a bug in your application. It is most likely the result of calling an MSIL-compiled (/clr) function from a native constructor or from DllMain.
R6032
- not enough space for locale information
      R6031
- Attempt to initialize the CRT more than once.
This indicates a bug in your application.
R6030
- CRT not initialized
R6028
- unable to initialize heap
    R6027
- not enough space for lowio initialization
    R6026
- not enough space for stdio initialization
    R6025
- pure virtual function call
   R6024
- not enough space for _onexit/atexit table
    R6019
- unable to open console device
    R6018
- unexpected heap error
    R6017
- unexpected multithread lock error
    R6016
- not enough space for thread data
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
   R6009
- not enough space for environment
R6008
- not enough space for arguments
   R6002
- floating point support not loaded
    Microsoft Visual C++ Runtime Library
... <program name unknown> Runtime Error!

Can't export zxp file with Flash Builder, CSExtensionBuilder

Dear all
I write Create Suite Extension project. I build this project success. It's output swf file.
I want to export to .zxp file to connect with IA Plugin.
In my Project. I do these steps:
1. Select Export => Adoble Creative Suite Extension Builder=>Creative Suite Extension and click "Next" button
2. Browe Certificate, type password and click "Finish". Have progress panel show and visible.
But no file in Export Directory.
My enviroment is:
WinXPSP3
Flash Builder 4.7 trial
CSExtension 2
IIlustrator CS6
Adobe Extension Manager CS6
What's wrong ?
Could you have other ideal for me.

I try to use
WinXPSP3
Flash Builder 4.6 trial
CSExtension 2
IIlustrator CS6
Adobe Extension Manager CS6
My project can export zxp file success.
But I can't run and debug my project with Flash Builder4.6.
Do you have same problem,

Running a Captive Runtime debug build through flash builder

Is there a way to launch a debug configuration through Flash Builder that has the captive run time built in?
I am developing and testing an app for android devices that do not have the newest version of the Air Runtime, some of the devices require captive runtime because they cannot upgrade. I need to be able to launch the app on these devices AND get debug/console information from flash builder for identifying defects.
any ideas?

Hey Wright,
Captive Runtime can only be used at export release build time.
Hence you cannot debug the application with captive runtime bundled.
Thanks,
Hari

Coldfusion Builder and Flash Builder 4 Premium

I am not sure should this question go in Flex forum or ColdFusion.
I am going to buy the ColdFusion builder which come with the Flash Builder 4 Standard. And I need to have Flash Builder 4 Premium. So should i buy the upgrade which is US$499 or should i but the full Flash Builder 4 Premuim for US$699?

Adam,
Thanks for the quick/thorough reply! You stated: You can use FB4 to write source files for any version of CF.
With that, I will continue to march foward with what tools I do have; I just didn't want to waste time if the end result wasn't going to work.

Export Release Build Flash Builder 4.5 fails to load over the web.

Exported Release Build Application fails to load over the web. You can reproduce using the following steps:
1. Create New Flex Project in Trial Flash Builder 4.5.
2. Use the default Flex 4.5 sdk.
3. Configure as a web application.
3. Place the following MXML code in the main application file:
<?xml version = "1.0" encoding = "utf-8"?>
<s:Application xmlns:fx = "http://ns.adobe.com/mxml/2009"
xmlns:s = "library://ns.adobe.com/flex/spark"
xmlns:mx = "library://ns.adobe.com/flex/mx"
minWidth = "955"
minHeight = "600">
<fx:Declarations>

</fx:Declarations>
<s:TextArea text = "Hello World!" width = "100%" height = "100%">
</s:TextArea>
</s:Application>
3. Save the main application file and Export Release Build to bin-release.
4. Place all files in bin-release on IIS web server in a web accessible location.
5. Go to the web accessible location in any browser with newest flash player and view the application's html page.
Actual Results:
Flash movie appears blank. Context menu shows Movie Not Loaded. Network traffic shows application main swf downloaded. Framework dependent swfs not downloaded.
Expected Results:
Movie loads. Hello World! appears in text box. Context menu does not show Movie Not Loaded. Framework dependent swfs downloaded.
Workaround (if any):
Deploy on an Apache web server.
The tests were run on IIS 7.x (7.0 for one, and 7.5)
Flex application was built using Flex 4.5.0 SDK pre-bundled release (built-in flex 4.5 with Flash Builder 4.5 trial) on Mac OS X 10.6.7 (10J869)
Flash Player 10.3.181.14
Example failing website:
http://staging.ibenergy.com/Test.html
Any idea as to why my exported release build fails? Any help would be appreciated.

Just tried this out on an IIS server with Flash player 10.3.181.14 - it worked.
Are you using the release version of Flash Builder 4.5 with the release version of Flex SDK (not a prior SDK build)?
The URL you mentioned gives me a 403 forbidden error.
-Anirudh

Flash Builder 4.6 Mobile Application Packaging and Exporting

Hello Everyone,
I'm novice to Flash builder,using Flash Builder 4.6 to develop android application.
It runs in desktop no error occur. But when I export it or try to run it on my
SAMSUNG GALAXY Y S5360 phone it doesn't run. It's Android version is 2.3.6
I plugged the USB with pc and tried to run on app on my phone.
First builder ask that Do you want to install ADOBE AIR to device I select the "YES" option then after it go for 57% and show me an error
Error occurred while installing the applicaiton: pkg:/data/local/tmp/Runtime.apk Failure[INSTALL_FAILED_CPU_ABI_INCOMPATIBLE] 3261 KB/s (8653085 bytes in 2.333s)
And when I Export and Release Build for .apk file.I select the Captive Runtime.
Then it shows a message
The package(s) were successfully created but the application could not be installed on one or more devices: Device ID 0123456789ABCDEF(Google Android): Problem Occurred while installing ADOBE AIR.
Please guide me...
Thanks

After searching on internet and have hands on this problem, finally found the solution.
SAMSUNG Galaxy Y S5360 has CPU 830 MHz ARMv6 and minimum requirement of minimum system requirements for AIR 3.3 Beta on Android :
CPU: ARMv7 processor with Vector FPU, Minimum 550MHz, OpenGL ES2.0, H.264 & AAC H/W Decoders OS: Android 2.2, 2.3, 3.0, 3.1, 3.2 & 4.0 RAM: 256MB RAM
Later I used a Motorola mobile handset with higher version my .apk file worked well.
Click here For Samsung Galaxy Y S5360 Phone Specification
thanks to everyone for your efforts.

Export release build fails with project created by Launchpad

When I try to export a release build (using Flash Builder 4.5) of a project created in Adobe Air Launchpad (p8_3-0-1_081911) I get the following error message:
"error occurred while saving the project settings: 'default' build target cannot be found for the selected project"
Is this a bug or am I doing something wrong? Any help/ideas would be greatly appreciated!
Rob

I solved this by creating a new project and copying everything across. But it was time-consuming work - especially creating all the new value objects and data services. Air Launchpad is a great concept and has helped me a lot, but this particular forum is dead.
Rob

Nightly SDK and Flash Builder Beta

I am using Flash Builder Beta and have tried different nightly builds (ie. 4.0.0.9437, 4.0.0.9417, 4.0.0.9188) and have the same issue - when going into Design View I receive several warnings:
Design View could not load fiber_rb.swc. It may be incompatible with this SDK, or invalid. (DesignSWFLoader.ERROR_LOAD_VERIFY).
The same error for: fiber.swc, serializers_rb.swc and sparks.swc.
Does anybody have a fix besides two workspaces with diff. sdks?
There have been some other discussions in regards to this but with no fix.
First ... Adobe talks of using nightly builds with instructions.
Second ... when users have problems such as above a standard reply is "this has been fixed in an internal build". How does that help us?
Third ... in Flex Bug and Issue Management System this was a reply -
Heidi Williams - [08/04/09 05:40 PM ]
I don't think we want to spend time on encouraging users to use newer SDKs with DV of Beta 1. There are probably lots of things that won't work so they should either just get on prerelease or wait for the next Beta.
Fourth ... prerelease is not open any more and I for one am unfortunately not on it. FWIW - I do own a Flex Builder 3 license.
I understand Flash Builder is a Beta program, but why talk of nightly sdk releases and using Flash Builder if there are issues and unavailable internal builds. And if Adobe is working on bug fixes, along with changes such as the Rename List, why not give users access to those internal builds? At least licensed users. Let everyone keep up to date!

Hi,
Form early in the piece it was acknowledged that nightly builds would not work corrrectly with design view. As there will be a second beta in a matter of days now It would be best to wait for that. The builds from the pre-release program have shown a great amount of improvements across the board so I am sure the end of August(hopefully) beta release will be pretty good and make a lot of people happy.
I use locally compiled sdks that I update every night and things are working reasonably well. So just hold on for a little longer and enjoy the second beta release when it arrives.
David.

***URGENT*** - Problem Installing Flash Builder 4 beta

Hi folks,
I'm really having a trouble with Installing FLASH BUILDER 4 beta on my WinXP SP2, 1.5 Ghz processor, 256 Mb RAM, 1.12 GB free on C drive, 1.26 GB free on H:drive, and 1 GB free on D drive.
But still i'm getting this prompt by Installer files I dowloaded from Adobe Labs for Flash Builder 4 beta.
Do i need more Hard Drive space ?
I have attached the jpeg image of the prompt.
Please Help me with this. I have a client with a project to build on Flash Builder 4 beta & only got 3 days to deliver.
thanks in advance.
regards
Ronny Depp

Firstly, are you serious ?
virtually no hard disk space(the install files need to extract with enough space to actually then install the software)
virtually no ram 256mb is barely enough for windows XP to start up. How are you going to run Flashbuilder
1.5ghz cpu - hmmm I don't think flashbuilder will run on a pda....
delivering a project in 3 days with beta software that you are obviously unfamiliar with...sounds almost like a mastercard ad
$100 for a cpu, $100 for some ram, $100 for some hard disk, look on the clients face when he saw the result- priceless...
hate to take the mickey, but I couldnt let something like this slide by it was just to easy
David.

Debug icon gone from Flash Builder 4 Beta 2

Gentlepersons,
In previous versions of Flex Builder (including Flash Builder Beta 1) there was a handy debugger-launcher icon in the upper-left corner of Flash Builder's main window. It looked like a green bug. That icon is missing from Flash Builder Beta 2 (or at least, it ain't there in my just-installed copy of Flash Builder Beta 2).
How do I get that handy icon back?
Thanks! :-)
Jim Plamondon

If you right-click the toolbar you can get to the 'Customize perspective' dialog.
From there make sure commands >> flash run/debug option is checked.
Oddly, there is no "Flash run/debug" option to check.
Please see the attached picture.
Note that I am running Flash Builder Beta 2 (build 253292) on Eclipse 3.4.2 (build M20090211-1700) on Max OS X (version 10.5.8).
Thanks!
--- Jim

Export Release Build on Flash Builder 4 Beta 2

Similar Messages

Maybe you are looking for