But IIRC, even on Android, SWFs loaded from outside the application
directory are loaded into a separate security domain, and there is no way
to tell them to load into your security domain which you need for modules
to work.  And really, it is theoretically unsafe to do so, as you cannot
trust that someone didn't replace that SWF with an evil SWF designed to
steal passwords and other data.

That said, the common workaround is to load the SWF as a ByteAray using
URLLoader, then hopefully do something to verify that it isn't an evil
SWF, then use the loadBytes capability to load the module.

-Alex

On 10/25/13 4:22 AM, "DarkStone" <darkst...@163.com> wrote:

>Hi Dmitriy,
>
>Well, you can load external swfs in AIR on iOS, but you need to meet the
>following restrictions:
>
>1. You must use AIR 3.7 or later version of AIR SDK.
>
>2. All the external swfs must be declared in a xml file and in a txt file
>in your project.
>
>3. Application swf and other swfs (external swfs) must be compiled into a
>single IPA file.
>
>4. You need to manually compile all the stuff above into IPA using
>compile line commands, cuz Flash Builder 4.7 does not support it yet.
>
>Here is the detail of how to do it (search for "Externally hosting
>secondary swf files (iOS)"):
>http://helpx.adobe.com/en/flash-player/release-note/fp_117_air_37_release_
>notes.html
>
>On Android platform, however, there is no limit to it, cuz Android is....
>well you know it.
>
>
>
>DarkStone
>2013-10-25
>At 2013-10-25 15:16:31,"Dmitriy Resnyanskiy" <zubo...@gmail.com> wrote:
>>Hi, Apache!
>>
>>We are developing a mobile AIR application for Android and iOS. Our main
>>application should be able to load the module SWF (compiled spark Module
>>or
>>sub-appplication), or the module styles (compiled CSS file) from any
>>directory. For example, here:
>>*File.applicationStorageDirectory.nativePath*.
>>We have carefully studied this issue and concluded that it was
>>impossible.
>>Is it really so? Please explain. Thank you.
>>
>>*P.S. We use Apache Flex 4.10 and AIR 3.8*
>

Reply via email to