Check in ActionScript if compiled for release-build

Hi,
I am looking for a way to check in ActionScript if it is compiled for a release build. I saw the flash.system.Capabilities.isDebugger, but that only detects if the player is a debug-player. What is the way to test this?
Thank you,
Andrej

Hi,
This question is related to Flash builder. Please post this under "Flash Builder 4 and Flex 4 Labs Archive" forum.
Thanks

Similar Messages

Compiler options for release build

I am using Ant to build a series of swfs in an Actionscript project and I want to compile them as small as possible, but I can't compile them as small using Ant and the mxml compiler as I can compiling in FB using the Release Build. What options can I use to emulate the FB release compilation?
I use optimize=”true” and debug=”false”
I have also seen this asked here:
On: http://flex.gunua.com/?p=79 Chris asked:
Does anybody know why the swf file is bigger when compiled by Ant, as opposed to when it’s done by the Flex Builder. It is even smaller (1/2 the size) when I use the “Export Release Build” option.
I am using optimize=”true” and debug=”false” in the mxml task, but it does not seem to be enough.

Hi Josh,
I think this should help. The -dump-config option should help you get what you want.
http://help.adobe.com/en_US/flashbuilder/using/WSbde04e3d3e6474c4-59108b2e1215eb9d5e4-8000 .html#WSbde04e3d3e6474c4-59108b2e1215eb9d5e4-7ff0
Nishad

An AppBarButton is randomly fired after the App is compiled for releasing

I'm developing a new App with VS 2013 for Windows Phone 8.1 (WinRT) and I'm getting desperate that sometimes works and sometimes doesn't work. I need to compile N times the same project to make that one element works. This
is my code:
XAML:
<Page.BottomAppBar>
<CommandBar x:Name="appBar">
<AppBarButton x:Name="btnNew" Icon="Add" IsCompact="False" Label="new result" Click="btnNew_Click"/>
<AppBarButton x:Name="btnShare" IsCompact="False" Label="share" Click="btnShare_Click">
<AppBarButton.Icon>
<BitmapIcon UriSource="Assets/AppBar/share.png"/>
</AppBarButton.Icon>
</AppBarButton>
<CommandBar.SecondaryCommands>
<AppBarButton x:Name="menuPersonal" Label="profile" Click="menuPersonal_Click"/>
<AppBarButton x:Name="menuTips" Label="tips" Click="menuTips_Click"/>
<AppBarButton x:Name="menuHelp" Label="help" Click="menuHelp_Click"/>
<AppBarButton x:Name="menuAbout" Label="about us" Click="menuAbout_Click"/>
</CommandBar.SecondaryCommands>
</CommandBar>
</Page.BottomAppBar>
C#:
private void menuTips_Click(object sender, RoutedEventArgs e)
Frame.Navigate(typeof(Tips));
private void menuPersonal_Click(object sender, RoutedEventArgs e)
Frame.Navigate(typeof(Personal));
private void btnShare_Click(object sender, RoutedEventArgs e)
Frame.Navigate(typeof(Share), txtLast.Text);
private void btnNew_Click(object sender, RoutedEventArgs e)
Frame.Navigate(typeof(OcrResult));
private void menuHelp_Click(object sender, RoutedEventArgs e)
Frame.Navigate(typeof(Help));
private void menuAbout_Click(object sender, RoutedEventArgs e)
Frame.Navigate(typeof(About));
The problem ONLY happens in the Profile menu option.
When it's not working, VS shows me this kind of messages after I did click on the button.
The thread 0xb08 has exited with code 259 (0x103).
The thread 0x1b0 has exited with code 259 (0x103).
What I have already tried:
Changed the name of the Class that I need to load.
Re-created the Frame.
Moved the location of the item.
Changed the name of the function.
Created one function for all options (it doesn't matter if I add a break point, I cannot know why it's not working).
Tried the Tapped Event (same problem).
Added several try catchs everywhere.
I should clarify that this problem happens even in another form where I'm calling the same Frame and it doesn't open it there too.
Even any break point doesn't work when the App gave that error. I'd like to know if someone has experimented this issue and if someone have lived it perhaps someone could so kind to give me an idea how to fix it.
Thank you for your worthy knowledge and time.
Federico Navarrete
Post-Data:
In my opinion it's a bug from Visual Studio because if it was from Windows Phone, it would never work and sometimes work.

Hi FANMixco,
Well Done!
I am very glad that you have solved your problem by yourself. If you have any other questions, welcome to post it in this forum.
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Export release build failed with an error message: complilation failed while excuting : compile-abc

I updated air sdk from 4.0 to 16.0 beta to fix apple app store submitting bug. I can build the project and run it on simulator without any problem. But when I tried to export the ios release build, I got this error message: complilation failed while excuting : compile-abc.
I use commmand line to excute compile-abc.exe with the parameters that adt gives it, but it failed without any error message.
Here is the command line:
compile-abc.exe -mtriple=armv7-apple-ios -filetype=obj -sdk "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1 - air16\lib\aot/lib/avmglue.abc" -fields "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1 - air16\lib\aot/lib/air-fields.arm-air.txt" -O3 -abc-file-list=E:\MyApp\bin-debug\AOTBuildOutput8184169967790207636.tmp\ABCFilesList.txt
There's a empty file AOTBuildOutput-0000001821_1821.o left in the command line workaroud path. I opened file AOTBuildOutput-0000001821.abc, but didn't get any clue. How can I trace this problem?

Still having similar issues - seems to be when I embed an image - but works for every release except for release build
Tried your work around but doesnt seem to make a different
[Embed(source = "/../assets/[email protected]")]
protected static const ATLAS_IMAGE:Class;
[Embed(source = "/../assets/[email protected]", mimeType = "application/octet-stream")]
protected static const ATLAS_XML:Class;
[Embed(source = "/../assets/iconMap.png")]
protected static const ATLAS_IMAGE_LOW_RES:Class;
[Embed(source = "/../assets/iconMap.xml", mimeType = "application/octet-stream")]
protected static const ATLAS_XML_LOW_RES:Class;
if(Starling.current.viewPort.width > 320)
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE(), false), XML(new ATLAS_XML()));
}else{
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE_LOW_RES(), false), XML(new ATLAS_XML_LOW_RES()));

Link ant step to 'Export Release Build'

We're now managing our assets totally manually, mainly with ant steps, away from Flash Builder's hands, which imo gives us plenty of benefits, but one definite drawback, exporting a release build. With nearly every other thing you do in Flash Builder, you're able to hook an Ant step to it, but I can't seem to find any place for release builds.
Currently what we have to do is create the 'bin-release'/'bin-release-temp' (depending on the type of project web/mobile & desktop) and copy our assets in to that folder to be packaged up when we then do a release build.
Is there any way to automate this step? All previous attempts to figure out how to have proven to be in vain.
I don't accept marking an assets folder that contains text and binary files as a source folder and choosing "Copy non-embedded files to the output folder" as a proper solution, as that creates an overhead on Flash Builder that's totally unnecessary and can produce lag while working with it, if you've a large assets folder.
Thanks for any help ye might be able to give on this, seaders.

So, even after setting up a new project, the problem didn't go away. Seems as if the problem sits within the libraries I'm using, though none of them do show any errors or problems.
Edit:
I was wrong accusing Flash Builder on this one! I've had two asset source paths that overlapped and apparently, Flash Builder can't handle that when you try to make a release build. Again, debugging always worked fine. I didn't get any warnings either, so it took me quite some time to even think that that might be an issue.
Still, the pletheora of Flash Builder bugs remains!
Found a new one with is also rather annoying recently;
Open the local history of a file and try to copy some text from that file, you'll instantly get a java nullpointer, resulting in the fact that the text isn't copied to the clipboard.
Edit2:
That last edit was actually based on a premature thought of success. Unfortunately, the project still doesn't compile. There are no errors or problems whatsoever in neither of the library projects or the main project.
Edit3: - Finally solved it!
After re-installing FB4.7, thus overwriting the old installation with all it's SDKs, I figured that the merged SDKs might have been causing this issue.
I've merged SDKs several times before using FB4.7 and it worked fine all the time, the absolutely ridiculous way Adobe forces us to update the AIR SDK with 4.7 is so prone to error, that I might have made a mistake this time though.
So for everyone who struggles with this issue as well, make sure your SDKs are in order! Also check the version numbers in air-sdk-description.xml which is located in the AIRSDK folder.

Export release Build failed.

https://www.dropbox.com/s/kt6m03xmj5vee35/Aquarium.zip
Fast & Standard version is OK.
Error occurred while packaging the application:
Exception in thread "main" java.lang.NullPointerException
     at adobe.abc.Block.succ(Block.java:150)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
     at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs(Algorithms.java:214)
          at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4672)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3546)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2247)
          at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:532)
          at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:341)
          at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:533)
          at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:80)
Compilation failed while executing : ADT

Still having similar issues - seems to be when I embed an image - but works for every release except for release build
Tried your work around but doesnt seem to make a different
[Embed(source = "/../assets/[email protected]")]
protected static const ATLAS_IMAGE:Class;
[Embed(source = "/../assets/[email protected]", mimeType = "application/octet-stream")]
protected static const ATLAS_XML:Class;
[Embed(source = "/../assets/iconMap.png")]
protected static const ATLAS_IMAGE_LOW_RES:Class;
[Embed(source = "/../assets/iconMap.xml", mimeType = "application/octet-stream")]
protected static const ATLAS_XML_LOW_RES:Class;
if(Starling.current.viewPort.width > 320)
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE(), false), XML(new ATLAS_XML()));
}else{
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE_LOW_RES(), false), XML(new ATLAS_XML_LOW_RES()));

Incorrect AIR release build destination

Using Flash Builder 4, I observed that whenever an AIR project is compiled (Export Release Build) the resulting .air file is placed on the project's root regardless of the user's selection
Same does not occur whti Flex project (Web Based)
Any ideas?

Interesting.
I was thinking of it as a Flash Builder bug.
However, behavior is similar but not identical. In my Flex (non AIR) project case export works perfectly.
I am suspecting something configuration related. But, I haven't played at all with eclipse configuration (I never do for safety and uniformity etc.)
I ended up thinking of it as a bug
Any other ideas?

"Export Release Build" does nothing in Burrito

I get an error when trying to export a release build of a library project: Unhandled event loop exception
Is it necessary to do a release build to get rid of debug data maximize performance, minimize size of the SWC?
If this is a bug, should I use Apache Maven or some such system for release builds in the meantime?
Is there some work-around? I saw this was a problem is Flash Builder 4 and 4.0.1 too based on forum posts but never experienced it.
http://bugs.adobe.com/jira/browse/FB-29046
http://bugs.adobe.com/jira/browse/FB-27412
http://forums.adobe.com/thread/614588
Here is the complete log:
java.lang.NullPointerException
at com.adobe.flexbuilder.exportimport.ExportImportPlugin.getExportReleaseBuildUIManager(Expo rtImportPlugin.java:154)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.getUIMana ger(ExportReleaseVersionWizard.java:108)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.getPageContent(ExportReleaseVersionProjectAndLocationPage.java:249)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionProjectAndLocati onPage.createControl(ExportReleaseVersionProjectAndLocationPage.java:176)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.createPag eControls(ExportReleaseVersionWizard.java:414)
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:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Session Data
eclipse.buildId=M20100909-0800
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -clean

- It is a good practice to use a release-quality version (non-debug SWF file or AIR file) of your application using the Export Release.
- You can choose to do a command line build using the steps mentioned here http://help.adobe.com/en_US/flashbuilder/using/WSbde04e3d3e6474c4-59108b2e1215eb9d5e4-8000 .html
- Is it possible for you to share your project so that we can try to reproduce the problem at our end.

Flash Builder 4.7 Release Build plays slow on Android

I am using FB 4.7 to build a mobile Flex app for Android (Nexus 10) which works fine when i use the debug apk in the development environment and on the Nexus but the release build plays at a slower framerate.
It feels like the GPU render setting in the xml is ignored. The framerate is very slow during a big animation but speeds up in smaller animations
If I decompile the release apk i can see the renderMode is set to GPU
The release build process is also ignoring all the folders and associated files in the bin-debug. The only files copied to the release temp folder are the swf (with smaller filesize) and the app xml. I have to manually copy all associated files with each build, which is quite annoying
Does anyone know how to fix the slow playback for release builds?
Or is there a way to rename the development apk so that it doesn't have the '-debug' suffix as this apk plays correctly
Thanks

hi ade_1,
i have figured out excatly the same where i also have the nexus 10 tables. Do you had a chance to test it on another device?
Do you have found a way to fix it?
I use AIR SDK 3.8 with FB 4.7.
The release version with runtime build-in is a lot of slower.
Thanx
Gary
Update:
When i debug the app (over USB) and then export a release version that is automatic installed on the device, i got the slow performance. BUT!! when i switch off the device, discounnect the USB calbe, start the release app, i got the full performance back.
Can you try this and report if i´m right?

Export Release Build for datagrid [xml file doesnt show?]

SRC folder
          assets
                    icons
          db.xml (located within assets folder)
datagrid.mxml
default.css
I am able to load the database and it populates my "db.xml" with no issues, however when I export release build and run the app - the database displays but with no information? I noticed that the my "db.xml" was not exported as well.
It is set up correctly? or do I need to just drop my icons, db.xml within src folder and not seperate them?
thanks

When you export a release build, it takes all your MXML And ActionSCript files and turns them into a SWF without the extra debugging code. If you are not embedding the XML in the swf, then this is expected behavior.
In your project properties, under Flex Compiler you can try checking the "copy non-embedded files to output folder"; but I believe this is only for debugging purposes and not for exporting a release build.

Release Build for Dev vs. Production environment

I'm working on a very small project that performs an LDAP
search using a CFC on our Dev box. The folder structure between
Development and Production are the same so when I create a release
build and copy it from the dev environment to the production server
I get a "send" error on the client. The compiled release build is
copied to the same folder structure location as it was on the dev
box, but I believe the application is still trying to point to the
dev box ip address vs. the production server address. How do I
handle exporting a release build for a different server than the
one I'm developing on?

How is your classpath build up?
if it's like this:
SET CLASSPATH=c:\prod;c:\dev
try
SET CLASSPATH=c:\prod
CLASSPATH=%CLASSPATH%;c:\dev
if that doesn't work try setting your classpath to nothing:
SET CLASSPATH=%CLASSPATH%
Please tell me if this helped, I've had a lot of problems with my PATH and CLASSPATH to, and I ain't sure I gave the solution. So please reply to let me know this is the answer or not.

Not using the most recent checked in version of the web app DLL in Release build

Hi folks
Got some peculiar behaviour - I have three build configurations set up within VS2K13 for Debug, Release and DebugOnLive.
There are some basic XML transformations to update emails, db-settings etc - all very simple and working.
Needed to do a DebugOnLive build to test an emergency fix and everything built fine. Tested on the pilot site, saw the fix was working and proceeded to rebuild for Release.
Everything seemed great except the web-app DLL with the fix in that was used for the release build was not the latest version even though the pilot build had used the latest version. I had to recheck in the DLL to get it to use the updated version!
Is this behaviour 'by design' - it seems peculiar you would have to re-check in to change the build if all you are doing is swapping some settings? You are fixed - all you are doing is building for a different configuration or am I misunderstanding?
mmacneill123 (MCP)

Hi Mmacneill123,
Thanks for your reply.
You said that “the issue is that I have already checked in the changes…”, and you said “if I check in before
EVERY build, everything works fine!” too.
You’re using the default build process template in your build definition? You configured these 3 configurations in your build definition to build your solution 3 times?
If you remove that DebugForLive configuration, only configure Debug and Release in your solution and build definition to perform build, everything will works fine?
After you changed the configuration from “DebugForLive” to Release, please check in on your solution first, then queue build definition to build your solution. After you changed the configuration each time, please check-in on your solution first,
then perform build.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

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.

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?

How to Setup Flash Builder ActionScript only project for iPad?

Hello!
Can someone give a short guide on how to setup an ActionScript only prject in flash builder such that it can be compiled using adt and deployed to the iPad?
i created successfully iphone games using FlashIDE and PFI.
now I'd like to create an iPad app using Flash Builder (ActionScript only). but I fail to load the compiled IPA to the ipad, keep getting different errormessages thus i think something with my projectsetup is wrong

Yes, in Terminal you type a single line which is made from the path to the adt application, some parameters, and paths to other documents. Here's the full list of things:
/Location/to/AdobeAIRSDK_2.6/bin/adt
-package
-target ipa-test
-provisioning-profile /Location/to/Provision.mobileprovision
-storetype pkcs12
-keystore /Location/to/Certificates.p12
-storepass password
NameOfApp.ipa ApplicationDescriptor-app.xml
-C /Location/to/swf NameOfApp.swf
splashscreens
icons
That "-C" line is clever, it does a directory change to the folder you give it, so after the -C /location/to/swf part it will then look in that same folder for other documents, and for where to build the IPA file.

Check in ActionScript if compiled for release-build

Similar Messages

Maybe you are looking for