I have spent some hours working on debugging my code and this
is the first time I think I found a bug that isn't mine. It appears
to be a bug with Flash player 9 on Mac OS X (10.5). In short, file
selections fail.
The same .swf file works fine on windows and worked on OS
10.49 before I upgraded a few days ago. Last night I began working
on the uploader portion of an application I am building and could
not figure out why the uploader class I made last week decided to
not work at all this week. After a good night's rest and an early
start I began my debugging effort again, this time copying the
compiled .swf file to my windows machine and testing it there (but
only after another hour or so of googling for better examples). It
worked. I tried the same file on the mac and it failed. After
testing the file in Firefox 2, Safari 3, and Opera, I decided that
it must be a bug introduced by the release of the new Mac OS. At
the time I wasn't sure exactly what the problem was but with a
little digging I discovered that the root of the problem (as far as
Flex developers are concerned) lies in the failure of the user's
file selection to trigger an event.
If anyone would like to try this out please use the link
below. It is not my example but it produces the same error that my
code produces. If you try on a non-mac OS 10.5 system you will be
able to select files and they will be added to the list. On a mac
10.5 system you will be able to select files but they will not
appear in the file list.
http://labs.newmediateam.com/Multifileupload/FileUpload.htmlURGENT!!! Flex Event error - Mac OS X...
I have exactly the same problem only my application is in
production. It works on Win XP, Vista and Tiger. No go on Leopard.
The SELECT event doesn't fire after you select a file. I'm
surprised there isn't more of a panic on this or the Flash
forum.URGENT!!! Flex Event error - Mac OS X...
As am I. I originally left out the ''URGENT!!!'' portion of the
post title... and after a short consideration re-titled it to
attract more attention. As I read earlier today, Apple announced on
Tuesday (10-30-2007) that they had sold over 2 MILLION copies of
the new OS. Anyone, such as yourself, with production applications
could be in a WORLD of hurt real quick with a bug like this on the
loose. I submitted a bug report just before I made this post so we
will see if it starts to get some attention. Better yet, let's see
if it gets the attention it really deserves. I would say that
something like this is HIGH priority.
Where did you post the bug report? I'd like to post one
too.
I posted the bug report here:
http://bugs.adobe.com/flex/
I wasn't sure exactly what to post it as so I put it under
''Flex'' and then chose ''Events''. Its actually kind of confusing how
they have it set up. At any rate - I just checked it and apparently
someone actually looked at it.... The ''resolution'' is a bit cryptic
though. You can see the report and comments here:
https://bugs.adobe.com/jira/browse/SDK-13254
From what I can tell it seems that they determined it is a
Flash player bug (something I actually suspected myself but didn't
really have the capability to test.) Seems that they may have
reposted this error on the Flash bug report system... not sure
though.
I saw the report. I wonder how a new version of Flash player
will get distributed... And if users have to initiate the update or
if it's automatic.
Could you post a link to the post you saw on the Flash
player? I'd like to see it. It will most likely need to be user
initiated.... and that is kind of a problem since most people will
not be aware that there is an update, much less the fact that they
might need the update. I have a feeling that those such as yourself
will need to manually raise the required version of flash player so
that users are prompted to download the new version. It would be
even better if they gave us the code to target mac 10.5 users for
such a prompt. At the very least the script should target macs and
not windows. The hassle of updating should be reduced to the
smallest number possible to avoid large numbers of frustrated
customers.
I meant I saw your report and the fact that they had a opened
a Flash Player bug. I have no idea how to access the Flash bug
database.
I guess incrementing the required Flash version won't be too
bad, but annoying for all users unless we can figure out a way to
identify Leopard users.
Ah, sorry I misunderstood. I also got an email from Robert,
the one listed on the bug report. He asked me to check the version
of the Flash player I was using and let him know. Yesterday I was
using 9,0,28,0 and so when I checked my version on the Flash player
update site I realized that 9,0,47,0 is actually the latest version
so I upgraded and ran some tests with that as well this morning. No
luck. I replied to his email and let him know the versions I used
to try it with.
And yes, it will be a pain for all users unless there is a
way to target mac users. Preferably only those that the problem
affects.
Thanks for testing. If you hear of a resolution from Robert
please let me know.
No problem. My days are filled with tests and debugging. And
if I hear of a solution or a Flash player update that covers this
issue I most certainly will let you know.
They just released today a new version of the Flash Player
for OS X that fixes the upload problem... I can't seem to track the
debugger version though (still stuck at 9.0.47.0):
http://www.versiontracker.com/dyn/moreinfo/macosx/11622
Thanks for the update on the player that addresses. However,
I would like to point out that it appears to be a beta release
(it's marked Beta on the page you linked to.) The link to the
official Adobe flash player download page is here:
http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFl ash
Anyone else who knows anything please keep us informed. (Even
if it is beta release stuff - we can still use it to get our
applications back on their feet again)
I haven't heard anything else from Robert on the bug report I
posted but I will let you know if anything does show up.
Subscribe to:
Post Comments
(Atom)
No comments:
Post a Comment