Future native Android API support in AIR ?

Greetins,
Is Adobe planning to increase the number of native Android APIs that are accessible through AIR?
If so, is there a planned order in which this additional API support will be added to future versions of AIR SDKs?
AIR is an easier way to target Android (for me) than native Android dev with ADT. One major advantage being the Flash Builder Design View. But those advantages only go so far against the disadvantage of not being able to access all the native API's on the devices.
If the plan is to eventually support them all (within a reasonable time frame), then I can wait. If however, AIR on Android will not support any more APIs than it does now, learning JAVA for ADT dev will become necessary.
Thank you

Thanks for the responses. I posted to ideas as suggested. See link below.
http://ideas.adobe.com/ct/ct_a_view_idea.bix?c=9D564F43-979A-4E35-AA21-85A61B6AB8DE&idea_i d=97A23FF1-8471-4C26-8EC3-1FC9A9B7F29D

Similar Messages

Can an AIR application be packaged and launched from inside a Native Android Application

Hello,
I work for a company that has an AIR application/game. We are currently developing an Android native application and would like to strip out the AIR game and include it with the native application, we would like to be able to launch the game from within the native Android application. How would this be done?

no p. )
[UIApplication sharedApplication] its most cool thing in xcode that allow make native windows over adobe air

Will AIR has any problems in the future with Android?

Will AIR has any problems in the future with Android?
If we are experienced in flash, is it better to do the mobile work with AIR or HTML5?
But we are doing flash only so that we may face problems if we faced any bugs, is it expected to have any bugs or complexities, we can do flash with AS3 and we will depend on flash in publishing

Do you mean you dropped the iPad Air? Is it working properly? Is the screen damaged?
If it is working properly and has no signs of damage, it is probably ok.

How to convert keystore (from native android project) to .p12 to use with AIR project?

Due to the advancements with adobe AIR, I'm really excited to be finishing up a HUGE update of an old project that was originally made with native android.
But, i've hit a brick wall with 2 issues, and it would be terrible if all the work i've done in AIR was for nothing...
First, how do I convert the keystore I previously used (from native android project) to .p12 to use with AIR project? (on a mac)
Second, how do I remove the "air." that gets automatically appended onto the front my android package name? I plan to use a captive runtime, so it's not really needed at all, and I can't upload it like this as an update because it will think it's a different app.
Please help so I can continue using air for all my projects from now on!

Thanks for the reply!
So I'm going through this guide..
http://helpx.adobe.com/air/kb/opt-out-air-application-analytics.html
I followed all the steps, made all the adjustments to the androidmanifest.xml like it asks.
But when i get to the stap that says
"Run the following command to create the resource file for the updated AndroidManifest.xml:"
I run this..
    "/Users/brybam/Documents/eclipse/android-sdk-mac_x86/platform-tools/aapt" package -f -M AndroidManifest.xml -F resources.arsc -I "/Users/brybam/Documents/eclipse/android-sdk-mac_x86/platforms/android-8/android.jar" -S ./res
But I keep getting the same error
    ./res/layout/expandable_chooser_row.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/expandable_multiple_chooser_row.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/main.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/multiple_file_selection_panel.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/ssl_certificate_warning.xml:1: error: Error parsing XML: not well-formed (invalid token)
The guide doesn't say anything about these xml files, and im not sure what to do with these ore how to handle them.
If i go into the res/layout folder, and just delete these (i know theyre for my layout and i need them, but im just saying i deleted them for the sake of a test)
I was able to get through the rest of the steps in the guide fine, make an apk, and put it on my phone...only to find out the app will crash the moment you try to run it.
So my question is, does anyone with any experience re-packaging an android application know how I might get around this or take care of the errors with the xml files in the layout folder?
Thanks!!
EDIT to note something i've tried:
So, earlier in the guide they have me use thing thing called the "AXMLPrinter2.jar" to make the AndroidManifest.xml readable so i can edit it.
I run something like this:
    java -jar "/Users/brybam/Desktop/repackage/AXMLPrinter2.jar" AndroidManifest.xml > AndroidManifest.xml.bk
This makes a new file "AndroidManifest.xml.bk" and i can edit that.
So, I was thinking with all of these layout xml files, maybe I could run this "AXMLPrinter2.jar" on them and then edit them. Because right now if you open them they're not human readable, and its hard for me to work on them if they're not...
But when i do the same command I did on the AndroidManifest.xml i just get blank files...
I tried
    java -jar "/Users/brybam/Desktop/repackage/AXMLPrinter2.jar" main.xml > main.xml.bk
Just get a blank file.
So, i think the issue might be with these just not being re-formatted to human readable.

Hello world Native Extension API

Hi all :-)
I am an android expert and I'd really love to create some cool extensions like the android notifications, but since I don't know much about Flex, I have a lot of trouble getting the test vibrator with native extension working.
(http://www.adobe.com/devnet/air/native-extensions-for-air/extensions/vibration.html)
My sample is still buggy, it is probably beginner's bug, but I don't see how to fix it yet.
I am surely not the only native guy trying to do this, so I would like to sumarize here all the steps needed to have our first hello world Native Extension API
Install Flex 4.5.1 http://www.adobe.com/go/try_flashbuilder/ and download the Adobe AIR 3.0 RC http://labs.adobe.com/downloads/air3.html as well as the sample files http://download.macromedia.com/pub/developer/air/ane/Vibration.zip
Create a test Flex mobile project.(all the deffault parameters are fine) I'll call it HelloWorldNativeExtension.
(If AIR 3 is not released yet) Do the following to tell Flex builder to use the RC on your test project : http://forums.adobe.com/thread/899921
Unzip the vibration.zip, and go to ready to use extansion.
Go to Project -> Flex buildpath -> Libraries -> Add a new swc. Add the ready to use extension as a library. Then open the extensions properties and change the link type from "bundled with" to "external linkage"
Go to HelloworldNativeExtension-app.xml and in the tag manifestAddition, add : <uses-permission android:name="android.permission.VIBRATE"/>
Write a sample view (as described below)
Run (target platform->android and then chosse to run on a device)
When asked to update the air version, answer yes
Wait a loooong time before it actually start.
Here is my code for the sample view:
In HelloworldNativeExtension.mxml
Use the following code :
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/mx">
    <fx:Script>
        <![CDATA[
            import com.adobe.nativeExtensions.Vibration;
            protected function testButton():void
                textArea.text="Before vibration";
                var vibe:Vibration;
                if (Vibration.isSupported)
                    vibe = new Vibration();
                    vibe.vibrate(2000);
                textArea.text="After vibration";
        ]]>
    </fx:Script>
    <s:Panel title="Exemple MXML" width="330">
        <s:layout>
            <s:VerticalLayout paddingLeft="15" paddingTop="15" paddingBottom="15" paddingRight="15"/>
        </s:layout>
        <s:Label x="223" y="173" text="test" id="textArea"/>
        <s:Button label="Vibrate" click="testButton()"/>
        <s:Label id="result" width="265"/>
    </s:Panel>
</s:Application>
Well... so far my project doesn't compile because the library is loaded externally. It compiles fine if I add it as a bundled library, but then the virbrator can't work (External native code have to be loaded externally)
And thus so far I get the errors :
Description
Ressource
Chemin
Emplacement
Type
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.display]::IBitmapDrawable.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
1046: Ce type est introuvable ou n'est pas une constante de compilation : [flash.events]::IEventDispatcher.
HelloworldNativeExtension
Inconnu
Erreur Flex
(Which means something like : 1046: this type cannot be resolved or is not in the buildpath ... So it probably means the project doesn't compile well)
So I'm still trying to figure out what to do, but I am close I think... Very close.

Yes, in fact you are very close
You will have to put an <extensions> tag in app-xml if not already done so:
<extensions>
<extensionID>com.adobe.Vibration</extensionID>
<extensions>
Then since it is FlashBuilder 4.5.1, you will have to package the android application through command line since it requires 1 more parameter -extdir :
adt -package -target apk . . . app.apk app.xml app.swf -extdir extensions
extensions is the directory which contains your .ane file. Checkout http://www.adobe.com/devnet/air/articles/extending-air.html#articlecontentAdobe_numberedhe ader_1 for more details.
Thats all. You should be able to run your app now. Let me know if it still doesnt work.
Thanks,
Meet
AIR Team

How to switch from legacy to native Android app with minimal interruption

It's gotten to the point where I'm recommending that my client switch their DPS app for Android from legacy to native. Can anyone offer any insight into the process of changing that over for an existing app? Most of the Adobe support documents are written for starting a new app in native format. I need to give the client an idea of how the transition will affect existing subscribers on the Android platform (i.e. will they need to download a new app, or will it work as an update) and what we can do to retain readers if they do need to download an entirely new app.
Complicating the situation is that the client likely will want to keep the legacy app as long as we can to continue offering it on Amazon, because Kindle devices account for 60 percent of our non-iOS downloads.
Thank you!

To replace the existing legacy viewer, simply use the same Bundle ID used in the legacy app when you build the native Android viewer, and then submit the app as a new version in the Google Play Developer Portal. To locate the Bundle ID for the legacy viewer, open the desktop version of DPS App Builder and look at the list of apps. It might include a .air prefix, depending on when the app was built. If it does, use the .air prefix when you specify the Bundle ID for the native viewer, even though it's not an AIR app. The Bundle ID just needs to be the same. If you want two separate apps--which I don't recommend--use a different Bundle ID and submit it in the Developer Portal as a new app.
The Amazon app is a different app that's unrelated to the Google Play app. You can continue to leave the app in the Amazon Appstore.

Are inline youtube videos supposed to work in native android viewer?

Hello,
I'm testing the new native android viewer. We are currently using the legacy viewer. I am wanting to have inline video - specifically from youtube, like we are able to do in iOS. Is this possible? I am still just getting sound and no visual in all of my tests. Thanks!

After some research, we've found that this is definitely Google's bug on Android and was fixed by them in later versions.
http://stackoverflow.com/questions/14289848/embedded-youtube-player-getting-cut-off
http://stackoverflow.com/questions/10433865/problems-aligning-a-youtube-clip-centrally-in- an-android-webview
http://stackoverflow.com/questions/16273930/video-is-cut-off-on-the-right-side
http://stackoverflow.com/questions/13080578/partial-screen-webview-with-video-cut-in-half
We're discussing now whether a) we could work around this given our current architecture, and b) whether it's worth the cost for these older devices. Either way, the experience is very slow on the older API and devices that ran it when you have youtube videos embedded in web views. Those devices simply aren't powerful enough. If the publisher you're working with owns the videos, I would consider streaming them directly, outside of youtube, in a native video overlay (we support streaming video on Android). The experience and performance should be better.
Regards,
Dave

HTML Banner for Native Android App Builder

In the release notes it says
The HTML banner in the library has limited available APIs.
I don't even see a place in the app builder to define a banner.
We called Gold Support and they don't know anything about the new Native App Builder.
Thanks,
Darrin

I know that with Android the subscriptions are not supported but a header banner (static - no action linked) is important to see!
Client want a branded viewer - now is very poor!
Are there some news about this? Now i'm working with the new native Android app and i see that in the web builder (works very well!) there is not a field to upload a png. V31, V32?
I use Professional

Native signing not supported on mac!!

To sign both the installer and its executable we're using Thawte and Comodo certificates. For MacOS we've Thawte and Apple. This following command builds a proper signed installer version (along with its executable .exe) with the combination of both the certificates, in Windows:
adt -package -storetype pkcs12 -keystore myCert.pfx -target native -storetype pkcs12 -keystore myCert.pfx myApp.exe myApp.airi
(http://help.adobe.com/en_US/air/build/WS789ea67d3e73a8b22388411123785d839c-8000.html)
When running the same command to compile a .dmg file - ADT reported an error:
Native signing not supported on mac
I'm not sure if the adt doesn't has the ability to do such process in MacOS unlike Windows! Any idea?

Hello Ken,
Thanks for commenting. But that 'solution' already tested and its found not true with recent AIR SDK version.
If you do this:
adt -package -storetype pkcs12 -keystore myCert.pfx -storetype pkcs12 -keystore myCert.pfx myApp.exe myApp.airi -target native
You'll have compiler error:
"-storetype already specified", and you can see why in the command
If you do this:
adt -package -storetype pkcs12 -keystore myCert.pfx native -storetype pkcs12 -keystore myCert.pfx myApp.exe myApp.airi -target
You'll again have compiler error:
"not enough argument"
I don't think this have a fix yet.
I lodged a bug at: https://bugbase.adobe.com/index.cfm?event=bug&id=3655573

How to read inline feed using android api for odata

Hi,
Need help on reading inline feed using android api. BB and iOS supports inline but for android there is no api.
Please suggest the workaround
Regards,
Satish

This link is very useful:
Knowledge Management and Collaboration (KMC)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/kmc/Knowledge%20Management%20and%20Collaboration%20Developers%20Guide.html
Patricio.

Error: native VM not supported

Hi
I have just run the blackbox application in the javacomms API download:
1) I invoked it using the prescribed command java -native blackbox to which I got the error native VM not supported.
2) I then ran it again without the -native switch and got the error Exception in thread "main" java.lang.NoClassDefFoundError: blackbox.
Can anyone help please? Is there something I have not installed correctly? I am using Windows XP professional service pack 1.
Thanks
Chris Wilson

java.lang.NoClassDefFoundErrorThat always means that either your classpath is wrong or that isn't the name of the class.

Native Android Extension - Service Not Found

Greetings,
I have created an AIR native extension which I am using in an AIR for Android app. My native extension needs to use an Android Service from a 3rd party library. However, seemingly no matter what I do to hook up this Android Service in the native code, the app reports "Unable to start....service not found" at runtime.
Now I have used this service in normal, native Android apps and it works fine - I have tried duplicating the same startup process from my previous apps, that process still results in a "service not found" error in this AIR for Android app.
Does anyone know whats going on here, or had similar issues?
My only thought at this point is that the intense mangling that happens when AIR compiles an APK might be screwing up the path to the Service, therefore the class loader on the Android device is unable to find the service at runtime. However, I do not know how to prove this hypothesis.
I have gone as far as to write my own Service class which wraps around the 3rd party service, so that the service I'm requesting is in the same java package as all the other native extension code I'm writing, but that option didn't work either.
Any help would be appreciated.
Thanks.
Matt
PS - In case you're wondering, I did make sure to declare the <service> tag in my extension's manifest file.

Hey Chris!
I figured out *JUST NOW* what the issue is (and this is certainly NOT documented in any PDF, or whitepaper on Native Extensions).
The problem lies with both the Signing Certificate and the package name for your AIR Application.
Rules for Adobe AIR Native Extensions
Rule 1 (Documented)
The Code Signing Certificate package must match the application id in your app.xml
so if the certificate package is `com.my.company`, then the air app id must be `<id>com.my.company</id>`
Rule 2. (Partially Documented)
When packaging a native extension for android using ADT, a prefix is added to your package name so it looks like `air.com.my.company`.
(Not Documented)
When the Android ActivityManager tries to run your service it looks for it in `air.com.my.company`. Thus, the Service class must live in the same package (including the 'air' prefix) within your java code. My TestService class now is defined as `air.com.my.company.TestService`
And with the following manifest, it runs just fine!
<application>
          <activity android:name=".TestActivity">
                    <intent-filter>
                             <action android:name="TestActivity"/>
                              <category android:name="android.intent.category.DEFAULT"/>
                    </intent-filter>
          </activity>
          <service android:enabled="true" android:exported="true" android:name=".TestService">
               <intent-filter>
                                       <action android:name="test.default.service"/>
               </intent-filter>
          </service>
</application>
Start the service using the following code
startService(new Intent("test.default.service"));
Thanks again!
Bow

BB10 runs native Android by partitioning?

Since there is not a BB10 support site yet. I will throw the question out here as PlayBook is QNX based.
After reading an old thread about running IOS on the Playbook, so why not run Android on PlayBook under BB10? Why do it in a round about way using Dalvik VM and getting partial result?
There will be four cores in the Snapdragon S4. Can one or two core(s) be partitioned out to dedicate to run native Android?
Android is an open source and IOS is not. RIM can pick up the Android for free and immediate.
I understand RIM doesn't want to be another Android. Why not use BB10 for business application and Android for consumer application. No need to reinvent the consumer ecosystem. It is out there for the taking...free!
Would not BB10 /Android be have the cake and eat it too?
Apple's real competitor is Android. RIM joining Android would be a great way to fight Apple, wouldn't it?
I like to hear what all the smart people here think.
Thanks.

beavertail wrote:
why not run Android on PlayBook under BB10? Why do it in a round about way using Dalvik VM and getting partial result?
Because that's the way Android works. There is nothing "round about" about it. All Android devices run a Dalvik VM too. Most Android apps are Java apps, and thus more or less require a VM. If you were to somehow precompile Dalvik bytecode, it would most likely be incompatible.
Files & Folders, the unified file & cloud manager for PlayBook and BB10 with SkyDrive, SugarSync, Box, Dropbox, Google Drive, Google Docs. Free 3-day trial! - Jon Webb - Innovatology - Utrecht, Netherlands

FileSystem API support in Safari?

Hi
I was trying to run this filesystem api demo: http://html5-demos.appspot.com/static/filesystem/filer.js/demos/index.html
in Safari. It says browser not supported.
Is Browser FileSystem API supported in Safari? If not will it be supported in future?
- Ambili

Safari (and mobileSafari) rely on WebKit - you may want to check there for hints on future direction and see if you can lobby them accordingly.
http://webkit.org

Please add native video call support to your phones

hey sony, please add native video calling support in your xperia s and xperia 2011 series with front cam , pelase ,we need that so much and you can do that ! please do not be lazy

there are myriad threads on this topic
1) the 2011 Xperias are not going to get any major updates anymore
2) Android doesn't support this natively
3) only few android phones have this in specific markets
4) it was requested by few users back with the 2010 Xperias and hasn't been added and most likely it wont
is Sony spying on users in this forum?
http://talk.sonymobile.com/thread/60197
Don't forget to mark the Correct Answers & Helpful Answers
UNRELATED topic, if you have some time please check this thread
http://talk.sonymobile.com/message/244522#244522
"I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994)

Future native Android API support in AIR ?

Similar Messages

Maybe you are looking for