7 Replies Latest reply: Oct 16, 2014 11:35 AM by chaosdev

Weird problem when -useLegacyAOT no

Ubika23 Jan 24, 2014 3:18 AM

Hi,

I'm trying to compile my mobile app with the new -useLegacyAOT no flag.

Compilation goes well and when installing and launching the app (release build) on iPhone 5 with iOS 7 I get the following messages on Scout:

Adobe iOS

External interface not available

0 - Init

Error: ga.js not found, be sure to check if

is included in the HTML.

And then an error is thrown and obviously the app crashes.

When I compile without the new flag I get the following expected output and the app starts flawlesly:

Adobe iOS

External interface not available

0 - Init

Init Database

...

(And the rest of the trace statements from the init)

So the ga class fails only when I use -useLegacyAOT no.

I use "AS3" mode to initialize the tracker so I wonder why it's trying to find the ga.js file when the new compiler is used...

Someone can share some light about this issue?

1. Re: Weird problem when -useLegacyAOT no

amanglic Jan 27, 2014 1:14 AM (in response to Ubika23)

Hi,

Could you please provide us the sample application, this would help us in reproducing the issue quickly at our end.

Thanks for reporting,
Ankit
Like Show 0 Likes (0)

Actions
2. Re: Weird problem when -useLegacyAOT no

MatthewVisser Oct 6, 2014 3:31 PM (in response to amanglic)

I'm getting this same issue.

Error: Error: ga.js not found, be sure to check if is included in the HTML.
Error: ga.js not found, be sure to check if is included in the HTML. at com.google.analytics.v4::Bridge() at com.google.analytics::GATracker/_bridgeFactory() at com.google.analytics::GATracker/_factory() at com.google.analytics::GATracker() at com.fisherpaykel.services::GoogleAnalyticsTracker() at com.fisherpaykel::Main/addedToStageHandler() at starling.events::EventDispatcher/invokeEvent() at starling.events::EventDispatcher/dispatchEvent() at starling.display::DisplayObject/dispatchEvent() at starling.display::DisplayObjectContainer/broadcastEvent() at starling.display::DisplayObjectContainer/broadcastEventWith() at starling.display::DisplayObjectContainer/addChildAt() at starling.core::Starling/initializeRoot() at starling.core::Starling/initialize() at starling.core::Starling/onContextCreated()

I just went from AIR 14 to AIR 15. Tried compiling my app and it wouldn't start. Looked in Flox and could see the above error. It was stopping on the Google Analytics stuff.
Like Show 1 Like (1)

Actions
3. Re: Weird problem when -useLegacyAOT no

Kobydo2 Oct 13, 2014 5:25 AM (in response to MatthewVisser)

I'm getting the same error since moving to AIR 15:
"ga.js not found, be sure to check if
<script src=\"http://www.google-analytics.com/ga.js\"></script>
is included in the HTML."
Like Show 0 Likes (0)

Actions
4. Re: Weird problem when -useLegacyAOT no

Kobydo2 Oct 13, 2014 5:27 AM (in response to amanglic)

This is an URGENT issue in AIR 15.0. Right now GA does not work in this framework.
Like Show 0 Likes (0)

Actions
5. Re: Weird problem when -useLegacyAOT no

Jitender thakur Oct 13, 2014 6:01 AM (in response to Kobydo2)

Hi,

Thanks for reporting the problem, but we haven't encountered any such issue. Iit will be great if you could provide us sample app or code so that we can reproduce the problem at our end.

Regards,
Jitender
Like Show 0 Likes (0)

Actions
6. Re: Weird problem when -useLegacyAOT no

Colin Holgate Oct 13, 2014 6:04 AM (in response to Jitender thakur)

It's common knowledge that some ANEs (or SWCs perhaps) are not compatible with the new compiler. I'm pretty sure that some of your colleagues, or your bug reports, have a note about GAForFlash not working.
Like Show 0 Likes (0)

Actions
7. Re: Weird problem when -useLegacyAOT no

chaosdev Oct 16, 2014 11:35 AM (in response to Ubika23)

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

Actions