1 person found this helpful
AIR had a security restriction that you can only load modules from the app directory (i.e. the same folder the application was installed to). However they added a loadBytes(...) function to allow a module to be loaded that had been downloaded. I don't know if this was added to the resource stuff however.
You cannot blindly add modules to the app directory either (at least ones that weren't part of the initial install) as the AIR runtime tries to work out from the directory whether it needs to update itself, and adding files in there confuses it (so say Adobe).
I actually think you might be stuffed unless you create a new version of your AIR application with the new resource bundle, and distribute it as an update.
Tel: 01382 564343
Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ
Registered Number: 1788577
Registered in the UK
Visit our Internet Web site at www.inps.co.uk
The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact email@example.com
ignore this message, see my other post.
You can load a module from any location if you load the bytes of the module instead of just using loadResourceModule()
Aaron Hardy wrote a class that can be used to load the bytes easily. Check out this link: http://aaronhardy.com/flex/loading-a-remote-style-swf/
I know that it is for loading style modules but you can use it to load other types of modules as well.
I just did a post on it here: http://blog.mediarain.com/2009/08/flex-loading-remote-modules-throws-the-following-error-u nable-to-load-resource-module-from/?preview=true&preview_id=168&preview_nonce=75366e9b0d
Hopefully this solves your problem.