Flash builder 4.7 AIR 17 compile-abc-64 fail on x32 OS

Ls,
Since AIR 16 I cant compile to iOs on my x32 Os (windows vista ultimate)
On my laptop its fine, uses x64 windows 7.
Failure because of compile-bc-64.exe not working on x32 (makes sense sure)
So: Is there a way to not have it use the -64.exe but only the normal compile-abc.exe?
Flash builder: 4.7
AIR sdk: latest two 16. & 17
OS: windows Vista ultimate x32
Highest regards,
Mac

I finally found what probelem i have. Visual studio has corrupted one dll. Flahs is crashing due to my browser in 64bits which has problem. I found that it could be a probleme while installing a .net framework. But unfortunately i can't delete or uninstall this framework, i had no option to uninstall it. I guess the best way is to format my computer. But as i am waiting for a new worksatation dedicated to your tool and zbrush of course(for stage3d is a real improvment), i won't format it now it would take too much time to resintall everything and i would have to do this again when i will received my workstation
If someone has problem like that there might be a solution(not the best but at least it works)
To solve my problem as i have to make an app in flash builder. I downloaded the 32 bits version of flash builder 4.7. And i will resintall the 64 bits as soon as i received my workstation.

Similar Messages

  • Flash builder 4.7 air 3.6 new adt compiler

    Hi. Ive been having serious issues when i tried to "Export release build" using air 3.4 and/or air 3.5 on Flash builder 4.7. Goit a lot of nonsense java.lan.nullpinter exceptions and similar errrors.
    When i tried to debug or run, even on device generating the ipa, everything ok. But when i tried to export the project, and it tried to re-compile it, always got absurd java errors.
    Ive tried everything: downgrade the java virtual machine, reinstalling flash builder, air, even windows!!! Nothing worked. Even recovering previous stages of the project where I originally could export it (its even published on the appstore!). No use. The app that was working no problem, now when trying to export returns a lot of javanull pointers or similar crap.
    BUT, when trying to generate the ipa through via command lines  on the ms dos console it works!! So... its obvious the problem was on the adl+java duo.
    Thing is, I updated to the just released AIR 3.6 (not the beta, the release version). It uses .exes(on windows, which is the system im using)  instead of java, so it showed promise.
    I overlayed the air version on the flash builder following this instructions:
    http://forums.adobe.com/message/4797974
    Well, not exaclty, because then flash builder throws a lot of errors and dosent show me the package explorer for instance.
    I made a copy of the AIR folder, but not deleted the content, just copied the new air version files over and substitute the replicas, but kept the originals where no new file substituted them (dont know if im explaining it ok, sorry for my english).
    It worked... except for the damn "Export release build" option. It keeps trying to debug it using java instead of using the new adt. And I cant find how to change that.
    The adt on the other hand is being used ok, as i can check it when I try to run or debug the project targetting a device. Before I could check the command used and now Im not, so Im pretty sure its using the new .exe instead of the java version. But now I dont know how to generate the ipa targetting the app store, for instance via command line using the new adt nor can i do it exporting the project from the flash builder IDE.
    SO...
    is there anyone having similar problems?
    How can I correctly overlay air 3.6 over Flash Builder 4.7 and force it to use the new air adt and adl?
    Anyone tried?
    Thanks in advance folks!!!

    Thanks everyone for your collaboration.
    Hey Nabren, What do you mean by "as well"?
    Just to make it clear. I already followed the instructions here:
    http://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder. html
    to overlay the air sdk. And the folder you are pointing me is the ONLY ONE the instructions tell me to replace. BUT when you say "as well" I understand something else have to be done.
    Ill explain the whole process Ive followed and the consequences:
    As I said I replaced the content on the AIRSDK placed in the fodler C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722 (or similar), for the content of the new SDK.
    The result is that flash builder throws me a lot of errors and is unable  to show even the package explorer, for instance or create a mobile project, so I went back to the original AIR folder. No problem there.
    When I was using flash builder 4.6 I overlayed the sdks in this way: made a copy of the last flex SDK (which already had the air sdk inside), and copied the content of the  latest AIR SDK over the current sdk, replacing only new files, keeping those not includded on the air sdk. That way I could keep several flex+air sdks, and could select wich sdk to use for each library/project. Now this doesnt work anymor on flahs builder 4.7.
    So I tried this:
    I made a copy of the AIR sdk under C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722 and copied over the new sdk ont he folder overwritting new files,keeping those not included on the new sdk... and this works! Everythings fine. I can debug complex projects on air simulator even launch it on an iphone or ipad...
    BUT it keeps throwing me JAVA errors (null pointer exceptions and things like that) when exporting that makes no sense at all (different errrors without making any change, now no error now another one...).
    More info on the projects provoking this behaviour:
    They are mobile projects (ios mainly). They use several libraries. Some of them come from compiled swcs from flash cs6 (wich contains classes we are using as views). All libraries have been double checked. They are fine. The problems emerge when trying to export targetting the apple store. Weve double checked the provisioning and the certificate. They are correct. In fact, when we try to generate the ipa using adt via command lines on ms-dos it works!
    Weve tried to remake and the rebuild the project class by class, even recreate the flas we are using to generate the swcs to be used as libraries on the project... it only works when the project is almost empty. As soon as some content is added.. bumm! Java errrors all over when trying to export.
    Our main machine is an i7 2.93 Ghz, 8 GB ram, 64 bits. Windows 7 Ultimate 64 bits, using Flash builder 4.7 64 bits and flash cs6 64 bits. But we have checked on other mahines and sme thing happens.
    Doesnt anyone else have these problems? Is there any other way to overlay the air sdk?
    Thanks again.

  • Are Flash Professional Buttons broken in Flash Builder 4.7/AIR 3.4?

    Moved my ActionScript Mobile Project game from Flash Builder 4.6 / AIR 3.2 yesterday to the new release of 4.7 / AIR 3.4. I immediately ran into a problem with Flash Professional Button's working incorrectly. The buttons have linkages in a SWC exported from Flash Professional CS6, which the project has linked. The content of the buttons doesn't seem to matter. It seems to break in different ways visually depending on it's composition (sometimes it loads unreleated bitmap data or displays with a strange transformation). Has anyone else seen this behaviour so far?

    I don't have the time to create a unique project for adobe bug database. So many are having the same issue, I'm shocked that Adobe doesn't know about this already. This discussion that I'm writing in right now was started in december, almost 7 months ago.
    Joseph Labrecque says in his blog that adobe does know of this issue and is working on it, he said that 6 months ago. Is he incorrect?
    Joseph LabrecqueJanuary 4, 2013 at 6:21 pmGood news that Adobe is actively working on a fix for this issue.
    http://inflagrantedelicto.memoryspiral.com/2012/12/flash-builder-4-7-useflashsdk/

  • SWC PNG's invisible when compression is set to JPEG in Flash Builder 4.7/AIR 3.4

    Moved my ActionScript Mobile Project game from Flash Builder 4.6 / AIR 3.2 yesterday to the new release of 4.7 / AIR 3.4. One side effect was that when my PNG's in my assets SWC were set to use JPEG compression instead of PNG, they are invisible at runtime. I haven't found any mention of this when searching so far. I can just use PNG compression for now, but it's nice to have the choice. Anyone else run into this problem?

    I haven't seen this come up, however you might want to give our latest AIR 3.5 build a try (12/11/2012 - AIR 3.5 Runtime and SDK Update).  If it still occurs, could you please open a new bug report on this over at bugbase.adobe.com?  Please post back with the URL so that others affected can add their comments and votes.

  • Flash Builder and Adobe AIR: anybody there?

    Hi,
    I've recently posted quite a few posts reporting very serious bugs of both Flash Builder 4.6 and Adobe AIR especially on mobile platforms, and asking about possible fixes and workarounds.
    I would have expected immediate replies by someone at Adobe showing some interest in such blocker bugs that render Flash Builder completely useless, and developing AIR apps for mobile impossible. But there was no reply at all.
    I wonder, are Flash Builder and Adobe AIR being maintained, or have they been abandoned? Because in the latter case I'd rather know it and stop wasting my time using this platform for development.
    thanks
    m.

    I feel your preoccupations, Matteo. I have them too.
    A few days ago, Gartner issued a document, called - as usual for Gartner - "magic quadrant", related to Mobile App Develpment 2012.
    This document explains the situation of the different vendors so one can make an educated choice about the IDE to use for platform-independent mobile things.
    Adobe is well-positioned in this quadrant. However, Gartner (who have talks with vendors before issueing their reports) only referred to PhoneGap when explaining how Adobe addresses mobile app development.
    This is a shame, because FB is powerful and uses ActionScript (which many of us like).
    I have bought FB last year and had fun with it. I don't think it's going to last for long, if I Adobe doesn't show that HTML5 + CSS aren't the only way to go.

  • Flash Builder 4.5 + AIR 3.0 RC1 does not output modules to correct location

    Hello
    I'm having some trouble with Flash Builder 4.5 and Flex SDK 4.5.1.21328 with AIR 3.0 RC1. Flash Builder does not appear to compile modules into the location set in the "Edit module" dialog.
    The screenshots below show that the output path of a module is set to a specific folder, yet Flash Builder compiles the module into the default sub-folder.
    #1. Project properties showing application modules
    #2. Dialog showing the path to the module. Not the "Output SWF" location. The default location is the same as the package namespaces, eg: "d6/v3/banners/Banners.swf". After removing the path the module should compile into the output folder (set to bin/debug), however as the next screenshot shows, the module still compiles into the default sub-folder.
    #3. The module is compiled into a sub-folder of the output folder, instead of into the "root" of the output folder.
    #4. The output folder contains only the main application, with a sub-folder for the module.
    #5. Project pproperties showing the output folder.
    There is a workaround - move the module source file into the "Default package" in the package explorer.

    I experienced this problem today, and kind of "solved" it. There may be an underlying bug, though.
    My project compiled fine last Thursday, but I opened it up on Monday (unchanged) and this error showed up in several files. I tried quitting and restarting Flash Builder to no avail. I could not replicate the problem in a new project.
    For me, each occurence of the error was at a private function definition, so I thought I would try changing "private" to "public" on one of the functions. The error immediately went away in all 3 locations (not just the one I edited). I then changed it back to "private" with no error.
    I hope that will help the Adobe team track down the problem.

  • Developing Iphone App using Flash Builder and Flex Air Mobile

    I started developing an Iphone app using the trial version of Flash Builder and was pretty impressed with how easy it was, then i hit problems:
    Trying to submit my app, I was getting invalid binary, using google i tracked this down to a change in the Apple App Store meaning that all apps needed to have native iphone 5 support, which meant updating to Air SDK 3.7
    Updating to AIR SDK 3.7 was a nightmare (mainly as a result of my failure to read the small print)
    Once I got SDK 3.7 to  work with flash builder / flex mobile i though i was there.
    However now i can produce a fast build but everytime i try and produce a standard / production build i get strange errors (air 3.8 does the same).
    My Question is - before i actually buy Flash Builder has anybody actually achieved the following:
         Building an Iphone App using:
         Flash Builder 4.7    (running on OSX)
         Flex Mobile 4.6
         Air 3.7
    If so how ?
    cheers
    Toby

    Thanks for your reply, its nice to know its not just me.
    the error i got when submitting to the App store where due to native support for IPHONE 5 which is now mandatory (from May 1st), looking around the internet the common soloution seemed to be upgrading to Air 3.7.
    The strange erorrs on 3.7 revolve around compiling a standard / production build (fast build works fine)
    the error is always the same (snippet shown below):
    Error occurred while packaging the application:
    Undefined symbols for architecture armv7:
      "__ZN7avmplus8Debugger9debugLineEi", referenced from:
          __ZN7avmplus9MethodEnv9debugExitEPNS_13CallStackNodeE in AOTBuildOutput-4.o
          __ZN7avmplus11BaseExecMgr22debugEnterExitWrapperNEPNS_9MethodEnvEiPj in AOTBuildOutput-4.o
    I have completly failed to work out why, but my gut feeling is its something to do with how the mac is compiling the code in standard build and unable to find a library it needs.
    cheers
    Toby

  • Flash Builder 4.7 AIR Release Build certificate problem

    I can´t export a Release Build of an AIR application in Flash Builder 4.7. In the Packaging Settings screen forms and buttons to browse for and create certificate are missing. There is just the notification that No certificate selected and Back and Cancel buttons. In Flash Builder 4.6 everything iworks allright. Can somebody help me?

    Moving this discussion to the Using Flash Builder forum.

  • Flash Builder 4.7 conditional compiling failed

    I installed Flash Builder 4.7 on my windows xp machine, and tried to migrate projects from FB 4.6. However in one of my projects I use conditional compiling, but I'm getting errors.For example in FB 4.6 I have this sample code:
    public class MyClass{
         CONFIG::DEBUGGING{
              import com.package.SomeClassOnlyForDebugging
         function someFunction():void{
              if (CONFIG::DEBUGGING){
                   SomeClassOnlyForDebugging.create();
    When I compiled it in FB 4.6 everything worked fine. However when I try to compile it in FB 4.7, then I get error on the conditional compiling only inside the function and not on the import statement. The only way I have found to overpass it is to go to Project>Properties>ActionScript Compiler and disable Enable strict type checking. But this is not a permanent solution.
    Am I doing something wrong, or is there some other way to do it?

    You should to do like that:
    function someFunction():void
    CONFIG::DEBUGGING {
         SomeClassOnlyForDebugging.create();
    without if.

  • Flash Builder 4.7 frequent compiler issues/restarts

    Basically Flash Builder 4.7 on Mac OSX 10.7.5 is unusable. Very frustrating.  Constant compiler issues that require frequent cleaning, closing of projects, restarts of FB, and even re-installs.  I've seen none of these issues on FB 4.6 with the same projects/code.
    The most common visible compiler errors are these two that randomly appear:
    1) An internal build error has occurred
    2) classes must not be nested
    I tried increasing memory as some have suggested, but this has no effect.
    It takes me 100 times longer to code now becuase every tiny code change cuases these errors.  Crazy!
    Before I revert back to FB 4.6, any suggestions? 
    Thanks,
    Don

    Hi!
    Close any unneeded projects in workspace.
    You can also split your large project to few libraries compiled into SWC. After compiling libraries, if not need to change often, close their projects. When such projects are closed main project compiling with just use of SWC libraries usually takes much less resources.

  • Flash Builder 4.7 - AIR SDK 3.1: Directory does not contain a AIR SDK

    Im still having issues with using AIR 3.1 with flash builder 4.7 (see my previous posts) and would appreciate any help/ advice.
    Ive uninstalled FB 4.7, reinstalled and followed the procedure to overlay AIR 3.1. Im now getting the following error -
    AIR SDK 3.1: Directory does not contain a AIR SDK
    Reason for using AIR 3.1 is that all of my projects are built with AIR 3.1 and no longer work with FB 4.7.

    Can anyone from adobe help with this please?

  • Flash Builder and Adobe AIR update framework

    Hi,
    I posted this in AIR forum , but thought it happens with new flash builder and flex 4 beta , i should do here also
    When I run the Air update framework with the new flash builder , i get this exception when I call appUpdater.initialize() in the same given in http://www.adobe.com/cfusion/communityengine/index.cfm?event=showdetails&product Id=4&postId=9543
    The error is
    TypeError: Error #1007: Instantiation attempted on a non-constructor.
        at mx.controls::ProgressBar/createChildren()
        at mx.core::UIComponent/initialize()[E:\dev\beta1\frameworks\projects\framework\sr c\mx\core\UIComponent.as:6510]
        at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\UIComponent.as:6402]
        at mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\Container.as:3879]
        at mx.core::Container/addChildAt()[E:\dev\beta1\frameworks\projects\framework\src\ mx\core\Container.as:2541]
        at mx.core::Container/addChild()[E:\dev\beta1\frameworks\projects\framework\src\mx \core\Container.as:2459]
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_ApplicationUpdaterVBox10_c ()
        at mx.core::DeferredInstanceFromFunction/getInstance()[E:\dev\beta1\frameworks\pro jects\framework\src\mx\core\DeferredInstanceFromFunction.as:105]
        at mx.states::AddChild/createInstance()
        at mx.states::AddChild/set targetFactory()
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_AddChild8_i()
        at ApplicationUpdaterDialogs/_ApplicationUpdaterDialogs_State7_c()
        at ApplicationUpdaterDialogs()
        at _ApplicationUpdaterDialogs_mx_managers_SystemManager/create()
        at mx.managers::SystemManager/initializeTopLevelWindow()[E:\dev\beta1\frameworks\p rojects\framework\src\mx\managers\SystemManager.as:3581]
        at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::docFrameHandler()[E:\dev\beta1\frameworks\projects\framework\src\mx\managers\SystemManager.as:3 400]
        at mx.managers::SystemManager/docFrameListener()[E:\dev\beta1\frameworks\projects\ framework\src\mx\managers\SystemManager.as:3258]
    The code is the exact same given in the updater example i mentioned in the link above. Only difference is i am using spark framework. The appUpater.initialize() never seem to work and keeps throwing an exception. Any alternatives so suggestions ?
     This works fine in my Flex Builder 3. 
    Thanks
    Hironmay Basu

    the issue is already reported here:
    http://bugs.adobe.com/jira/browse/SDK-22886?page=com.atlassian.jira.plugin.system.issuetab panels:all-tabpanel
    As a workaround, you can try using:
    http://www.websector.de/blog/2009/09/09/custom-applicationupdaterui-for-using-air-updater- framework-in-flex-4/

  • Launch Failed !ApolloLaunchDelegate.fileDoesNotExist! in Flash Builder when debugging AIR apps

    Hi Everyone,
    I've been using flash/flex builder for years, but have never tried to create an AIR application before.  I tried to create a 'hello' world app before porting some of my stuff over by following the instructions here:
    http://help.adobe.com/en_US/AIR/1.5/devappsflex/WS5b3ccc516d4fbf351e63e3d118676a28bd-8000. html
    but when I try to debug the code I get the a 'Launch Failed' dialog with the unhelpful comment '!ApolloLaunchDelegate.fileDoesNotExist!'.
    I'm running win7x64, SDK 4.1
    I've tried all sorts of different AIR files, including the default when you just create an empty project, and converting copies of some of my existing flex projects to desktop, but they all give the same message.
    Google doesn't help.  Any ideas would be gratefully recieved.
    kenneth
    EDIT: just tried the same thing on my same version of flash builder on my laptop and it works... The laptop runs Vistax64.  The only other different is that when I selected SDK 4.1 in the new project dialog it said it needed AIR 2.0, whereas on this machine is said it needed AIR 1.5
    Message was edited by: kennethGilpin

    Hi Anirudh,
    Thank you for your reply.
    My flash builder says that it is version 4.0 (build 272416).  When I checked for updates it said my program was up to date.
    There is a copy of the *-app.xml and .swf in the bin-debug folder
    There are no errors reported in the 'problems' view.
    kenneth
    EDIT: just checked the version on my laptop, says version 4.0.1 (build 277662)
    EDIT: I manually upgraded to version 4.0.1 and this fixed the problem.

  • Flash builder 3 won't compile

    I have a flash builder 3 project  but I done something but it won't compile now. How can I resolve this. Tried clean project and no luck

    what are the compile errors u r getting ?

  • Built app with Flash Builder 4.6 and compiled for iOS, now error when loading to appstore

    I built a fairly simple app using Flash Builder 4.6 and have successfully deployed it to the Android Market (after testing on my own Android device).  I have also taken that same app and compiled it for iOS and tested it on my own iPad. 
    I have then done the release build with the "Final Release for App Store Distribution" option in the release build wizard.  I have all the correct provisioning certificates in place and compiled the application to a .ipa file.
    At this point, using a MAC, I have run the Application Loader utility to upload my application to the itunesConnect portal to get it in the appstore.  I've already gone through the steps of entering the metadata, price scheme, and screenshots in the itunes connect portal, and just need to upload it for review.
    When I upload the .ipa file into the application loader, it gives me the following error:
    "iPhone/iPod Touch:  application executable contains unsupported architecture(s): arm"
    Anyone have any idea what this means and how I can fix it?  Any help is greatly appreciated!
    Thanks in advance!

    Solved it.  Just added the following in the <InfoAdditions> tag for iPhone in my app descriptor XML file:
      <key>UIRequiredDeviceCapabilities</key>
    <array>
    <string>wifi</string>
    <string>armv6</string>
    <string>armv7</string>
    </array>

Maybe you are looking for