AIR 15 Beta - New Improved compiler engine for iOS is now Default.

Vontre

I may have actually figured out what's wrong with FB 4.7 ... it seems it doesn't like it if you embed the same file in multiple places (this was just a 3 line versioning file, so ya know). FB 4.6 was fine with this. I dunno if this will help anyone but just in case!

NagRock

Sorry for offtopic but we are waiting for Workers on iOS not for fast building. We can't us Workers on android without workers on iOS - this results in two different code for two OS.

eRistocracy

@NagRock couldn't express it better. I don't care how much it takes to compile release version on devices. I prefer reliability and bugs-free compiler with workers support for all platforms, before I start using them...

Crossplatform MEANS Crosplatform!!!

santanu4ver

It looks like they're hurry to push the release without a valid/stable Q/A test pass.

santanu4ver

Its good that they're following the issue with AdobeAIR‬ 15.0.0.258 Beta Release:

Known Issues

iOS Fast Packager - FPS reduces for Feathers Components Explorer app on iPad when packaged with fast packager. (3776055)

I wonder how the performance with Flex SDK, though.

youmex

This issue has been fixed in an internal build. I guess it will be released soon. The guys at adobe put a lot of effort in fixing this and it is a pleasure to work with them. So you can expect 1:1 performance like in the old compiler, although it only takes seconds to compile. Great job!

eRistocracy

Great news in AS3 world going on! Someone mentioned that when everything will be moved to C++ compiler, it will be able to spit out anything. Is that anywhere around the truth?

What about Windows Phone support?

el_alien

What about Windows Phone support?

<<< Yes, can we get a info on that? Im making more mobile apps than ever and im actually thinking about leaving WP because i cant showcase my own work withouth an aditional iPad...

santanu4ver

BETA updated: http://blogs.adobe.com/labs/archives/2014/09/updated-flash-player-15-and-air-15-betas-available-on-adobe-labs-6.html, and Fast Packager frame-drop issue taken to 'fixed' status.

[3776055][Fast Packager] FPS reduces for Feathers Components Explorer app on iPad when packaged with fast packager

http://labsdownload.adobe.com/pub/labs/flashruntimes/shared/air15_flashplayer15_releasenotes.pdf

tsangwailam

Anyone try new AIR 15 and useLegacyAOT=no ? Do you have any problem. I am trying and seem it is fine. But i want to confirm if any other issue using it.

joshtynjala

I just tested the new beta today, and as far as I can tell, the performance issue(s) seems to be fixed.

matulk

Hello everyone,

we are about to submit our app to the Apple App store this weekend. I would rather use the old compiler until I am sure the new one is stable.

Since iOS 8 is out now: does anybody know if it is necessary to use the new compiler for not getting rejected?

joshtynjala

I think you need to use the AIR beta SDK from Adobe Labs to submit right now because it's the only current version that includes the required fixes for iOS 8. However, yes, you can still tell it to use the legacy packager.

matulk

alright.. thanks josh.

I downloaded the latest beta already. Compiling with useLegacyAOT=yes. Let's hope for the best 😉

Cheers

tsangwailam

I try the AIR 15 with useLegacyAOT=no when package a release build. Some apps still crash when launch. No problem with useLegacyAOT=yes.

numa

Like @tsangwailam, some apps crash or bugs appear with the release build and the new (default) compiler. I had to use useLegacyAOT=yes.
For FDT users, this is the way I use useLegacyAOT in FDT http://bugs.powerflasher.com/jira/browse/FDT-3295

Dennis

I had a lot of problems with the new compiler. AIR 15.0.0.356 SDK, FB 4.7. After packaging my App with the new compiler and SDK it stopped working with Testflight, Apple rejected it because it was crashing in iOS 8.1 which i couldnt recreate because i couldnt install the build via (the old) Testflight. Then when i finally got the app on an actual iOS 8.1 device (trough Apples internal Testing in iTunesConnect) i noticed it was indeed crashing immediately. (But not in the simulator and not on <8.1) So not easy to debug. So i am now back to useLegacyAOT=yes and everything is back to normal, but should that happen in an AIR 15 SDK stable release version?

stortof

I tried today to publish with AIR 15.0.0.356 and useLegacyAOT=no, and my App crash on start...in fact it doesn't really crash but it seems it goes in background and when I tried to relaunch, it goes in background again...strange.

I don't what could be the cause of the problem...any idea ?

No problem with useLegacyAOT=yes...

joshtynjala

I don't what could be the cause of the problem...any idea ?

The best way to find the source of crashes and weird things that don't give you a runtime error in the debugger is to start removing/disabling parts of your code until it starts working properly again. Maybe you find that it works after you remove a specific class. Next, you might put the class back in, but then you start commenting out functions in that class to narrow it down even more.

If you can get it as specific as possible and easily reproducible, that's the start of a great bug report to submit to Adobe.

stortof

OK, so I investigate a little and the problem is related to TextField.

Each time I create a new Textfield instance...

var txt:starling.text.TextField = new starling.text.TextField(txtWidth, txtHeight, txtLabel, txtEmbeddedFont, txtFontSize, txtColor);

...the app restarts and goes background.

Maybe it is related to the embedded status of the font but I must do further tests to confirm.

the font is embedded like this in a static Class:

[Embed(	source = "../../lib/fonts/tahoma.ttf",
	mimeType = "application/x-font-truetype",
	embedAsCFF = "false",
	fontFamily = "Tahoma")]
private static const Tahoma:Class;

Anyone has the same issue with TextField and/or embedded fonts ?

« Previous Page Next Page »