In Flex Mobile Release Build arguments.callee cause crash

This is my code in a simpler way:
In my main MXML:
private var applicationData:AppData = AppData.getInstance();
My AppData Class
package {
    public class AppData {
        private static var instance:AppData;
        public function AppData(caller:Function) {
            super();
            if (caller != AppData.getInstance)
                throw new Error("This class is a Singleton and can not be instantiated: Use the .getInstance() method!!");
        public static function getInstance():AppData {
            if (!instance)
                instance = new AppData(arguments.callee);
            return instance;
arguments.callee cause a crash in the Release Build (just stop to splash screen), not in the Debug Version.
It is possible to log this kind of error?

Tring to run via adl i get this error:
-bash: adl: command not found
im inside the bin directory: /Applications/Adobe\ Flash\ Builder\ 4.6/sdks/4.6.0/bin/
And should put the folder AdobeAIRSDK somewhere or should install?
Thanks and sorry for all this question!

Similar Messages

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 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?

Actionscript mobile release build 0 percent

Windows 7 64bit Flashbuilder 4.7JDK 1.7 AIR3.7
my action script mobile game will not export a release build, it just hangs at 0 percent for hours and hours. In my task manager Java.exe grows to 7GB. Please help me!!
others are having the same issue here
http://forums.adobe.com/message/5688472#5688472
http://forums.adobe.com/message/5688472#5688472

I commented out a large array containing 30,000 elements, the release version published in minutes. Thanks for the advice....
I am hoping if I upgrade from 8GB ram to 16GB this will help FlashBuilder publish a release version. I assumed since the Debug Version worked great the release would as well ...lesson learned.

Some questions to Flex Mobile

Hey there,
does Flex Mobile / Flash Builder 4.5.x supports this things to Apps on iOS & Android?
- Sound/Musicplayback
- Videoplayback
- SQL on a dedicated server
- Send an eMail from the App
- use the native keyboard of the device (such as iOS)
Thank you!
- bb

Yes to all except the email... I don't think you can even do that in a native iOS app... I could be wrong though. The best you can do is navigate to a mailto: link to initiate the native mail support 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

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.

Blank Screen in Flex Mobile IOS Release Build

Please I need help!
After exporting the release build with the right certificate, after installing on iphone a get just a blank screen (it stop to the splash screen). I cant understand why, the debug version it's working correctly!
Thanks!

http://forums.adobe.com/message/4520676#4520676

Flex mobile 4.6 app works inside flash builder but not in android emulator

Originally posted on stackoverflow: http://stackoverflow.com/questions/8663892/flex-mobile-4-6-app-works-inside-flash-builder- but-not-in-android-emulator
I have a basic flex mobile 4.6 app and it works fully fine in the flash builder built-in emulator using an android device profile like aria...
It also launches fine in the android emulator but one particular view shows blank (and this view works fine in flash builder).
Before I get in to many details of the view are there any categorical gotchas that can be causing this?
I can't seem to get the trace statements from the app to show in 'adb logcat'. It seems I need to compile a debug version of the apk but I don't know how to do this. I use the 'Export Release Build' from the Project menu in flash builder and it doesn't seem to have an option for debug=true.
The problematic/blank view basically uses the stagewebview and iotashan's oauth library to call linkedin rest apis... A different (and working) view can make restful web service calls in the emulator fine, so it doesn't seem to be an internet permission.
The source code contained in the problematic/blank view is almost identical to the tutorial found at:http://www.riagora.com/2011/01/air-and-linkedin/
The differences are: a) The root tag is a View b) I use StageWebView instead of HtmlContainer c) I use my own linkedin key and tokens.
I would appreciate it if someone can provide me with some pointers on how to troubleshoot this situation. Perhaps someone can tell me how to debug the app while running in the emulator (I think I need the correct adt command arguments for this which matches the 'Export Release Build' menu but adds the debug param?)
Thanks for your help in advance.
Comment Added:
I suspect that this has to do with connections to https:// api.linkedin.com and https:// www.linkedin.com. The only reason I can think of that the same code is not having issues inside of Flex Builder but indeed having issues in the Android emulator is something to do with certificates. Any ideas?

Thanks er453r,
I have created a project that clearly reproduces the bug. Here are the steps:
1) Create a UrlLoader and point it to https://www.google.com (HTTPS is important because http works but HTTPS does not)
2) Load it
3) Run in Flash Builder 4.6/Air 3.1 and then run in Android emulator. The former works with an http status 200. The latter gives you an ioerror 2032. I am assuming what works in Flash Builder is supposed to work in the Android Emulator and what what works in the emulator is supposed to work in a physical device (plus or minus boundary conditions).
I see a certificate exception in adb logcat but not sure if it's related...
Here is the self contained View code which works with a TabbedViewNavigatorApplication:
<?xml version="1.0" encoding="utf-8"?>
<s:View xmlns:fx="http://ns.adobe.com/mxml/2009"
                    xmlns:s="library://ns.adobe.com/flex/spark"
                    xmlns:mx="library://ns.adobe.com/flex/mx"
                    xmlns:ns1="*"
                    xmlns:local="*"
                    creationComplete="windowedapplication1_creationCompleteHandler(event) "
                    actionBarVisible="true" tabBarVisible="true">
          <fx:Script>
                    <![CDATA[
                              import mx.events.FlexEvent;
                              protected var requestTokenUrl:String = "https://www.google.com";
                              protected function windowedapplication1_creationCompleteHandler(event:FlexEvent):void
                                        var loader:URLLoader = new URLLoader();
                                        loader.addEventListener(ErrorEvent.ERROR, onError);
                                        loader.addEventListener(AsyncErrorEvent.ASYNC_ERROR, onAsyncError);
                                        loader.addEventListener(SecurityErrorEvent.SECURITY_ERROR, securityErrorHandler);
                                        loader.addEventListener(HTTPStatusEvent.HTTP_RESPONSE_STATUS, httpResponseStatusHandler);
                                        loader.addEventListener(IOErrorEvent.IO_ERROR, ioErrorHandler);
                                        var urlRequest:URLRequest = new URLRequest(requestTokenUrl);
                                        loader.load(urlRequest);
                              protected function requestTokenHandler(event:Event):void
                              protected function httpResponse(event:HTTPStatusEvent):void
                                        label.text += event.status;
                                        // TODO Auto-generated method stub
                              private function completeHandler(event:Event):void {
                                        label.text += event.toString();
                                        trace("completeHandler data: " + event.currentTarget.data);
                              private function openHandler(event:Event):void {
                                        label.text += event.toString();
                                        trace("openHandler: " + event);
                              private function onError(event:ErrorEvent):void {
                                        label.text += event.toString();
                                        trace("onError: " + event.type);
                              private function onAsyncError(event:AsyncErrorEvent):void {
                                        label.text += event.toString();
                                        trace("onAsyncError: " + event);
                              private function onNetStatus(event:NetStatusEvent):void {
                                        label.text += event.toString();
                                        trace("onNetStatus: " + event);
                              private function progressHandler(event:ProgressEvent):void {
                                        label.text += event.toString();
                                        trace("progressHandler loaded:" + event.bytesLoaded + " total: " + event.bytesTotal);
                              private function securityErrorHandler(event:SecurityErrorEvent):void {
                                        label.text += event.toString();
                                        trace("securityErrorHandler: " + event);
                              private function httpStatusHandler(event:HTTPStatusEvent):void {
                                        label.text += event.toString();
                                        //label.text += event.responseHeaders.toString();
                                        trace("httpStatusHandler: " + event);
                              private function httpResponseStatusHandler(event:HTTPStatusEvent):void {
                                        label.text += event.toString();
                                        trace("httpStatusHandler: " + event);
                              private function ioErrorHandler(event:IOErrorEvent):void {
                                        label.text += event.toString();
                                        label.text += event.text;
                                        trace("ioErrorHandler: " + event);
                    ]]>
          </fx:Script>
          <fx:Declarations>
                    
          </fx:Declarations>
          <s:Label id="label" y="185" width="100%" color="#0A0909" horizontalCenter="0" text=""/>
</s:View>

Flex iPad Application : Run code before application enters background Application Type: Flex Mobile Application Target Platform: iPad AIR Version: 4.0 Development Environment: Flash builder 4.6 I want to run some code just before iphone application goes

Application Type: Flex Mobile Application
Target Platform: iPad
AIR Version: 4.0
Development Environment: Flash builder 4.6
I want to run some code just before iphone application goes into background. I need function similar to didEnterBackground
of native xcode app
(https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIApplicationDelegat e_Protocol/Reference/Reference.h
tml#//apple_ref/occ/intfm/UIApplicationDelegate/applicationDidEnterBackground:)
I tried using devactivated function of flash.display.STAGE.
I used following addEventListener:
STAGE = this.parent.stage;
STAGE.addEventListener(Event.DEACTIVATE, onAppDeactivated);
It worked for me but only when device is connected to development environment in debug mode. When I create my release build
it is not working.
So how can I make sure that my code runs before application goes into background.

Even I am facing almost same issue
Problem installing Adhoc version to iPhone and iPad - Development Environment Is - Adobe Flash CS6

Adobe Flex Mobile + AIR - Custom iOS Build Setting

I am building some Adobe Flex Mobile application using Flex 4.6.0 + AIR 3.5 only for iOS
This app involves some iOS Native Extension created also by me.
The thing is that this ANE uses some third party framework (GD.framework from Good Dynamics Technology). That framework requires GD FIPS linker to be used, and for that, i need to set some custom build settings in a .xcconfig file, with this content:
FIPS_PACKAGE=$(CURRENT_ARCH).sdk LDPLUSPLUS=/Good Technology/Good.platform/FIPS_module/$FIPS_PACKAGE/bin/gd_fipsld LD=/Good Technology/Good.platform/FIPS_module/$FIPS_PACKAGE/bin/gd_fipsld
The ANE compiles OK, but then, I add the ANE to the app, I compile the app, but when I launch the app, it crashes because the FIPS linker was not properly got set on my Flex Mobile project.
So, my question is:
Is there a way to set the above configuration on my project like somebody would do in a Xcode project?
Regards!

I see your key as a reserved key for iOS. I haven't tested it myself but here's the keys you cannot change. Sure enough, MinimumOSVersion is reserved.

Release build and standard packaging doesn't work for iOS mobile project.

Hi,
We are trying to port our web application on iOS(iPad). Made some minor changes and package ipa with fast packaging method. It works great.
Now we are try to package application for AppStore and use Standard method. But error occurs.
     Error occurred while packaging the application:
     Exception in thread "main" java.lang.Error: Unable to find named traits: spark.components::Application
         at adobe.abc.Domain.resolveTypeName(Domain.java:225)
         at adobe.abc.Domain.resolveTypeName(Domain.java:142)
         at adobe.abc.GlobalOptimizer$InputAbc.resolveTypeName(GlobalOptimizer.java:272)
         at adobe.abc.GlobalOptimizer$InputAbc.readInstance(GlobalOptimizer.java:994)
         at adobe.abc.GlobalOptimizer$InputAbc.readAbc(GlobalOptimizer.java:390)
Distribution certificate and provisioning profile are used for compilation.
Restarting FB and OS doesn't help. Packaging via command line also throws same error.
Exporting Release build shows other error. After opening Export Release build window and click next error occur:
     Encountered errors or warnings while building project XXXX.mxml.
     configuration variable 'runtime-shared-library-path' requires a value 'rsl-url'.
All the libraries are merged into code, not RSL.
OS: Windows XP SP3, Windows 7.
Flash Builder: 4.5.1.
Flex SDK: 4.5.1 build 21328.
AIR: 2.7.1(2.7 shows erros also).
Thanks in advance for your answers.

Hi,
Please send your swf and app-xml to [email protected] so that we can try it at our end.
Thanks,
Amish.

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: debugging Flex Mobile application on Android Virtual Device

Hi,
we are trying without success to debug a flex mobile application in Flash Builder 4.5 on an Android Virtual Device (AVD).
We can debug with real Android devices via Flash Builder 4.5, by using a standard Mobile Application debug configuration with "On device" launch method, but emulated devices are not listed in the "Choose device" Flash Builder 4.5 window.
The emulated device is correctly listed by "adb" command line tool, as the following screenshot shows:
c:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.0\lib\android\bin\adb" devices
List of devices attached
emulator-5554 device
("emulator-5554" has been created and started with Android AVD Manager standard Eclipse plug-in)
By using the adb command-line tool we can also install applications on the emulated device, but we'd like to use Flash Builder 4.5 directly, without manually using adb.
Many thanks in advance for any direction.
PS: we can debug with Flash Builder "internal" android emulator (the one used with "On desktop" launch method), but we want to use the more "realistics" android emulated devices provided by Android SDK (Android Virtual Device (AVD)).

well that's just ... oh what's the word I'm looking for? ... um ... ah yes - inconvenient.
I've been wrestling with this too. I use VDs with eclipse all the time, I'm wondering why it's not supported in flashbuilder. I mean, it's just a VD that runs on a virtual port, plugs into the editor like a read device would - right?
I'm going to take a wild stab at this and say it probably has something to do with running a program inside (Air) a virtual machine, running inside a virtual machine inside a virtual device?

Mxmlc arguments for replicating FB's Export Release Build

Which mxmlc arguments do I need to replicate the behaviour of Flash Builder 4's Export Release Build?

Noone?

In Flex Mobile Release Build arguments.callee cause crash

Similar Messages

Maybe you are looking for