![]() ![]() Apparently, you need the thing there that makes the difference. I still have other instructions trace() in there, that cause no problems at all. I am a little amazed as to why this has caused the problem. I had to then back-track through all my changes to see what caused and found it was her. After this change, the app worked after installation. The event is a LoaderEvent, of the LoaderMax lib. While doing this, I decided to remove a trace() statement I had, or rather modify so that it used the recorder. I thought that maybe some of the assets are not loaded correctly, so I went through and put in loads of logging, using the SOS Max Logger. I got an error when using the ADL, "original content not found. I tried a few other things, such as the application of AIR through the ADL, to see if that would produce the error log that you describe. I tried the thing you suggested, but strangely, no record of this name (in the other thread, you're connected to you) has existed before or after that the app crashed. Someone at - it ideas, I'm totally stuck. ![]() The only slightly suspicious entries were those with "NAME NOT FOUND" and "OPLOCK NOT GRANTED", but there was no included info that gave me ideas on what is causing the problem. I tried to use Process Monitor to see if errors occur when the application starts, but I can't really do all that much sense of what he reports. Which is all simply because I am using an AIR API call that is not taken in charge by Flash Player. events::NativeWindowBoundsEvent is not found. I tried to open the SWF file that is included in the debug Flash Player, but it stops on an exception to this: AIR TEST SECURE BROWSER DOWNLOAD APPLICATION EXE .EXEexe file opens the window app momentarily, and then it closes instantly without errors or exceptions are thrown. I installed the application to a directory on my desk, and no errors have been launched during the installation.ĭouble click on the. I built the app in Flash Builder and exported using the 'Export Release Build' dialogue I chose 'Package signed AIR', everything went well there. I built and depolyed AIR apps before and never had any problems, but the app I'm working on right now really causing me trouble. Application of AIR closes instantly at the opening
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |