3.2.0 Adobe Air android - question uri custom

Similar Questions

• GTIS-90086 'Lack of 64 bit support' error downloading Adobe Air application questions

  Hello

  I have an Adobe Air based application which I previously downloaded using the iTunes connect application loader.

  Today, I get the error: ERROR ITMS-90086 'Missing Support 64-bit' iOS apps submitted to the App Store must include 64-bit support and built with iOS SDK 8 or later.

  It's weird because the 64-bit requirement has existed for some time and I use the same build method has been accepted previously.

  I tried the building without the extensions to exclude third party extensions. I have updated to the latest version of the Air SDK and use new certificate/provisioning profiles.

  Any ideas, what has changed?

  Tom

  Try to update Application Loader 3.1 or newer or install xcode last

• Impossible to compile Adobe AIR for Android TV

  Hello

  We try to compile the AIR with the flags are:

  < android >

  < manifestAdditions > <! [CDATA]

  < manifest android: installLocation = "auto" >

  ...

  < / manifesto >

  []] > < / manifestAdditions >

  < supportsAndroidTV > true < / supportsAndroidTV >

  < banner > "path of the image of the banner (320 x 180 px, .png file)" < / banner >

  < / android >

  and get:

  C:\MediaSignageDepot\Solution\5.0\Products\SignagePlayer\Android\SignagePlayerAn

  droidApp - app.xml (206): error 103: application.android.supportsAndroidTV is a UN

  element/attribute EXPECTED

  Anyone had success compile those flags with Adobe AIR for Android TV last?

  We're uisng the flag of swf-version 31 and namespace 20.0 to try to access this feature.

  We use the AIR 20

  Kind regards

  -Sean http://DigitalSignage.com

  ____________________________________________

  MediaSignage.com, digital signage FREE for everyone!

  5776-D Lindero Cyn Rd #182

  Westlake Village, CA 91362

  Phone: 1.877.DIG. SIGN (1-877-344-7446)

  Fax: 1.818.337.0442

  Live support: http://chat.digitalsignage.com

  I see that beta support has been added for Android TV in one of the beta versions of AIR 20. Read this discussion:

  AIR 20.0.0.230 iOS install questions and support Android TV has stopped working

  It seems that you would have used equip 185 and not the final version. Or you can try an AIR 21, or 22 AIR beta version.

• Many problems with the runtime Adobe AIR for Android

  I created an application on Adobe AIR for Android platform, which requires for AIR. The app is very popular in the Android Market, but many users complain of problems with the installation of the Adobe Air runtime.

  For example, these users phones: LG LGE-P698, LG Pecan, HTC Wildfire. But judging by the fact that users have access to the installation of the Air, their phones are compatible with it.

  Tell me how to solve the problem?

  In addition, I have a few questions:

  1. Decides that the problem of demand for export with built-in AIR runtime?

  2. I have create my applications using ADT. In this case how do I seal AIR runtime?

  3. is it possible to invite the user to download and install older versions of AIR? Where can I find her?

  I hope I can help, because the problem is global.

  Hi Astraport,

  I think you should integrate the air in your application runtime,

  Some time ago I wrote a step by step guide, take a look at this post:

  http://forums.Adobe.com/message/3961579#3961579

  I hope it helps

• the overview of the .pdf on Android using flash adobe air app.

  Hello

  can someone help me?

  Thanks Gerard.

  Hello

  Adobe AIR is not for PDF documents.  You will need a PDF as Adobe Acrobat Reader - Android applications on Google game player

  --

  Maria

• Adobe Air for Flash CS6 works only on Android 5.0.2

  Hello

  I tried to publish a game that I have developed in Adobe Flash CS6 using the Adobe Air platform.

  I've done this countless times before, I'm not new to develop in Flash.

  Even if everyone thinks that HTML5 will take over as "Flash is dead" I still think it's a great development platform.

  I have trouble getting my APK files to run on Android 5.0.2 (Lolipop) without apparent reason.

  If I choose to install AIR separately, it works. If I decide to incorporate it into the APK, it gives an error immediately after the launch of the app.

  There is no error code and nothing I can do reference. just an error "The Application was able to start".

  I would be grateful if someone could help, thanks.

  This article was written 7 months ago, there is a good chance that the AIR is ok with 5 Android now. Even the article, that it was fixed in 5.0.1.

  AIR installed on the computer is not the same as the AIR SDK. You don't want to not download either version of the AIR SDK:

  Download Adobe AIR SDK

  or download the latest beta, which is be AIR 19:

  Download Adobe AIR 19 Beta - Adobe Labs

  Once it has downloaded and unzipped, you will have a record. Now go to the Help menu of Flash Pro and select managed Adobe AIR SDK...

  Here, you can add an item and navigate to where the folder is located. It can be anywhere, I tend to leave in my downloads folder.

  If you were to take the file act.jar of this article it would be things likely to mess. But just as a point of interest to Flash Pro users, the file is located in the SDK folder, inside the lib folder.

  So, the short version of what I hope are you currently build for AIR 3.2, who would have a chance with the latest versions of Android, and edit using AIR 18 or 19 would be a good idea.

• Partial Wakelock in Adobe Air for Android

  I develop Adobe Air (for Android) application that is designed to be constantly turned on. App has operations based event. However, when the phone goes to sleep mode app is able to perform only one or a few events in a second which is not good enough. AIR SystemIdleMode.KEEP_AWAKE - mode is not an alternative because it is too consuming battery.

  I am looking for a solution when the phone is allowed to enter the mode 'sleep' (screen is off), but still the CPU performance are not radically fallen. Not sure Android part wakelock-mode does the job and is available through DONKEY?

  What type of event you are missing to be able to manipulate during sleep? According to the documentation from Adobe AIR decreases the rate of 4 frames per second when it is moved to the background or becomes inactive. Im guessing that the screen, disabling account in this respect and that is probably a reason as to why you have found only a few events a second, but I can't say for sure without knowing what type of event you use. In regards Android PowerManager WAKE_LOCK function, Google documentation says that you should not use this API unless you absolutely, and if you have to use it, you use it and do with it as soon as possible as long as this hurts API independence (they have same "BOLD" the part about the battery life). What you try to do that requires that the app is always on? More details can help myself or others provide other options to accomplish what you are trying to do. If you must use the PowerManager, you should be able to create a DONKEY to turn on and off the WAKE_LOCK mode, but could only help the side Android/Java things and you might need to move your event handling during the side of things because Java application of AIR will be always abandoned at 4 frames per second when the screen turns off.

  Adobe AIR * Mobile application design considerations

  PowerManager | Android developers

• Adobe Air on android 4.1.0 and more

  No android 4.1.0 and above tablets support adobe air? Are there any known issues or bugs?

  There should not be problems with Adobe AIR on Android 4.1

  If you have any problems, please post on the forum of the AIR.

• PromptDialog question (BlackBerry® Tablet OS SDK Adobe Air)

  I have the following code to display a prompt dialog box in which you can enter text after a user clicks on a button. The prompt dialog box displays 2 buttons: OK and cancel. Whatever button I click, the program is never in the "onPromptButtonClicked" event listener function (I don't see the text "Hello" in the debug output).

  What I'm doing wrong here?

  private function onBtnAddTextClicked (event: MouseEvent): void {}
  var promptromptDialog = new PromptDialog();
   
  prompt. Title = "Title";
  prompt.message = "Please enter the text:";
  prompt.addButton ("OK");
  prompt.addButton ("Cancel");
  prompt.addEventListener (DialogEvent.DIALOG_BUTTON_CLICKED, onPromptButtonClicked);
  prompt. Show();
  }

  private void onPromptButtonClicked(event___ialogEvent):void {}
  trace ("Hello world");
  }

  Hey eugenevk,

  Yes unfortunately this is a bug and I hope it gets fixed soon. It has been discussed on the forums prior and work around it was the following:

  Replace:

  prompt.addEventListener(DialogEvent.DIALOG_BUTTON_CLICKED, onPromptButtonClicked);
  

  with:

  prompt.addEventListener(Event.SELECT, onPromptButtonClicked);
  

  and he must do what you need to do. Here is a reference thread if you need more information:

  http://supportforums.BlackBerry.com/T5/Tablet-OS-SDK-for-Adobe-Air/strange-dialog-behaviour/m-p/6681...

  hope that helps. Good luck!

• Adobe AIR for Android update fails to UPDATE

  Why the update for Adobe AIR is a failure to update, and also how is it that no one is able to install?

  Nathan I would recommend posting a request on the Adobe AIR http://forums.adobe.com/community/airforum.

• Porting an application multi-threaded for Adobe Air.

  Someone at - it never been faced with this task?

  The application in question has a thread about 10 in addition to the main user interface thread.

  Each thread is blocking ops in long-distance communication, GPS, HTTP, manipulation of the filesystem, processing of data of general application, SQL execution, etc.

  Very little of it is based on the direct interaction of the user.

  Is it possible to get something like this in Adobe Air?

  Or simply wait for Android/BB... which would be realistic player out right at about the time where that this port is complete.

  Support an implementation not threaded with threaded implementations could be a lot of work.  I would recommend waiting.

  AIR has a flash.utils.Timer class, or a simple setTimeout() call that uses only the timer below.  The question is not "burden" on the UI thread, depending on CPU load... work has to be done one way or the other.  The issue is latency, in terms of how long it takes the application to respond to user events, or how long to make the updates.  Do more that small pieces at a time in the main thread, you will feel your app slow and inconsistent, with irregular updates and (if you try) animations jerks.

  Thread safety is not a big deal, normally... it is a matter of concern for applications poorly structured in a multithreaded environment.  Properly structured multi-threaded applications will eventually look a lot like an AIR application, with respect to certain things (for example, GPS pilot or connections SQLite) communicating through mechanisms of threads (queues, events, etc.) with the main thread.

  Called async stuff basically back to the main thread.  What are the event listeners.  You might be better not think of it as a wire when even... it's not like your "main thread" in another application, perhaps, where you have full control.  This is the main thread in a framework of GUI like WxWidgets or QT or whatever... everything is done with events and you * must * return to the caller (the frame) as quickly as possible or you will have a user experience impact.  Basically, the entire application is a collection of event listeners, with no place where you can implement a "loop of interrogation" for example, as you might in a different environment.

  Rather than stuff on 'simple threaded environments', you should probably just search for "asynchronous programming" or "event-driven" stuff.  There not much more to it than that.

• Adobe Air will keep living or should move us on to HTML5!

  Hello!

  After reading these recent news, I noticed that they want to tell us that adobe Flash is to reach the end of the rope! Is this true?

  (a reply from the Adobe creative team will be highly appreciated, for me and others who have read this post.)

  
  

  My https://www.yahoo.com/Tech/s/Adobe-Flash-finally-Dead-183755537.html?soc_src=mail & soc_trk =

  
  

  This will affect only the "Desktop" applications and web banners in Flash?

  Or it also affect Mobile Applications written in Adobe Flash / Air packages?

  
  

  So, I need to raise this question asked by another developer in 2013:

  Re: Continue with Adobe AIR or move back in with HTML5?

  
  

  It is now many years, I use Adobe Flash CS6 to develop Air for Mobile Applications, same source for iOS and Android. And everything works very well for our applications. So I have no knowledge of HTML5 or JAVA or anything except Flash and AS3.
  

  
  

  It's time for us to developers to change our old tools? What will happen to our applications on the market that needs regular updates! What is the alternative do you propose!

  
  

  Thank you and hope to receive an answer to this, soon.
  

  
  

  Don't believe these articles stating that «Killed Adobe Flash» The only thing they have done is rename Flash Professional CC (the tool, not the player) to animate CC. everything will stay the same and probably take it from here.

  Other news, Adobe has announced a collaboration with Facebook to improve the Flash Player, which is good news and a positive signal for the Flash Player.

  http://blogs.Adobe.com/conversations/2015/11/Flash-HTML5-and-open-Web-standards.html

• Can update my AIR Android app with an app without AIR?

  A few years ago, I published an Android with Adobe AIR application. Now, I created a new version of the application with a different technology (HaxeFlixel / OpenFL) which uses the native C++ code.

  The certificate that I used for the AIR version is in the format "p12", and it seems that I need to use the format "jks". I tried to use a converter jks p12 I found online, which seemed to work, but when I try to submit the app I get an error saying that the certificates do not match.

  Any suggestions on how I can update the application with an app without AIR? Is this possible? Thanks in advance.

  Just for the record, I was able to solve the problem by removing the certificate of the apk and again sign the jks certificate, jarsigner. I followed essentially this: te-than-what-it-came-with http://stackoverflow.com/questions/3267216/can-i-re-sign-an-apk-with-a-different-certifica if the problem had something to do with the way the application was signed, not the certificate.

• Time of excessive latency of connection... Adobe Air supports on mobile connection pooling?

  Hello

  I'm developing a mobile application that loads the thumbnail images to a remote server. During testing on the Android platform, however, I discovered that the images are very long to load. By monitoring the server logs, I determined that poor performance is caused by the absence of connection pooling, which means that each request creates a new connection. Running the sample code below on a mobile device produces 20 applications and 20 attempts to connect. By comparison, the same web application or desktop creates 2 connections and reuses connections for the following applications. Important overhead and latency associated with generating new connections has a significant impact on performance, with 20 thumbnails taking about 4-5 seconds to load on mobile compared to 0.5-1 second on a desk.

  I've included a sample application below the emphasis placed on the performance issue. The image itself is very small (290 bytes), to focus the issue on the latency of the connection. I confirmed this behavior on many Android devices running 4.1, 4.0 and 2.3. I also tried using the charger c. URLLoader v. URLStream and v. sequential loading with no change in the behavior of simultaneous connection. Trying to set up the connection to 'keep-alive' in the URLRequest has also no effect.

  package

  {

  import flash.display.Loader;

  import flash.display.Sprite;

  import flash.display.StageAlign;

  import flash.display.StageScaleMode;

  import flash.events.Event;

  import flash.net.URLRequest;

  import flash.utils.getTimer;

  SerializableAttribute public class Main extends Sprite

  {

  private var _count:int = 0;

  public void Main()

  {

  Super();

  internship. Align = StageAlign.TOP_LEFT;

  stage.scaleMode = StageScaleMode.NO_SCALE;

  trace ("Start time" + getTimer() + "ms");

  var loader: Loader;

  var url: String = " " http://fbcdn-profile-a.akamaihd.NET/static-AK/rsrc.php/v2/yo/r/UlIqmHJn-SK.gif ";  290 bytes

  for (var i: int = 0; i < 20; i ++) {}

  loader = new this.addChild (Loader()) as a charger.

  loader.contentLoaderInfo.addEventListener (Event.COMPLETE, complete);

  Loader.Load (new URLRequest (url));

  }

  }

  private void complete(event:Event):void

  {

  _Count ++

  trace ("Completed" + _count + 'to' + getTimer() + "ms");

  }

  }

  }

  So, I have a few questions:

  (1) is there something I can do to allow the reuse of connection?

  (2) is it an inherent limitation with Adobe Air for mobile?

  (3) is that someone can confirm if this limitation exists on other mobile platforms (iOS or Blackberry)?

  Any help you can provide would be greatly appreciated. I really hope that this isn't a fundamental limitation of Adobe Air because it weakens my application to feel very slow.

  Thank you

  Adam

  Hmm. You were quite right, it's a little disappointing!

  This is Android recompiled for 3.4 rather than 3.1.

  null

  OVER 50 with 8 Chargers in 11327 milliseconds or 226,54 by load.   50 8 11327 226,54

  OVER 50 with 50 Chargers in 8899 milliseconds or 177,98 by load.   50 50 8899 177,98

  OVER 50 with 50 Chargers in 9280 milliseconds or 185,6 by load.     50 50 9280 185,6

  OVER 50 with 50 loaders in 9513 milliseconds or 190.26 per charge.   50 50 9513 190.26

  OVER 50 with 8 Chargers in 9744 milliseconds or 194.88 by load.     9744 8 50 194.88

  OVER 50 with 1 Chargers in 16383 milliseconds or 327.66 by load.   16383 1 50 327.66

  Compared with Apple iPad recompiled for 3.4 rather than 3.1.

  null

  OVER 50 with 8 Chargers in 502 milliseconds or 10.04 per charge. 50 8 502 10.04

  OVER 50 with Chargers of 50 to 100 milliseconds or 2 per load.     50 50 100 2

  OVER 50 with 50 Chargers in 117 milliseconds or 2.34 per charge. 50 50 117 2.34

  OVER 50 with 50 Chargers in 93 milliseconds or 1.86 per charge.  50 50 93 1.86

  OVER 50 with 8 tires in 270 milliseconds or 5.4 per charge.    50 8 270 5.4

  OVER 50 with 8 Chargers in milliseconds of 307 or 6.14 per charge.  50 8 307 6.14

  OVER 50 with 8 Chargers in 316 milliseconds or 6.32 per charge.  50 8 316 6.32

  OVER 50 with 4 Chargers in 555 milliseconds or 11.1 per charge.  50 4 555 11.1

  OVER 50 with 4 Chargers in 547 milliseconds or 10.94 per charge. 50 4 547 10.94

  OVER 50 with 4 Chargers in 535 milliseconds or 10.7 per charge.  50 4 535 10.7

  OVER 50 with 2 Chargers in 1038 milliseconds or 20,76 by load.        50 2 1038 20,76

  OVER 50 with 2 Chargers in 1042 milliseconds or 20,84 by load.        50 2 1042 20,84

  OVER 50 with 1 Chargers in 2107 milliseconds or 42,14 by load.        50 1 2107 42,14

  OVER 50 with 1 Chargers in 2099 milliseconds or 41,98 by load.        50 1 2099 41,98

  Both are on the exit compilation, which should take all of the variability. So, Yes, it is as if the Runtime AIR 3.4 lost the pool of connections, but ONLY for Android.

  PS: Code I used in my test (which was a view based Mobile application conventional) is below in case you want to include it when you submit a bug report.

  
  http://ns.Adobe.com/MXML/2009.
  xmlns:s = "library://ns.adobe.com/flex/spark" title = "TestLLatency" xmlns:mx = "library://ns.adobe.com/flex/mx" >
  
    Import mx.events.FlexEvent;
    
  protected function uicomponent1_creationCompleteHandler(event:FlexEvent):void
  {
  startTest();

  }
      
  public function startTest (): void {}
  If (tail) throw new Error ("Please wait for the previous test at the end.");
  queue = new Array();
  _Count = 0;
  var loader: Loader;
  var i: int;
  for (i = 0; i< numtoqueue;="" i++)="">
  loader = new bob.addChild (Loader()) as a charger.
  Loader.x = (I have 10%) * 50;
  Loader.y = Math.floor (i/5) * 50;
  loader.contentLoaderInfo.addEventListener (Event.COMPLETE, complete);
  queue.push (Loader);
  }
  startTime = getTimer();
  for (i = 0; i
  nextQueue();
  }
  }
  protected var startTime:int;
  protected var endTime:int;
  protected var numToQueue:int = 50;
  protected var numLoaders:int = 8;
  protected var queue: Array;
  private var _count:int;
  private void complete(event:Event):void
  {
  _Count ++
  nextQueue();
  }
  [Bindable] protected var results: String;
  protected function nextQueue (): void {}
  var url: String = "http://fbcdn-profile-a.akamaihd.net/static-ak/rsrc.php/v2/yo/r/UlIqmHJn-SK.gif";  290 bytes
  if(queue && queue.) Length) {}
  var loader: Loader = queue.pop () as a charger.
  Loader.Load (new URLRequest (url));
  } else {if(_count==numToQueue)
  endTime = getTimer();
  var last: int = endTime-startTime;
  results += "\n" + ("COMPLETED" + numToQueue + "with" + numLoaders + "Chargers in ' + (elapsed) +" milliseconds or ' +(elapsed/numToQueue) + ' by load.\t"+[numToQueue,numLoaders,elapsed,elapsed/numToQueue].join("\t ' ""));
  queue = null;
  {while(Bob.numChildren>5)}
  bob.removeChildAt(bob.numChildren-1);
  }
  bob.getChildAt (0) .addEventListener (MouseEvent.CLICK, repeatTest);
  bob.getChildAt (1) .addEventListener (MouseEvent.CLICK, repeatTest);
  bob.getChildAt (2) .addEventListener (MouseEvent.CLICK, repeatTest);
  bob.getChildAt (3) .addEventListener (MouseEvent.CLICK, repeatTest);
  bob.getChildAt (4) .addEventListener (MouseEvent.CLICK, repeatTest);
  }
  }
  protected function repeatTest(event:MouseEvent):void {}
  var dob:DisplayObject = event.target as DisplayObject;
  var testBehaviour:int = dob.parent.getChildIndex (dob);
  try {}
  {Switch (testBehaviour)}
  case 4:
  this.numLoaders = this.numToQueue;
  break;
  case 3:
  this.numLoaders = 8;
  break;
  case 2:
  this.numLoaders = 4;
  break;
  case 1:
  this.numLoaders = 2;
  break;
  case 0:
  this.numLoaders = 1;
  break;
  }
  startTest();
  dob.removeEventListener (MouseEvent.CLICK, repeatTest);
  for (var i: int = 0; i<5;i++)>
  } catch(e:Error) {}
  trace (e.message);
  }
  }
   
  ]]>
  
  
   
  
  
   
   
   
  
  

• How can rejection of the Amazon - the link to Adobe AIR in your app update needs - I change this

  Here is a message I received from Amazon:

  Unit tested : Motorola Droid (2.3), HTC Evo (2.3.3), Samsung Galaxy Tablet (2.2)

  Question : The link in your Adobe AIR application must be updated so that visitors are taken directly to the page of Adobe AIR app on the Amazon Appstore. The download URL is http://www.amazon.com/gp/mas/dl/android?p=com.adobe.air steps: I) launch the application. (II) press 'Install' > > «Appstore» Observe that the application accesses the home page of the Amazon app store for Adobe Air installation.

  I'm guess I could change this in my xml file:

  I change the URL in this line than what they provided (http://www.amazon.com/gp/mas/dl/android?p=com.adobe.air):

  <? XML version = "1.0" encoding = "UTF-8" standalone = 'no '? >

  " < application xmlns =" http://ns.Adobe.com/air/application/2.6 ">

  However, when it is published it always changes it back to the old address. How to prevent this?

  Thank you.

  I think I found the couresty of Benny 7500 response on August 11, 2011 09:18.

  For me the work of editing the file Markets.xml to:

  "C:\Program Files\Adobe\Adobe Flash CS5.5\en_US\Configuration\Android\Markets.xml"

  and the replacement of key of Amazon Appstore

  http://www.Amazon.com/GP/MAS/DL/Android?p=com.Adobe.air"/ >

  That's all!