How to work with the Flash Lite 3.x playback security settings.
Problem
Content that loads external data or assets doesn't work when played back in Flash Lite 3.*
Solution
Go to the publish settings and change the local playback security settings to match the call being made (either remote or local).
Detailed explanation
Flash Lite 3.x has playback security which makes it the same as Flash Players 8+. There are several confusing aspects to this though because Flash Lite doesn't operate in the same context as a desktop computer.
PLAYBACK SECURTIY
Playback security is something you need to know about if you load or send anything external to or from your swf. So for example data from a local text file or another swf file. The only exception to this is Shared Objects. These are treated as native to the SWF and therefore safe.
If you only load data from one source, either local or remote, then its easy to work with the security settings. In the publish settings tab at the bottom of the Flash IDE is a dropdown list called 'local playback security'. This is where you determine the playback security. The default is local access only, so if your swf file only accesses local data use this setting. If your swf accesses remote data then change the setting to 'remote access only'.
If your swf accesses both local and remote data then forget about the publish settings because you can't set both local and remote access for a swf. What you will need to do is install your application into a folder called 'trusted' within the Flash Lite player directory. This will allow your swf to load data from any local or remote destination.
Although this seems like a bit of a headache its actually not entirely unreasonable. If you are loading local data then its likely that its your applications own data, for example additional swf files, text files etc. In order to install this data on the phone you will need to have some kind of installation process, so creating a 'trusted' folder shouldn't be to difficult.
Note that there is no guarantee that phone manufacturers will implement the 'trusted' folder security.
Be aware that neither Device Central or the Flash IDE currently enforce the new security measures, so you won't realise any issues until you test on the device.
PLAYBACK SECURTIY
Playback security is something you need to know about if you load or send anything external to or from your swf. So for example data from a local text file or another swf file. The only exception to this is Shared Objects. These are treated as native to the SWF and therefore safe.
If you only load data from one source, either local or remote, then its easy to work with the security settings. In the publish settings tab at the bottom of the Flash IDE is a dropdown list called 'local playback security'. This is where you determine the playback security. The default is local access only, so if your swf file only accesses local data use this setting. If your swf accesses remote data then change the setting to 'remote access only'.
If your swf accesses both local and remote data then forget about the publish settings because you can't set both local and remote access for a swf. What you will need to do is install your application into a folder called 'trusted' within the Flash Lite player directory. This will allow your swf to load data from any local or remote destination.
Although this seems like a bit of a headache its actually not entirely unreasonable. If you are loading local data then its likely that its your applications own data, for example additional swf files, text files etc. In order to install this data on the phone you will need to have some kind of installation process, so creating a 'trusted' folder shouldn't be to difficult.
Note that there is no guarantee that phone manufacturers will implement the 'trusted' folder security.
Be aware that neither Device Central or the Flash IDE currently enforce the new security measures, so you won't realise any issues until you test on the device.
+
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License. Permissions beyond the scope of this license, pertaining to the examples of code included within this work are available at Adobe.
Report abuse
