Air 3.3 beta: Still relying on ANEs for hardware mute switch on iOS?

Just want to know if we will get that functionality anytime soon on the SDK

Hi again!
I'm glad to report that you will no longer need to use an ANE to enable the hardware mute switch on iOS. This functionality is now available in the Adobe AIR 3.4 beta SDK with the new Ambient AudioPlaybackMode.
You can get the Adobe AIR 3.4 beta SDK from:
http://labs.adobe.com/technologies/flashplatformruntimes/air3-4/
For more information on using Ambient AudioPlaybackMode, see
http://blogs.adobe.com/airodynamics/2012/07/17/silencing-audio-on-ios-with-ambient-audio-p layback-mode/
Hope this helps! We look forward to hearing your feedback on the feature.
Sadia Fatima,
Adobe Systems.

Similar Messages

All my technology needs are now met with my iPad Air. Do I still need a computer for syncing etc?

All my technology needs are now met with my iPad Air. Do I still need a computer?

Only you can make that decision. If you say that all of your computer needs are met, then you have answered the question yourself.
I would never rely totally on iCloud for backups. I want more control than what Apple has to offer with iCloud and I don't want to have to pay for the storage that I need as the content on my iPad continues to grow. I realize that I had to buy the computer, as well, but I can backup my iPad to iTunes, backup my iTunes library with Time Machine and backup other files with another external drive that I have connected to my MacBook Pro.
I just don't trust all of my content being in the cloud or in Aplple's servers. Just a matter of choice.

AIR 3.7 Beta: TypeError: Error #2022 occurs for an unrelated class

On AIR SDK 3.7.0.1240, the error "TypeError: Error #2022: Class (flash.text.Font-derived class) must inherit from DisplayObject to link to a symbol" occurs when instantiating an unrelated class when launched in the Flash Builder debugger.
Include an swc with a linkage built with Flash Pro and instantiate a class (ClassA) in the swc results in:
TypeError: Error #2022: ClassB must inherit from DisplayObject to link to a symbol.
at flash.display::Sprite/constructChildren()
at flash.display::Sprite()
at ClassA()
Does anyone see this? Because of this problem, I can't evaluate AIR 3.7 Beta at all.
I entered the bug here.
https://bugbase.adobe.com/index.cfm?event=bug&id=3520793

no, i try to install air app on desktop that was build month ago, and was succefully installed previously
but now, said that there is a problem, and i need to send request to this app developer (me)
problem was with certification, it was expired, generate new one, compile app, and it installed
sry for bad english

Could not resolve sparks component with Air 3.6 Beta

Description
Resource
Path
Location
Type
Could not resolve <s:SolidColor> to a component implementation.
ExpandingItemRenderer.mxml
/ProjectTest/src/renderers
line 59
Flex Problem
Could not resolve <s:State> to a component implementation.
ExpandingItemRenderer.mxml
/ProjectTest/src/renderers
line 33
Flex Problem
Could not resolve <s:State> to a component implementation.
ExpandingItemRenderer.mxml
/ProjectTest/src/renderers
line 34
Flex Problem
Could not resolve <s:Transition> to a component implementation.
ExpandingItemRenderer.mxml
/ProjectTest/src/renderers
line 38
Flex Problem
Could not resolve <s:Transition> to a component implementation.
ExpandingItemRenderer.mxml
/ProjectTest/src/renderers
line 47
Flex Problem
This is what i get with the latest Air 3.6 Beta SDK with a mobile project !
FB 4.7 shows the <mx:Transition> potential match but not the <s:Transition>. Its the same for all the other errors it shows the potential matches
Can someone provide a solution I even tried to add sparks.swc as external SWC but it doesn t work.

I Still have theses errors :
Description
Resource
Path
Location
Type
Could not resolve <s:State> to a component implementation.
MessageBox.mxml
line 129
Flex Problem
Could not resolve <s:State> to a component implementation.
MessageBox.mxml
line 130
Flex Problem
Could not resolve <s:State> to a component implementation.
MessageBox.mxml
line 131
Flex Problem
Even if I added the spark.swc
But the other errors are gone !

Adobe Air 2.0 beta causes overly transparent applications - unuseable

Hi,
   I'm running Crunchbang linux 9.04 (Ubuntu Jaunty) x64. I successfully installed Adobe Air 2.0 beta and apps run, but they are all so transparent that they can't be seen or used. Below is a screenpic of an adobe air application called doit.im. It works fine in Adobe air 1.5 on this rig, except it always asks me to click to okay the certificate and the window won't move, it's fixed where it is.
When running Adobe Air 2.0 apps, they are moveable, still ask me to click the certificate each time, but... they are WAY too unclear to see. When running the apps in a terminal, they yield no errors. I worked through all the gtk canberra errors successfully.
So I'm running the apps fine from 1.5, but just wondering if anyone know how to fix the overly transparent issue for adobe 2.0 beta - with X64 linux rigs.
    Thanks,
        Peace

Hi Tshann
Thanks for reporting this problem! We were aware of this issue and it will be fixed in the final release of AIR2.
-Thanks
Sundeep
AIR Team

Air 3.3 beta PC audio distortion / Air 3.1 / 3.2 Mac black screen issue

Hi there,
I've recently released a large game coded in Flash Builder with Air (www.lonesurvivor.co.uk), and I used Air 3's captive runtime feature to bundle it for Mac and PC.
The initial build used Air 3.2 and for a large proportion of OSX users, there were no visuals at all, just sound and the game obviously working underneath. This caused a very large support issue, and took several weeks to deal with, as well as having to maintain a seperate Projector version for those for whom the Air version wouldn't work. I wish I had known that the game would fail on some Macs, but unfortunately the issue showed up on none of the ones tested.
I'm about to launch the updated build of the game which uses Air 3.3 beta 1, as it seems to fix the black screen issue for all those who experienced it. I was very happy that Adobe have managed to iron this out, even if there was no response to the bug I entered into bugbase.
The problem is, on a final test on XP SP2, the 3.3 beta version produces what appears to be filtered graphics... which is how the Mac version has always appeared, but the PC version of the game seemed to use what looked like nearest-neighbour sampling in Flash's fulllscreen upscaling, which looked good for the zoomed pixel art in this game.
This is a small cosmetic issue, but there is another one whhich is far more severe - the audio has become extremely distorted, and is now unlistenable.
So with 3.2 giving me no visual on Macs and 3.3 giving me unlistenable audio on PCs, I will now have to maintain two versions again. I really would like to keep one project I can quickly make changes to, but the seperate problems in different platforms means I lose out on the great cross-platform functionality of Air. I'm hoping this is a known issue, but I couldn't find it on google / bugbase / these forums.
Could these two issues be related - is hardware acceleration not working or something? Somehow I think it is, because the XP test machine is quite old, and tended to fall over with the game running in software mode in a Flash projector.
I tried swapping out the Air 3.3 runtime for the previous 3.2 I shipped with, and editing the XML desciption to make sure it was set to use that and, sure enough, the game worked as it did before. So there is definitely something up with the beta. I'm just glad I caught this problem before I shipped as going to save me thousands of emails of support!
So I guess my question is - is this a known issue? And if so, do you have any workarounds / or are Adobe working on a fix?

Hi Chris,
Thanks for the prompt response - I guess I should have tried the forums instead of the bugbase last time... It really was a support nightmare! Not least because I had to deal with the problem of saved games being wiped by over-zealous browsers on the backup Projector version I was supplying Mac customers with.
Fortunately the Mac Air 3.3 runtime works great.
Out of interest - there is still the difference in GPU scaling used between Mac and Windows though, which there always has been since it was introduced (is this a known issue btw?)
Which leads me to the 3.3 beta 2 - I tried it out last night, and while it corrected the blurry graphics (the scaling appeared nearest neighour again on XP), the audio suffered the same distortion.
In addition, I had several other XP / Vista / Win 7 users test out the build, and the user with XP SP3 also suffered the issue.
So I'm planning to ship the PC version with 3.1 as it worked well for the first release, and use 3.3 beta 1 for the Mac version. Unfortunately I've run out of time and need to get it out there!
I'd definitely be interested in getting into the pre-release program. I'll write you an email and send the builds of the game too.
Cheers,
Jasper

Hey, I'm trying to install Adobe Flash on my Macbook Air. At a certain point it asks for my password but it doesn't take it. So I cannot continue installment. I have reset my password already. Still the same problem. How can I continue to install when it

Hey, I'm trying to install Adobe Flash on my Macbook Air. At a certain point it asks for my password but it doesn't take it. So I cannot continue installment. I have reset my password already. Still the same problem. How can I continue to install when it keeps asking for a password it doesn't recognize over and over again? How many times do I have to reset it then? Advice please

You have to provide your computer's administrator password in order to install Flash Player.

Can no longer return to iOS app in AIR 4.0 Beta

Is it me or is it no longer possible to return to an iOS app in AIR 4.0 beta? An app I just compiled restarts every time you launch it. No such problem in AIR 3.9.

Just yesterday I saw a problem where going to the home screen and back would either crash the app or would leave it in a frozen state. It only happened if by that time I had been via a part of the app that played an animation that used stream audio.
Might you be seeing the same kind of thing, where you can go in and out of your first screen, but get crashes or hangs when going from another screen?
I didn’t log a bug yet because it’s a hard problem to narrow down, because the crashing happens when you return to the app, and so doing a debug session won’t help, the session closes when you go to the home screen.

HT5621 I have changed my apple id on the manage my apple id page. For some reason, the id didn't change on my macbook air. My iCloud still registered my old email id and I can't get it to recognize my correct id. Any ideas? Thanks!

I have changed my apple id on the manage my apple id page. For some reason, the id didn't change on my macbook air. My iCloud still registered my old email id and I can't get it to recognize my correct id. Any ideas? Thanks!

Hi Baem_leeds
Welcome to the Support Communities!
If you change your Apple ID you will need to sign in with the new information or password the next time you use an Apple service or feature that uses Apple ID. If you have multiple devices that use features and services that require an Apple ID, you will need to sign in again on each device.
The links below will provide additional information:
Where can I use my Apple ID?
http://support.apple.com/kb/HT5616
Using your Apple ID for Apple services
http://support.apple.com/kb/HT4895
iOS: Changing the signed-in iTunes Store Apple ID account
http://support.apple.com/kb/HT1311
Cheers,
Judy

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.

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).

Have loaded lion and now cant access office for mac or apple works as it says it does not support power pc applications, how can I acces them or better still reinstate them please

Have loaded lion and now can't access office for mac or apple works as it says it does not support power pc applications, how can I acces them or better still reinstate them please?

MS-Office for Mac versions 2004 and older do not run in Lion since these are PPC-apps for which Apple has dropped support.
Free alternatives to open Word and Excel files:
NeoOffice http://www.neooffice.org/neojava/en/index.php
OpenOffice http://www.openoffice.org/
Or get the 2011 MS-Office

Adobe AIR ANE for Mac OSX 32-64bits Error

Hi,
I'm trying to build a ANE for Mac OSX. I setup XCode 5.1 and was following this two tutorials:
http://riawanderer.com/2012/03/27/working-with-air-native-extensions-on-the-mac/
http://quetwo.com/2011/12/03/working-with-air-native-extensions-on-the-mac/
To get the project setup.
I'm finding that Adobe AIR.framwork in folder /runtimes/air/mac is 32-bit, but XCode has deprecated 32-bit...so I'm finding this error when I try to build the project:
error: -fobjc-arc is not supported on platforms using the legacy runtime
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cl ang failed with exit code 1
So right now ANE development for Mac OSX is broke since I can't build a cocoa framework library due to 32-bit deprecation and Adobe not updating the library since 2011
I'm right or maybe I'm missing something.
Hope someone could give some path to solve this since it's very frustrating to deal with this stuff to see there's no update for this basic libraries for Mac.
If what I'm seeing is true, I see another error in Adobe stack that make people like me supporting the platform tired of deal with this kind of things. Sorry to be sound so frustrated but it's a very negative experience for the Adobe AIR platform since you see that a part of the platform is not updated for 3 years!.
Thanks
Carlos

Does what is talked about here help in any way?:
http://stackoverflow.com/questions/22363266/xcode-5-1-force-32-bit-compilation-for-a-cocos 2d-iphone-v3-project

Adobe AIR Alarm Services ANE for IOS and Android

I want to make an Adobe AIR app for android and ios platforms and i should use alarm services of these platforms (ios & android) for several scheduled times in a day when app is not running.
Could you suggest free or commercial ANE for this operation?
thanks.

Well nothing prevent you from mixing flascc with native extension.
Also, I think that you can also use domain memory in AS3 with the Bytearray class (not sure about that).
Flascc vs normal as3 is mostly a question of language (portability) Do you want to write as3 or c++?
Native extension give you speed and native platform access(platform specific feature).
So, you should think about it this way:
AS3, run in flash and air. Is sandboxed. Can use domain memory, but it's a bit harder to leverage than flascc.
Flascc, run in flash and air. Is sandboxed, Can use domain memory. Give you the potential of leveraging the hundreds of opensources lib already out there.
Native extension, run ONLY in air. Is not sandboxed. Native memory management. Also let you leverage the c++ lib.
The best (in my opinion) is to write native code for mobile and desktop (no air or flascc involve) and use flascc for the flash/web platform. It's harder, because you have write portable native code (lots of abstraction), but you mostly have the same problem with native extension.

Air 3.9 beta - update app with final ( non beta ) version?

I used Air 3.9 beta when i published on the app store, can i update with the final ( non beta ) version?

You can, but you usually don’t need to. When you have other reasons to do an update, just use a later version of AIR at that time.

Air 3.3 beta: Still relying on ANEs for hardware mute switch on iOS?

Similar Messages

Maybe you are looking for