-
Notifications
You must be signed in to change notification settings - Fork 27
Common Issues And Solutions
You may encounter a situation where your pages aren't showing up in the context menu even though menu="true". The reason is because there are some words that are not allowed, the most common one brought up is "About".
The complete list of what is not allowed can be found on this Adobe web page. If you turn a page node on for the menu and it has one of these titles, it won't show up.
You cannot have non-Latin characters in urls with SWFAddress, so if you have non-Latin characters in your page titles, use the route attribute on your page nodes to create a valid url while maintaining your page titles.
After updating an existing Gaia project, if you see compile and/or runtime errors about missing classes or invalid properties, the solution is to make sure you always delete your ASO files after updating. You can do this under the menu Control > Delete ASO Files.
Coercion errors occur when the Flash file in question did not compile correctly. This commonly happens when you make custom preloaders based on the PreloaderScaffold or your page.fla has an error in it when it compiled. You have to make sure that the preload.fla/page.fla file compiles without errors or Flash won't be able to treat it as the proper class (IPreloader/IPage). This is always because the Flash file did not compile correctly.
You will see >>> INTERRUPT IN <<< if a transitioning page did not fire its transitionOutComplete() method correctly.
You will see >>> INTERRUPT OUT <<< if a transitioning page did not fire its transitionInComplete() method correctly.
You will see >>> INTERRUPT CROSS <<< if there is some combination of the above or you are using Cross Flow.
You'll have to figure out which page is failing to call its transition complete method.
If you make a custom preloader, you might also have to check if the preloader is firing its complete method correctly, as well.
This is a common problem for international users, and is caused by a bug in the Adobe Extension Manager. The solution can be found on this thread in the forum
Read Grant Skinner's article on this subject if you are developing with Gaia AS3.
When declaring instances in your classes that are put on the stage in the Flash IDE, you have to make sure you declare them as public. This is an AS3 requirement, but enough people get tripped up by it that it was worth posting here.
This happens when you pass TweenLite a Gaia interface, like IMovieClip or IDisplayObject. The solution is to either not wrap the asset in its interface, or pass the .content property of the asset instead.
This is due to how AS3's ApplicationDomain works. The simplest solution is to reference your static class in Main.as. I usually set a public static var init:Boolean = true from Main.as. The more advanced solution is to use domain="current" on all of the pages in the site.xml that need to share those static variables, or in the site node. Check the Site XML documentation for more information on the domain attribute and how to use it.