Flex 3 release ?

Does anyone know when Flex 3 will be release?
The reason I'm asking is because I got into the bad habbit of
using Flex 3 beta for production, but honest I had good reasons, I
swear.... I was having some issues with Flex 2 and Remoting, that
were clieaned up in Flex 3 beta, so I picked up the bad habit of
using the beta version.
But now my Beta Flex 3 is giving me a messaging saying that
it's expiring in 15 days, so I need to find a way to extend the
usage of the beta, Upgrade to Flex 3 if it's released, or go back
to Flex 2...
Carlos

I have read some where that you can use your Flexbuilder 3
(Beta) without time limit if you use your Flex 2.0 Serial number.
(think it was in the blog from
Ted
Patrick )
best regards,
kcell

Similar Messages

Compiler.define in flex-config and compc

I'm having an issue with compile time constants. I'd like to define these constants in two places, but when I do the flex compiler forgets constants defined in my flex-config.xml (DEBUG::DEBUGGING and DEBUG::VERBOSE). I am using flextasks.tasks in ant to build the project.
In my build.xml:
<target name="build-project" depends="init">
    <echo message="Building ${proj.swc.file}" />
    <compc output="${proj.target.dir.bin}/${proj.swc.file}"
        target-player="${proj.flashver}">
        <compiler.define name="INFO::VERSION_MAJOR" value="${proj.version.major}" />
        <compiler.define name="INFO::VERSION_MINOR" value="${proj.version.minor}" />
        <compiler.define name="INFO::VERSION_RELEASE" value="${proj.version.release}" />
        <compiler.define name="INFO::BUILD_TIMESTAMP" value="${proj.build.timestamp}" />
        <compiler.define name="INFO::BUILD_TIMEZONE" value="${proj.build.timezone}" />
        <load-config filename="${mx.sdk.dir}/frameworks/flex-config.xml"/>
        <load-config filename="${basedir}/flex-release-config.xml"/>
        <source-path path-element="${proj.build.dir.src}" />
        <include-sources dir="${proj.build.dir.src}" includes="**/*.as **/*.mxml"/>
        
        <compiler.external-library-path dir="${proj.target.dir.lib}" includes="*.swc" append="true" />
    </compc>
</target>
In flex-release-config.xml:
<flex-config>
    <compiler>
        <debug>false</debug>
        <keep-generated-actionscript>false</keep-generated-actionscript>
        <verbose-stacktraces>false</verbose-stacktraces>
        <optimize>true</optimize>
        <define>
            
            <name>DEBUG::DEBUGGING</name>
            <value>false</value>
        </define>
        <define>
            
            <name>DEBUG::VERBOSE</name>
            <value>false</value>
        </define>
    </compiler>
</flex-config>
If I compile using compc on the command line I can use -define+=NAME,value and it works. Why is it not working using the compc task in ant?

Try adding the append="true" attribute to the define elements. I'm not sure if this will work, but that's how it works (append="true" is the equivalent of +=) for other elements like external libraries.

Tour De Flex is currently not working - desktop or web version. Why?

I'm trying to install the TourDeFlex air app. from this link:
http://www.adobe.com/devnet/flex/tourdeflex.html
When doing so, the app installs and I can run it, but when trying to select 'What's Flex', then I get 'NOT FOUND'.
Can anyone help me?

Sure, there are folks with the authority, but it isn't me. I forwarded your prior post to the person I think can make the decision. We'll see what happens. Basically, Paul is correct. The TDF sources have been donated to Apache, the problem now is that Apache folks don't have the bandwidth to resurrect it on Apache servers. Apache is a volunteer community so if folks want to pitch in to help, let us know on the [email protected] mailing list.
I just lurk on this forum trying to help when I can, mostly to try to get folks to move to Apache Flex. It is no longer under my set of responsibilities. I am still and Adobe employee, but I'm supposed to spend 100% of my time trying to make Apache Flex as good as it can be. Over at Apache, we've even got an alpha of a next-gen Flex SDK and tool chain called FlexJS that outputs MXML and AS to JS. A different set of folks support Adobe Flex and Adobe Flash Builder, but only via issues raised via Adobe Support. I don't believe they watch this forum.
The future of Flex is in the hands of the Flex developers who get involved with Apache Flex. Adobe has only promised five years of support for Flex 4.6 (since it announced the donation to Apache) and has no plans to make any future releases. Over at Apache, Adobe has no influence over Flex. There Flex can live on forever with out fear of surprises from corporate strategy changes. So, if you like Flex and want to keep using it, join the Apache Flex mailing lists and contribute code, testing, answers and help upgrade Tour De Flex. Over 400 bugs that are in Adobe Flex 4.6 have been fixed in Apache Flex releases.
There is no big company like Adobe pouring big money into Flex like it used to. It is up to you, the folks reading this forum, to contribute what you can and collectively create its future. Adobe is actually spending serious money to help by paying me and some others, but it isn't like it used to be. Flex is now truly a community project.
Hope to see you over at Apache,
-Alex

Trying to dynamically load CSS for project at compile time via config XML file to select CSS file.

I'm using the same code base to compile different versions of a project. Each project has different base fonts. I've created multiple css files that use the same style names. The idea being that in the code I reference the style names, then the loaded CSS determines which font (and size, color, etc) is used for each style name.
The CSS files are compiling to SWFs, and those SWFs are referenced in config.xml files. Before compiling, I select the config file to use.
I am loading the CSS SWF files via the StyleManager in the Application.mxml, like so:
styleManager.loadStyleDeclarations( _contentData.elements( 'cssPath' ).@path )
The path traces out correctly as:
assets_embed/styles/project2.swf
For some reasone I must include an fx:Style line in the Application.mxml file or no fonts are recognized. Example:
<fx:Style source="assets_embed/styles/project1.css"/>
If I reference the css for project one (as done above) then most, but not all, styles work. Some styles reference the fonts from the project 1 css, others properly use fonts from project 2 swf. If I point to the CSS for the project I'm compiling in the <fx:Style > tag then all fonts work, but that defeats the goal of using XML rather than code to identify the styles.
So, why do I need the fx:Style line if the css is being loaded via StyleManager?
Why is there "cross talk" between style definitions?
Is there a better way to select styles at compile time?

I read this quickly so I might have missed a detail. I think your describing an issue with recent Flex releases that is described in the fine print somewhere. If you don't have any fonts embedded in the main app and are only bringing in fonts embedded in CSS SWFs, you have to force-link the EmbeddedFontRegistry by adding something like this to the main app's script block.
import mx.core.EmbeddedFontRegistry; EmbeddedFontRegistry;
(Yes, "EmbeddedFontRegistry" is in there twice, once to define the fully qualified name, the other to create a class dependency to force the linking).

4.6 strange display problem

You can see in the image above that the display of the game is offsetted by some amount vertically. The white section is not supposed to be there. In fact the blue is meant to be flush with the bottom of the screen.
This happened by making two changes to a previously perfectly working project: change the SDK to the new 4.6 Flex release candidate including 3.2 air player with support for Stage3d. The other change is in the Air Application Descriptor file: changed the xmlns to end in number 3.2 instead of 2.6. Nothing else has changed. In fact, if I revert to the 4.5.1 SDK, the graphics show as expected.
I have looked for a couple of hours for a solution, but I haven't found anything...
OS: mac
IDE: Flash Builder 4.6 trial
Device: the Flash Builder device simulator, but also seen on a real device
Application settings: fullscreen, landscape, renderMode=direct/gpu (same thing), size: 1024x600
Stage alignment: TOP_LEFT
Stage scaling: none
Project type: Mobile ActionScript
As I said, just the fact of changing to 4.6 introduced the problem and I can toggle it at will be reverting to 4.5.1, so the code hasn't changed. I can add that the white section in the graphic is actually a repeat of the last row of pixels (bleed basically) all the way to the bottom of the screen. With other graphics, that section changes - so not always white.
Thanks for any tips

I received a tip that setting the fullscreen app variable in the application descriptor file to 'false' instead of the normal 'true' for a game will solve the problem while you are developing on the desktop. It works. Thanks Matt.

Can't run app from another machine

Some time ago, I created a prototype using the Flex 2 Beta
tools, and it is working fine on the machine I built it on. When it
runs, it reads in some XML files. It runs fine if I run it directly
from my file system, or from the IIS server on my machine. But if I
move the files to another directory - on the same machine - I
cannot run the demo from the file system. I get errors on startup
saying "file:...blah.xml may not access Internet URL". Also, if I
move the files to a new machine I get the same problem.
This demo is being used internally to my organization to try
to foster the acceptance and potential adoption of Flex
technologies within the enterprise, and we have a big presentation
coming up and I need to get this to work on a laptop. What would be
causing these errors, and how can I fix it? Do I have to install
the Flex release version (which I will be doing pretty soon,
anyway) and recompile it? I just would like to understand the
problem, first.
P.S. I tried adding a crossdomain.xml file to allow access
from any domain, but that had no effect, and I'm not sure how that
even works when launching from the local file system.

Try adding -use-network=false to your compiler options. I
don't know if that will work but your symptoms sound
similar.

Adobe SVN email format change

All,
We will be making a change to the way the subject line will read in the emails that are received from the Adobe Open Source Subversion commits. The hope is for the new format to avoid any further confusion, alarm and in some cases screw-ups. The change
should also aid in making email rules easier to define. The new subject line will be prefixed as follows:
[ svn:PRODUCT ABBREVIATION-BRANCH NAME ] REVISION NUMBER: THE SUBJECT LINE
Product Abbreviations:
BlazeDS – bz
Flex – fx
Subject line example:
For a commit to Flex in the trunk: [svn:fx-trunk] 9999: fixed some stuff
If you have your email rules setup to look for “[svn]” in the subject, I apologize for having you to recreate your email rules, but we think this change will make managing SVN mail better in the future.
This change will be taking place immediately.
Thanks,
Jim Murphy
Flex Release Engineer

This is great. It will totally help clear up what commits happen in flex trunk vs the i10/11 branches.
Great solution!

@Adobe, do you intend to contribute Flash Catalyst as Open Source Project ?

Hello,
in the recent Whitepaper* you write that you no longer develop Flash Catalyst.
Wouldnt it be great if you make it open source (contribute to Apache as well?)
or sell it to another developer so that it can be continued to be developed ?
I think many people will totally agree with this and would be happy to continue using
Flash Catalyst to visually built/prototype engaging GUI for the Apache Flex Framework.
What do you think ?
Best Regards
Marc
Flash Catalyst
Flash Catalyst CS5.5 is the last release of Flash Catalyst.
At this time, it will not be updated to work with Flex SDK 4.6 or any Apache Flex releases nor will it be included in future versions of the Adobe Creative Suite software offerings.
*http://www.adobe.com/devnet/flex/whitepapers/roadmap.html

Hi daslicht,
im also very interrested to know the answer.
But im afraid they wont because it uses code from other proprietary tools.
And even if the community get flash catalyst source code, it will be useless (in a sens) mainly because the synergy with other Adobe Tools will not be maintained. And for me it was the main power of Flash Catalyst.
And knowing that, i think it is more easy for Apache community to create a new tool from scratch not linked to Adobe's tooling chain.
It could be a Flex app!!
For you information, the design view from Flash Builder has also been discontinued by Adobe. But in that case its a flex app incorporated in Flash Builder so theres good chances that Adobe will donate it to Apache community.
So why not use the design view as a base for a Flash Catalyst like tool? by making it a standalone tool or designers.

Why Kill of Flash Catalyst, especially when it works well?

Flash Catalyst
I skin components via an Illustrator files (also psds) received by designers. The joy of skinning and making sure the components are rasterized for performance, and having a stage to edit components and reskin them is wonderful! I adore Flash Catalyst.
Apache Flex
Now with the Flex going to Apache, the white paper states that Flash Catalyst will actually be "Removed" from future Flex releases - This baffles me!
I quote the White Paper:
Flash Catalyst CS5.5 is the last release of Flash Catalyst. At this time, it will not be updated to work with Flex SDK 4.6 (even though it does?!) or any Apache Flex releases nor will it be included in future versions of the Adobe Creative Suite software offerings.
Flash Catalyst workflows will be removed in updated 4.x versions of Flash Builder. - That is a Crime!
I would like to ask, if it is possible to stick with Flash Builder 4.6 (which works with Flash Catalyst 5.5), and continue to develop with these two tools, and no matter what Flash Player (even future ones) users have - would still render?
The idea of killing off something that works so well (if you know how/when to use it), and so enjoyable to work in, angers me!!

You can find the answer. Just modify some config file.
http://chrisgriffith.wordpress.com/2011/12/05/flash-catalyst-cs5-5-and-flash-builder-4-6/
In Applications/Adobe Flash Catalyst CS5.5/plugins/com.adobe.flexbuilder.flex_1.5.0.308731/config.xml add in a reference to 4.6. You’ll need to copy 4.6 into the sdk directory. When you publish it will publish with the 4.6 SDK. Still haven’t figured out how to add new components to the components panel or change the theme (mobile) (or add new Interactions…) You can export this project and import it into FB. Going the opposite way is a bit more trouble. You’ll get an error about the supported SDK’s. You may need to update the hidden project files to “4.5″ instead of “4.6″ which may allow you to import it again… There’s more you can update… search for plugin.xml in the plugins directory.

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
Anyone have an idea on other things to try to debug/resolve this?
Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
Thanks!

After a week's worth of debugging, I found the issue.
The Java type returned from the call was defined as ArrayList. Changing it to List resolved the problem.
I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid. And, why it works in Debug mode and not in Release build is even stranger. Maybe someone can shed some light on the logic here to me.

Flex 4 Release Build breaks text editor

I was working on an editor using FB4 beta 2. Fonts were loaded at runtime ... CFF is being used.
In Flex 4 SDK that comes with FB4 beta 2, my spark rich text field sitting in a group in my application looks fine - proper font families applied and renders correctly. My font + style drop down lists are all fine as well.
As soon as I switch to the release SDK, or any SDK later than FB4 beta 2 (well, major releases) the font styles are not longer properly applied to the field. Changes to the family no longer apply to the rich text field.
The rich editable text that I'm using is basically as follows:
                <s:RichEditableText id="editor" fontLookup="embeddedCFF" renderingMode="cff"
                                    focusEnabled="false" x="100" y="50" focusIn="focusInEditor(event)" focusOut="focusOutEditor(event)"
                                    width="300" height="200">
                    <s:textFlow>
                        <s:TextFlow fontFamily="HelveticaNeueLTStd-MdCn">
                            <s:p fontFamily="HelveticaNeueLTStd-MdCn" fontSize="14" color="0x999999">Test first line of text</s:p>
                            <s:p fontFamily="HelveticaNeueLTStd-Blk" fontSize="18" color="0xFFFFFF">Test second line of text</s:p>
                        </s:TextFlow>
                    </s:textFlow>
                </s:RichEditableText>
That probably isn't too important but I figured I would paste it anyway. I'm using setFormatOfRange primarily and this block of textFlow was only to get some initial content into the text area.
There is a ton of other related code for editing, selection, etc. It seems any font family related change does not get applied.
I know there have been a ton of changes and this may be difficult to pin down. However, this is pretty awkward. The application I was building loaded up fine, fonts loaded up all fine and all editing worked perfectly until going to release SDK.
Is there any change that would cause this to happen?

Ok, so I finally got it working but this is not ideal at all. Adobe really needs to give us some direction on how to properly deal with font embedding and TLF now that the release build breaks all functionality with loading runtime fonts and TLF.
Problem:
I am embedding collections of fonts (faces) into single family classes. Each individual face is registered with Font.registerFont(). I need to do this because I have to have mixed fonts within text flows - at least according to Alex H's recent blog post.
Fonts do not display in TLF without doing the following:
1. GlobalSettings.resolveFontLookupFunction = null;
2. editor.textFlow.flowComposer.swfContext = ISWFContext(this.getFontContext("AnyFamilyNameFromAnyFontEmbedded", false, false, FontLookup.EMBEDDED_CFF));
3. Instead of #2, use editor.textFlow.invalidateAllFormats();
Either #2 or #3 need to be performed. If I have a spark richEditableText control in MXML with defined familes from the loaded fonts. I even tried placing the control into a separate state so it wasn't created until after the fonts were loaded... I still needed to invalidate the formats or set the context.
The "AnyFamilyNameFromAnyFontEmbedded" does not need to be all of the embedded family names. It only needs to be one of them. Once one is used, all embedded fonts work. Also, I have to use the internal namespace to even get access to getFontContext, another oddity that, in my humble opinion, should never be necessary to create mixed style TLF content.
My questions are then:
1. Why am I required to use ISWFContext if I am using Font.registerFont()?
2. Why is GlobalSettings.resolveFontLookupFunction = null; also required for this to work?
3. What is the recommended workflow to embed fonts from multiple SWF files into the release build and have it work without having to jump through all these hoops?

How to create Bin Release folder Through commandline (without flash/flex builder)

Hi friends
is it possible to create bin release folder of my application without using flash builder or flex builder.i want to create the release of my application through sdk.is there any way to create this.i am working on windows.so please let me know any dos based command to create this release.
Thanks and Regards
Vineet Osho

Hi lee thanks for your reply.actually i am already use tha command but it cant create bin release folder it just make swf file.i want all bin-relase folder so that all the css and images and other resources that my application used should comme in relesed folder.is there any way to create bi-relese folder.i am working in flash-builder 4 and my operating system is windows 7
Thanks And Regards
Vineet Sharma

Flex Builder 3 - Export Release Build Feature

Just bought the Flex Builder 3 prof version and imported my
project from Flex Builder 2 to 3. All compiled OK and I see all
.html wrappers and swf (debug and release versions) in the bin
folder. However when I run the "Export Release Build Feature" only
index.swf (my main application file) along with its wrapper
index.html and my images directory gets copied to "bin-release"
folder. Not sure why remaining.swf files corresponding to the .mxml
files are not copied. Do I need to copy these manually???
Appreciate any help with this.
Thanks in advance.

The problem is that:
all the images do not appear in the "Select the output files to include in the exported AIR or AIRI file" section of the Export Release Build. I see only 30 files with the rest of the files missing.
As a work around, what I did is manually copy all the resources/images from bin-debug to bin-release directory and then make the export release build. In this air package after installation, I see now all the images.
so, the original problem with flex builder not being able to include all the images in release build still persists.
thanks,
Sunil

Flex Builder 4 Export Release Build fails on OSX

Flex Builder 4, SDK 4.1.0.16076
When I choose Project->Export Release Build, or Export Release Build from the Export context menu, nothing happens on teh interface, but I see the following error in the log. Any thoughts on solution or workaround?
Thanks
D
!ENTRY org.eclipse.ui 4 0 2011-05-25 14:54:44.886
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.getDefaultOutputFolderPath(ExportReleaseVersionProjectAndLocationPage.java:312)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createLocationControls(ExportReleaseVersionProjectAndLocationPage.java:297)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createControl(ExportReleaseVersionProjectAndLocationPage.java:501)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.createPag eControls(ExportReleaseVersionWizard.java:310)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:734)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:606)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction$1.run(Export ReleaseVersionAction.java:93)
at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction.run(ExportRe leaseVersionAction.java:103)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1669)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1693)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1678)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1421)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3657)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3240)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

looks like this is same as http://bugs.adobe.com/jira/browse/FB-29046 -- export works if turn Application Server in Properties to None/Other rather than J2EE... that bug report was closed as unreproducible. Looks like its still out there in the wild...

Flash Builder 4.5.1 - Problem compile Flex Mobile release build

I am building a flex mobile applicaiton using Flash Builder 4.5.1. The application works fine on the device (Nexus S) and desktop in the debug mode however, whenever I export the release build the app is not installed on the device automatically. When I manually install .apk it also fails (get Application not installed message with green check mark). Any thoughts?

Getting a big closer... Compiled .swf using mxmlc, then manually packaged .apk without any issues... When I try to run: adb install -r myapp.apk: I get the following error:
pkg: /data/local/tmp/myapp.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Perhaps certificates are not respected?

Flex 3 release ?

Similar Messages

Maybe you are looking for