Adobe AIR 2.0 Major Bug

Hello,
We have an application built in Adobe AIR (HTML and Javascript Based).
It's been running for 14 months now with no problems.
Adobe came out with the AIR 2.0 version, and because the updates are pushed automaticaly to the clients, we started to suffer from major pages render issues.
The app is written in Hebrew. and now with version 2.0 we get every few paragraphs, in the middle of the paragraph a question mark or two instead of the letters, and sometimes it just drops letters.
This happens randomly and I can't put a rule on this.
Because Adobe pushes this upgrade, a lot of our customers updated to this buggy version.
This is a major issue. I wish to know if you know something about it or atleast tell me how can I easily revert this version back to AIR1.5.3 on the clients.
This software is in our main structure of the company. Adobe should not release new upgrades that are automatically updates on the client side. this is something that we, the developers, should push to our clients (after checking for bugs).
We spent a lot of hours and money to develop our app, what should we do now?
I wish to know how can I contact someone from the Adobe AIR team, and get this issue resolved ASAP.
Thanks,
Uri

Uri,
First, I am sorry to hear that your application was impacted. Whenever possible, we release public betas so that customers can report back issues related to backwards compatibility. In the case of AIR 2, we released two public betas.
However, per the Adobe AIR system requirements page, Hebrew is not a supported language. While it is possible that your application was working in an earlier version (AIR 1.5.3), it was still not a supported platform at that time.
I would encourage you to submit a bug using our feedback form and we'll take a look. However, to set expectations, we always prioritize supported systems over unsupported systems.
Feedback form (please provide all information necessary to reproduce the issue):
http://www.adobe.com/go/wish/
-Rob
Product Manager, Adobe AIR

Similar Messages

  • I0S7 StatusBar Overlays stage, Adobe Air 3.9 Beta Bug VOTE this Bug

    Hi
    I am using Adobe air 3.9 Beta. It seems that iOS7 give you the the possibility to style the Statusbar. But if you open an adobe air application the statusbar overlays the stage by default. It creates problems with my tabs.
    I tested the app with an iPod and IPhone, both with iOs7 Both have the Issues. If I compile the app with Adobe air 3.8 the Statusbar will be displayed correct.
    But I can't use air 3.8 because I need the new Icons 120x120 76x76 etc.
    Other people have the same issue. See screenshots https://github.com/mutualmobile/MMDrawerController/issues/51
    I think the solution is in the info.plist. There is an option for the info.plist UIViewControllerBasedStatusBarAppearance. We need this paramter to activate or deactivate the Statusbar overlay.
    Please vote to fix this bug
    https://bugbase.adobe.com/index.cfm?event=bug&id=3633422
    any Ideas for an workarround?
    p.s.
    sorry for double post in Air Development section

    Hi,
    up until now, I think this might be a general issue, even Xcode (5) apps have this.
    However, if you just need the new icons you shouldn't care too much about this, you nearly can't see the differences when you adjust your icons a little bit (no border on the edges etc.), so I would rather use 3.8 (fast, since you might not be able to upload an app without the icons after tomorrow) and update it once those issues have been fixed (I think that this might need a while, since there are some more problems with 3.9).

  • I0S7 StatusBar Overlays stage, Adobe Air 3.9 Beta Bug? Is there a Workarround

    Hi
    I am using Adobe air 3.9 Beta. It seems that iOS7 give you the the possibility to style the Statusbar. But if you open an adobe air application the statusbar overlays the stage by default. It creates problems with my tabs.
    I tested the app with an iPod and IPhone, both with iOs7 Both have the Issues. If I compile the app with Adobe air 3.8 the Statusbar will be displayed correct.
    But I can't use air 3.8 because I need the new Icons 120x120 76x76 etc.
    Other people have the same issue. See screenshots https://github.com/mutualmobile/MMDrawerController/issues/51
    I think the solution is in the info.plist. There is an option for the info.plist UIViewControllerBasedStatusBarAppearance. We need this paramter to activate or deactivate the Statusbar overlay.
    any Ideas?

    My variation of the problem shows different results in 790 and 1080. Here's what I'm doing, and what's different:
    When I ask the user to pick a photo from their album, the status bar appears (my app is full screen, and no status bar is showing at first).
    With build 790, the status bar is opaque, black background, and it sits on top of the title banner of the picker (the word "PHOTOS" gets obscured). When I return to the app, the status bar remains there, and is sitting on top of my stage content. The picker is iOS 6 styled.
    With build 1080 the behavior is identical to the above, except that the status bar is transparent, and the picker is iOS 7 styled. The status bar does not obscure the "Photos" word, that is further down the screen. On returning to the app I see the black text of the status bar sat transparent on top of the top part of my stage content.
    If I build for 3.8.0.910, the behavior is the same as it is for 3.9.0.790.
    This is with the GM version of iOS 7.
    Overall, I think I'll build for 1080, and hope the client doens't notice the remnants of the status bar. Hopefully you will have added the new icons to the next iOS 7 AIR build, and found a way to hide the status bar after showing the picker.

  • Adobe Content Viewer - Potential major bug

    I saw that the new Adobe Content Viewer was just approved by Apple, and updated the app on my iPad 3. When I opened the app and downloaded a folio (folio made using r23), none of my Vector MSO's showed up as vector, they're all still raster. I repeated the process on another iPad 3 and had the same results. It seems like the r24 Content Viewer won't show vector MSO's. Anyone else having the same problem?

    Here are three screenshots. 1 - normal viewing, 2 - first zoom, then I zoomed out, then 3 - second zoom

  • AIR - Major Bug (?) with MovieClip class

    Hello all,
    We are a team of developers working on ActionScript 3.0 project using Adobe AIR SDK and Adobe Flex SDK.  During the development we discovered what seems to be a major problem with getting MovieClip instances to play correctly. More specifically,  the problem has to do with the gotoAndStop method. If, using the gotoAndStop method, you perform a for loop over all MovieClip frames (from the 1st frame to the last one) and go back to the 1st frame again, then, after adding MovieClip to the Stage, the 1st frame won't be set, contrary to what's expected. Instead, the MovieClip selects the last frame, which messes things up.  Are there any solutions to the described problem, other than switching to the right frame after the object has been added to Stage?
    This seems like a 'no way out' situation - any help would be much appreciated.
    A note: MovieClip itself is being imported from the 'swc' file.

    Thanks for the heads up and I'm sorry you guys have run into this issue.  Is this is new to AIR 3.x?
    Could you please open a new bug report on this over at bugbase.adobe.com, including a brief description and sample code/app to help us easily reproduce the problem.  Please post back with the URL so that others affected can add their comments and votes.
    Thanks,
    Chris

  • Home view major bug: Home view navigation not available in Common File Dialog Box (i.e. Java, Adobe Photoshop etc)

    Homeview major bug: Homeview navigation not available in Common File Dialog Box (i.e. Java, Adobe Photoshop etc)
    Hi
    All though provisioning somewhat more flexsible and pointing forward ... things are starting to go wrong here ... i.e. pointing to a very potential lack of success introducing users to the new Home namespace/concept ...
    0) Situation if you do not fix 1 + 2:
    You can not release the Homeview feature like this - without fixing 1 + 2.
    If not 1 +2 is fixed you might just as well leave the release of the Homeview feature out of the roadmap for Windows 10. I.e. not ready for use ... or promotion in the UI
    1) How come Homeview has not been included - like other namespaces i.e. Libraries into the Common File Dialog Box?
    How can such a trivial thing to do be missed? I.e. like forgetting to include Homeview into Explorer (would be absurd).
    If not included into the Places Bar of the Common File Dialog Box ... Home View will be unusable - because some very visible applications like Java, Photoshop will not be able to navigate that space easily at all.
    2) Finally, please fix obscure situation in the UI namespace in Explorer
    Please fix obscures like having Home view, Favorites and Libraries (side-by-side complexity and confusion obscuring usability) - all similar concepts but on a different evolutionary step. I.e. have Favorites and Libraries
    hidden - and add i.e. view control like to small buttons whatever to unhide/show the legacy concepts.
    In any case - Home view already seem to migrate/move links from Favorites to the Homeview container.
    Additionally, Home view should migrate links from Libraries to Home view - and provide similar and better functionality.
    Thus going the evolutionary way from Libraries > Favorites > Home - with the later concept of Home providing links to the cloud. Even better, sync relation ships could then later (extended features for Home) be set up among the pins - i.e. concerning
    cloud/network syncing.
    The UI should always reflect the 1 essentional concept - and not under the hood technologies or different evolutionary stages of the same basic/essential concept (technology/implementation free - abstract: "Home with pining of user data space"
    - was previously favorites or libraries (thus obsoleted)). Now the name for that concept is Home. Have it include the technology that replaces Libraries too - i.e. categorization/nesting ... and some whitespace inbetween the nesting (alike some whitespace
    already there inbetween the namespaces in the Explorer UI ... provides easy "modular" reading)

    Hi,
    Please clarify the following:
    * "X: is a network drive, but it's actually a network drive on my machine." - Is "X" a mapped drive to one of your shared folder on network?
    * What is the project directory structure with respect to WEB-INF/web.xml? Are you able to see the three pages (from web & pages folder) in NitroX Editor?
    * Does the modified content appear in "Design view" of index.jsp upon restarting NitroX?
    Ex:
    - modify one of the pages in "web" folder > save the file (alert appears)
    - restart NitroX, does index.jsp display the modified content of included page?
    * If possible please send the test case project which exhibits the behavior to [email protected]
    Thanks,
    M7 Support

  • I have a major problems with adobe air.

    i have a major problems with adobe air. day before yeasterday it work. now it tell me that it is musconfigure. so i have tried a download it again. but still not working.

    You really need to explain what you are doing, and what your "major problems" are.  We do not even know if you mean the AIR runtime, or AIR SDK?  Nor your operating system.

  • Adobe AIR Team - please stop trolling us and start fixing critical bugs.

    Hi there,
    i didn't intend to get offensive at anyone, but you at adobe give us, the developers and therefore your customers, not any choice.
    Please see these critical bugs which are filed almost 2 years ago:
    https://bugbase.adobe.com/index.cfm?event=bug&id=3496074
    https://bugbase.adobe.com/index.cfm?event=bug&id=3077653
    It is one example where you making us the fools and behave like a troll by telling us a "workaround" and close the ticket. Again.
    Giving us a workaround which affects the overall app experience and freezes the UI is not a solution to this problem. Why do you not care about stuff like that? File Operations are one of the most recent showstoppers to me in doing Adobe AIR Applications for iOS and you give me no chance but to search an alternate development platform. And I am not the only developer who is thinking like that.
    Please be more developer friendly and try to fix as many bugs as you can before thinking about new features which aren't really important to us.

    Hey , it's  adobe ..OK.  It's very very very  normal . Just  waiting ,just be  patient , we will fix it  several years  later ,because we have more bugs important than it.
    OK ,let me tell you  another funny thing.
    Refer to this article :  http://help.adobe.com/en_US/air/extensions/air_extensions.pdf  , Adobe  said in  page 49
    Resources on Android devices
    For the Android-ARM platform, put the resources in a subdirectory called res,relative to the directory containing the
    native code library. Populate the directory with resources as described at Providing Resources on
    developer.android.com. When ADT packages the ANE file, it puts the resources in the Android-ARM/res directory
    of the resulting ANE package.
    When accessing a resource from the extension’s Java native code library, use the getResourceID() method in the
    FREContext class. Do not access the resources using the standard Android resource ID mechanism. For more
    information on the getResourceID() method, see “Method details” on page 125.
    The method getResourceId() takes a String parameter that is the resource name. To avoid resource name conflicts
    between extensions in an application, provide a unique name for each resource file in an extension. For example, prefix
    the resource name with the extension ID, creating a resource name such as
    com.sample.ext.MyExtension.myImage1.png.
    SO ..I follow they says to do.  OK ,i got an  ANE  successfull .  Then  ,i  Add the  ANE into my mobile project . And Click  "release"  button(or  debug ).
    THat  is the  funny  thing .I actually got an error message:
    java.lang.Exception:
    aapt tool failed:invalid resource directory name: D:\LocalProfile\Localtemp\8d438362-8178-429a-858f-715c1e176235\res/values-sw600dp
    invalid resource directory name: D:\LocalProfile\Localtemp\8d438362-8178-429a-858f-715c1e176235\res/values-sw720dp-land
              at com.adobe.flexide.multiplatform.android.launching.ADBLaunchHandler.doPackage(ADBLaunchHan dler.java:454)
              at com.adobe.flexide.multiplatform.android.launching.ADBLaunchHandler.launch(ADBLaunchHandle r.java:350)
    I've test it on windows 7 32bit + FB4.7+AIR3.7 SDK ,and i  also asked my  friend test it  on  Mac OS + FB4.7+3.6SDK  ....cann't package APK too. but error message is diffrent .
    I wonder if anyone of adobe  actually fully tested what they said . But I spent a few days checking my approach. And i responsible for my words.
    I'm tired of reporting BUG.No matter what happens, i  tell myself ,"it's product by adobe".

  • Bug after updating Adobe Air to Adobe Air 2.6.0.19140

    I have an application developped in last version of Adobe Flex Builder (Flex 3 Pro) which worked very well.
    But when I have updated to the last version of Adobe Air (2.6.0.19140), the method maximize() on a window now not works. The window is small in the corner of my screen.
    Has anybody a solution ?
    Nicolas

    Hi Martin,
    Could you post your AIR installer log?
    Thanks,
    Chris

  • Adobe AIR rendering bug

    Hi all,
    I have a HTML page where I hide a form till the user click a
    button. The form have dropdown list and radiobuttons. This fuctions
    works 100% when I open the HTML in a browser. But when I render the
    HTML to an Adobe Air application, the form is hidden, except the
    radiobuttons.
    Any help will be appreciated.
    Regards,
    Chris

    As an update, I submitted a test build of the AIR app I'm working on to the Valve devs so that they could profile the Steam Overlay to see if any issues were going on there. Unfortunately, they were not able to find anything wrong on the Overlay side. It sounds like its a combination of the Overlay blocking win32 input messages and AIR's input handling. Here is the response I received this evening:
    I got your depots and did some testing.  Nothing unusual happens in the overlay.  Profiling your app with xpref while the issue occurs and taking some minidumps to check callstacks it looks like the app just blocks up completely and uses zero CPU during the time it is blocked, when it happens it calls Present() only at roughly 1 second intervals until it recovers (maybe there is a 1 second timeout somewhere in the AIR code).  It's hard to get much detail since I don't have any symbols for the AIR runtime libraries.
    It does however look like this is somehow related to input state and AIR being unhappy with win32 input messages stopping.  If I change our overlay to not block any input at all once activated (which obviously has some pretty big problems for usability, but just for testing purposes.) then the issue does not occur.  It's possible that the AIR code has some weird logic where if it's seen some specific WM_WHATVER message it's expecting another right after and blocks on it waiting somehow.
    Hopefully you can work out on your side or with Adobe as to why the application behaves badly in these situations and starts blocking and not presenting at regular intervals.
    Can any AIR devs shed light on the underlying AIR input handling on Windows? We're very close to shipping on Steam, but this is holding us up because we need the Steam overlay for payment processing. Any help would be greatly appreciated!
    Josh

  • Bug: Adobe Air Print Stylesheets

    When using Air to print an html file (already a silly process
    in of itself) it appears that Air doesn't actually use the @media
    "print" style sheet rules.
    quote:
    @media screen { .noprint {display:none;} }
    @media print { .noprint { display:block !important; padding:
    5px; border: solid 3px #0000FF; font-weight:bold;
    text-align:center; } }
    Does anyone have any word when Printing will be fixed in
    Adobe Air applications? It's really terrible as it stands now, and
    having to make hacks to display windows with alternate "screen"
    media stylesheets is just adding insult to injury.
    For now I will try to create a js/as bridge and attempt to
    use AlivePDF. If anyone has dreamed up any alternatives I'd really
    appreciate it.
    Here's some sample prints of the above test if needed:
    Sad, kinda
    gross looking, Adobe Air Print
    Happy,
    properly formatted, Firefox Print

    This was an issue with retina iPad's prior to AIR 3.5  .. I saw this fixed as of AIR 3.5.  Altho it doesnt take a retina screen capture. It captures at 1024 x 768 and scales up to 2048 x 1536

  • Kindle Fire and Adobe Air plug in + Air 2.7 + gpu + landscape + full screen

    Alright I got a couple of issues here.
    First I was on air 2.7 trying to convert an app that is designed to run in gpu mode, in landscape orientation, and full screen, well this is a known bug on 2.7 and the work arounds I found did not solve my problems or I was not clear on implementing them.
    Then I figured I go 3.1, surely that issue is fixed by now, run the app on my Kindle Fire and it tells me my air is out of date so it prompts me to go to the Amazon app store for an update except when I do it just takes me to the free app of the day page and I can't manually find the air app through the built in amazon app store, I see it on the web version but cannot download it, and if I am having this problem all the users will too so some solution like getting it off the android market and putting on the fire manually is useless.
    It seems that there is no plug in available on the amazon app store that will allow the fire to run applications built in 3.1, is this true? I've seen a few posts regarding this. And if true, why and when will this be fixed? I wasted a day with this problem when I could have been doing some design.
    Any ideas or suggestions are welcome.

    A word of caution:
    the Amazon Appstore checks for Kindle Fire support AFTER it accepts app updates.  So a developer can unknowingly break KF support, and still get app updates accepted into the store!
    Here is an e-mail I just sent to Amazon's KF team:
    FYI, there is a significant loophole in your submission pipeline:
    1) All my apps use Adobe AIR.
    2) For the longest time, they were all compiled with AIR 2.7 so there was no problem.  I got a bunch of downloads, including from Kindle Fire users.
    3) A week ago, I updated most of my apps to AIR 3.1, and broke Kindle Fire support, without my realizing it, because I didn't know that the KF only supports AIR 2.7.  Unfortunately, all the updates with broken KF support were accepted into the store!!!
    4) Now I am getting users complaining that their apps no longer work on Kindle Fire.
    What should have happened: NONE of the updates should have been accepted after it was realized by your review team that they broke Kindle Fire support, while previous versions worked fine on it and KF users downloaded them.  Reviewing KF support separately, after the initial review/acceptance, is not a good process!
    In any case, I have re-submitted all my apps with the release note 'Restored Kindle Fire support'.  What I did was use 'captive runtime' for compiling all my AIR 3.1 apps, which normally means that the app will not require an external AIR runtime to function.  Hopefully, this will work this time.  If not, I am going to have to re-compile everything using AIR 2.7, which is a major drag since some of the features I depended on are part of AIR 3.1.

  • Adobe AIR Runtime Redistribution and Native Installer

    Will there be new instructions for Adobe AIR 2.0 Runtime Redistribution? In particular, I'm looking for instructions on how to use the runtime redistribution installer to perform a "side-car installation" of AIR 2 alongside an application that uses the NativeProcess API (and so must be built into a native installer instead of a .air file).
    Thanks!

    Thirded!
    On a test deployment using SCCM and the supplied Adobe AIR Runtime Installer files, we have managed to install our application with the 1.5.3 Air Framework with no major issues other than having to disable the Auto Update feature that doesnt really work in a corporate environment.  Everything was absolutely fine until the release of AIR 2.  Now, the test machines are prompted to install the updated Adobe Air 2 framework once a week, see an excerpt from an Adobe blog post below:
    "In addition, once a week AIR apps check to see if an AIR update is available, and if so, users are presented with the option to update to the most up‐to‐date version, helping to ensure that end users get the benefits of improved security and performance."
    That sounds great right?  Except my users (like many other corporate users) don't have Admin permissions on their machines (hence the use of SCCM), with the result being resultant error messages when a user attemptes to install the AIR framework update without the necessary permissions.
    All of the above would be fine if the Adobe AIR Runtime Installer files were updated to include the latest version of the runtime.  This of course hasn't been done yet - does anyone know when this may happen?  Can anyone help me with this or offer any advice?
    I hope the above makes sense and I would really appreciate any help or advice!
    Thanks!

  • Adobe AIR runtime update dialog breaks application

    I'm working on a large project that utilizes a C++ application to house the core logic and an AIR application to display a UI. The C++ program launches the AIR UI and passes it several command line parameters, including locale and port number to call back to the C++ application with.  Under normal circumstances, this works great.
    However, when there's an Adobe AIR runtime update, things go bad.  The runtime intercepts the UI invocation, kills it, and displays the generic AIR "do you want to update?" dialog.  Whether the user presses update or cancel, the UI application eventually gets relaunched -- but without the command line parameters originally passed to it!  I presume this is a bug in the Adobe AIR runtime updater code.
    The end result of this is that the UI gets relaunched, but doesn't know how to localize itself or what port to call back to the C++ application with!  If the user relaunches, it works fine (because the update dialog won't intercept again), but by then the user experience has already been mangled.  We can't even display a localized error message to tell them to relaunch because we don't know what locale they're using any more, and we can't call back to the C++ application to ask.
    I'm trying to find solutions/workarounds to this issue.  Because AIR won't let us turn off the update check on a per-application basis, it seems like the only viable solution would be to turn off the runtime update check for the whole machine.  But altering machines settings for the benefit of one application is definitely bad form, and I'd prefer not to do that if any other viable workaround exist.
    Any ideas?

    I filed a bug report last night using that same form.
    The duplication steps are straightforward.  I can duplicate the following with 100% success on a freshly imaged Win 7 32-bit box, admin user account:
    1) Install older version of Adobe AIR framework (I tried both 1.1 and 1.5.1).  It will ask you to update.  Click "Update later".
    2) Pull up task manager and watch the process list
    3) Run ANY Adobe AIR app with some parameters (I used Adobe's Settings Manager as a sample because it's small)
    4) Note that your application appears in the task manager briefly
    5) Your app is terminated and "Adobe Air Installer.exe" appears in the task manager.  A dialog pops up asking you to update.
    6) Click cancel
    7) Your app is reinvoked without any parameters
    As for my specific case, by "session" I do mean a single launch.
    I'm not aware of an evoke event -- perhaps you meant invoke event?  The invoke event is not executing before the app terminates (in step 5 above).  I think the AIR app is just running long enough to load the runtime and then the runtime takes over from there.
    Thanks...

  • Adobe Cloud window and adobe air not showing up or starting even though it is installed, i have tried reinstalling/uninstalling

    I downloaded muse cc 2014. It worked fine for a while (couple of bugs though). Yesterday it would crash whenever it was launched. So i tried to uninstall and re-install. No Luck. Then noticed adobe cloud/adobe air windows were not starting up as per usual on startup and i have been through pc to try to locate and start manually. No Luck with them either, so i have been trying re-download manually, i download the CC exe and try run it from c:drive but no response - not running.
    i have tried a restore and that hasnt helped. I have uninstalled all muse versions but now cant re-download it!?
    where to from here, urgent help would be appreciated. Thanks

    Link for Download & Install & Setup & Activation problems may help
    -Online Chat http://www.adobe.com/support/download-install/supportinfo/

Maybe you are looking for