This document contains the current known issues for Adobe Flash Professional CS5.5. If you have further questions that this document does not answer, see the Flash Help and Support page.
- On Mac OS, when shortcuts for tools are started with ATOK IME on, Flash Professional CS5.5 tools don't work on the Stage.
- Saving a CS4 file in CS5 and reopening it in CS5 sometimes results in a "Flash cannot parse this document" error. To solve this issue, update your Flash Professional installation to the most recent update.
- Flash Professional CS5.5 crashes when converting more than two symbols into a symbol. This issue usually happens as a result of the computer being out of memory. To solve this issue, free up available memory. To free up memory, try restarting the system, or closing other open applications or documents. If neither of these options work, add more RAM to the system.
- In Flash Professional CS5 & CS5.5, some JPG/JPEG files will disappear from the Stage and appear blank in the library after saving. o solve this issue, update your Flash Professional installation to the most recent update.
- When a child symbol is used in multiple symbols, existing symbol content is deleted after performing a copy and paste action. This issue only happens if the symbol is not loaded (on the stage or in library) before copy and paste. To work around this issue, load the symbol by clicking it once in the library or adding it to the stage before copying and pasting.
- Custom default color palettes cannot be saved when saving as CS5.5 format (compressed and uncompressed). To work around this issue, save as CS5 first and then resave as CS5.5.
- Flash CS5 files sometimes don't open if they contain components in the Library that have been moved to a folder other than where originally created. (For example, the issue occurs when components are dragged from the Components panel into the Library panel).
- When using Flash CS5 and CS5.5, symbols saved in XFL format (compressed or uncompressed) are corrupted if its name has a special character. Refrain from using special characters in symbol names.
- Windows only: When using compressed XFL files, data loss can occur when saving as a hidden file. To solve this issue, use hidden folders instead of hidden files.
- Windows only: You can't save a FLA file in a Network/Desktop folder a second time after receiving an "unable to save" error message. To solve this issue, save the file as a FLA file instead.
- An error occurs when you publish an AIR file if a surrogate pair Unicode character appears in the path to or filename of FLA file. The error also occurs when a surrogate pair Unicode character appears in the file or OS login name.
- When you use a Japanese Device font in a TLF vertical text field, Japanese symbols appear rotated on the Android runtime and AIR2.6.
- (Windows) When you publish an AIR for iOS application, an error occurs when the path to the FLA file includes a double-byte or high-ASCII character (not including the FLA filename).
- When you use a double-byte or high-ASCII character in the filename or path to any included file of an AIR for Android FLA file, the .apk file isn't created.
- When you using the Japanese language environment of Mac OS, Flash crashes when a high-ASCII-European character is used in the AIR for Android (.apk) output filename.
- FLA does not open due to ETX characters in TLF markup. To solve this issue, update your Flash Professional installation to the most recent update.