I am assuming you are using flash.filesystem.File.browseForOpenMultiple. That is an API for the AIR runtime and not Flex specifically.
When you run your app in development mode, you may be using ADL (Air Debug Launcher) or maybe you fully publish it as a .AIR file or .EXE/.DMG I think if you use ADL, you will run the ADL in the AIR SDK for the Flex SDK. For Adobe Flex 4.6, I think it was AIR 3.1 or something like that. For Apache Flex 12 and 13 I think it is something like AIR 4.0 or AIR 14. Adobe AIR tries to maintain old behavior based on a version number written into the SWF that AIR runs. The version number is different in each Flex SDK and defaults to the version of the AIR SDK you are using. Further, AIR also chooses different code paths based on the namespace in the -app.xml file that goes along with your SWF. So, there are a lot of variables that can cause your app to choose different code paths in different versions of the AIR runtime, and it could be that there is a bug in newer versions of AIR or you are just getting unlucky and the bug has always been there but enough has changed at runtime that you are hitting it now. If you do a google search, folks have been complaining about browseForOpenMultiple for several years now. Also, it may not be a bug per-se: sometimes I think more recent versions of AIR get tighter security and don’t allow certain things to happen. A test you can run is to build a simple non-Flex app that uses browseForOpenMultiple and see if you can reproduce the problem without Flex. If you can, file a bug at bugbase.adobe.com. You can also try using Apache Flex 12 or 13 with the same version of AIR that Adobe Flex 4.6 used, and/or try setting SWF versions and -app.xml namespaces to make AIR use the same code paths that Adobe Flex 4.6 is using. -Alex On 1/6/15, 9:40 AM, "aabarreiros" <aabarrei...@gmail.com> wrote: >Hi Alex, > >And first of all, thank you for your reply, could you please be more >specific, i didn't understand your point. I set the application to be >compiled with the latest sdk 13 and with the default 4.6.0 that comes with >the flashbuilder installation. > >Best Regards >Alexandre > >2015-01-06 17:26 GMT+00:00 Alex Harui [via Apache Flex Development] < >ml-node+s2333347n44181...@n4.nabble.com>: > >> Different SDKs have different default SWF versions. Adobe 4.6 also >>comes >> with an older Adobe AIR SDK embedded in it. I’m wondering if your >>problem >> is related to the version of AIR or the SWF version that causes AIR to >> take different code paths. >> >> -Alex >> >> On 1/6/15, 6:27 AM, "aabarreiros" <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=44181&i=0>> wrote: >> >> >Hi All, >> > >> >I'm having a problem when browseForOpenMultiple if i select more than >>300 >> >images, i got a system error in this case a windows error saying my >> >application just crash. I made several test and with the sdk 12 and 13 >>i >> >got >> >this error, but if i tried with the adobe 4.6.0 it works without any >> >trouble. And this issue it just happen in adobe air, if i made the same >> >code >> >in browser (flex) it works without any trouble and import the same >>images >> >fine. >> > >> >A quick example is: >> > >> ><?xml version="1.0" encoding="utf-8"?> >> ><s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"; >> > xmlns:s="library://ns.adobe.com/flex/spark" >> > xmlns:mx="library://ns.adobe.com/flex/mx" >> >creationComplete="init()"> >> > <fx:Script> >> > >> > </fx:Script> >> ></s:WindowedApplication> >> > >> >Does anyone got a workaround for this? I got this on a customer >> >application >> >and i'm receiving a lot of complains. >> > >> >Thanks in advance for all the help. >> > >> >Best Regards >> >Alexandre Barreiros >> > >> > >> > >> >-- >> >View this message in context: >> > >> >>http://apache-flex-development.2333347.n4.nabble.com/problem-with-browseF >>o >> >rOpenMultiple-tp44179.html >> >Sent from the Apache Flex Development mailing list archive at >>Nabble.com. >> >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the >>discussion >> below: >> >> >>http://apache-flex-development.2333347.n4.nabble.com/problem-with-browseF >>orOpenMultiple-tp44179p44181.html >> To unsubscribe from problem with browseForOpenMultiple, click here >> >><http://apache-flex-development.2333347.n4.nabble.com/template/NamlServle >>t.jtp?macro=unsubscribe_by_code&node=44179&code=YWFiYXJyZWlyb3NAZ21haWwuY >>29tfDQ0MTc5fC0zOTI2MTUwODA=> >> . >> NAML >> >><http://apache-flex-development.2333347.n4.nabble.com/template/NamlServle >>t.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabbl >>e.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace >>-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21 >>nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_ema >>il%21nabble%3Aemail.naml> >> > > > > >-- >View this message in context: >http://apache-flex-development.2333347.n4.nabble.com/problem-with-browseFo >rOpenMultiple-tp44179p44182.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
