Probably because it's trying to work out if it needs to update itself.
By the sounds of things, you are keeping all the assets in the same folder as the application?
Try moving the assets out into the application storage directory instead.
Thanks for the reply. The problem with having the assets in the app-storage folder is that I soon run into the well documented security sandbox issues. The main AIR application loads a swf, which in turn loads many other swf, image and mp3 assets. If I move the swf to app-storage I can still load it into the application sandbox using readBytes and allowLoadBytesCodeExecution, but it then expects all its assets to also be in the application folder, but they aren't - they're still in app-storage.
I still think it's odd that AIR would want to scan my application folder. Surely the update framework just compares the application version strings to decide if it needs to do anything.
So, the question still is, how do I stop AIR taking 90 seconds to scan my application folder. Alternatively, how can I get the dynamically loaded SWF in app-storage to locate it's assets?
1 person found this helpful
" still think it's odd that AIR would want to scan my application folder. Surely the update framework just compares the application version strings to decide if it needs to do anything."
You'd think so, but according to Adobe, adding any files into the application directory may mess up the updater when it works out if a new version is required (I think one of the AIR engineers stated that on Flexcoders). The implication being that it checks all the files in the directory...
Can you embed all the assets into a swf and load them that way?
Well, I've spent a bit longer looking at this now, and the problem appears to lie with my encrypted local store. The first thing that happens is for the app to read the product key from the ELS. But, it fails (for some unknown reason). So, the app seems to hang there for 90 seconds until it eventually renders the welcome screen. If I remove the assets folder it still fails to read from the ELS, but only takes a couple of seconds to start the welcome screen. This is where the scanning of the application folder seems to come into play, because if I remove the code which reads from the ELS the app starts within 2 seconds whether the asset folder is there or not.
I think the slow startup and the scanning of the assets folder are just symptoms of a different problem, i.e. a problem with the ELS. I don't have the same problem with my development environment though - it's only when I test deploy the application.
Thanks for your help on this problem EgorKDie. I think I should be able to resolve it once I can sort out why the ELS is being awkward.
No problems, just make sure you post the solution to the ELS issue when you find out what the problem is, just so the thread is complete!
You've got yourself a doozy there, so good luck!
Did you ever fix this in your app, PauloBonza? I'm running into the same thing.