Skip to main content
chaosdev
Participant
Oct 18, 2014 10:07 AM UTC
Answered

App crash if not add -useLegacyAOT yes in Flash builder

hi,

i found the same issue, i use fb4.7 and package ios app.(doesn't use adt tool),if i don't add param -useLegacyAOT yes, the app will crash on phone.(with air15.0.328 beta).i found maybe Sound.play crash app.When i add -useLegacyAOT yes,it will run well,but package time is too long.

Someone can share some light about this issue?

This topic is closed to new replies. Start a new post to keep the conversation going.
Govind11519869Correct answer
Adobe Employee
Oct 28, 2014 4:57 AM UTC

Just as an idea: could this be caused by the usage of custom metadata in parsley?


Hi,

We have seen this problem and we are working on it. As a workaround, try to recompile Parsley with latest Flash builder. That should fix the issue.

Thanks

Govinda Gupta

View reply

13 replies

soccerob
Participant
Nov 11, 2014 3:52 AM UTC

has anyone been able to compile for iOS (without random crashes) without using the legacy compiler? i'm on build 349 and still seeing problems.

Translate
Colin Holgate
Colin Holgate
Inspiring
Nov 11, 2014 12:05 PM UTC

If you're using certain ANEs, such as the GAForFlash one, then yes, it will crash when you run the app. In general using the faster compiler works, and in some cases using the legacy on can fail.

Translate
tomaugerdotcom
Known Participant
Feb 18, 2015 9:48 PM UTC

We're into 2015 now and this is still an issue, using AIR 16 and FB 4.7 or Flash CC 2014. Would love to hear some movement forward on this issue. See: AIR SDK bug: Fast AOT compilation causes app crash and Bug#3942042 - Application crash ONLY when using new fast AOT

Translate
cgascons
Participating Frequently
Oct 22, 2014 3:00 PM UTC

Same problem here, it only works when using the -useLegacyAOT param set to "yes", as a side note, it works fine without the parameter when not building a release version. I'm using the AIR 15 beta released on the 17th October.

Translate
    iam0815
    Participating Frequently
    Oct 18, 2014 4:37 PM UTC

    Same issue on an application using parsley for me. While initialising the application on the first parsley operations the app crashes with an error. Rebuilding the parsley library with the current sdk won't help at all.

    Translate
    Colin Holgate
    Colin Holgate
    Inspiring
    Oct 18, 2014 6:22 PM UTC

    When you talked about the current SDK, did you mean the 302 that was around for a couple of weeks, or 328 that came out today?

    Translate
    iam0815
    Participating Frequently
    Oct 19, 2014 8:10 AM UTC

    Well - I tested it with the release version and with every Beta released since the release of the final - even the current. No one worked at all. The parsley lib was not recompiled with the current beta, it was compiled with the previous beta. There is also an entry in the Air Bugbase about that problem from me.

    Translate
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices