Closed GoogleCodeExporter closed 9 years ago
I've hit this issue too. This issue is bigger than it appears. The high level
view on this issue is that facebook-actionscript-api / facebook connect does
not work with IE browsers full stop.
Works fine in Chrome and latest ffox 3.6.12
I'd like to vote for this issue to be moved to priority blocker or critical as
this affects IE completely
Original comment by javagu...@yahoo.com
on 7 Nov 2010 at 8:35
There's a related bug entry on Facebook's Bug Tracker as well:
http://bugs.developers.facebook.net/show_bug.cgi?id=10631
As mentioned in the discussion there, the only reliable workaround currently is
to make you're Graph API requests using JavaScript on IE.
Attached is a basic patch that adds this ability to the
facebook-actionscript-api. It allows you to prefix the request method with "JS"
and the request will then be redirected through the JavaScript FB.api method
(e.g. using "JSGET" and "JSPOST" instead of "GET" and "POST").
Tested on IE6, IE7 and IE8. I was able to make a "/me" request successfully in
all cases, whereas the same call would fail before when it was being sent by
Flash.
Note that the implementation only supports the Graph API. Extending it to
support Rest API calls should be trivial, though. Also, file uploads cannot
work this way.
Original comment by adrian.s...@gmail.com
on 15 Nov 2010 at 8:50
Attachments:
Hi Adrian,
Thanks for the post! I was stoked that someone cracked this nut. However
after applying your diff, it still doesn't work for me :(
Details as follows:
- I'm using Flashplayer 10.1, and I've compiled facebook-actionscript-api trunk + your mods using flex 4.1 sdk
- I'm using running an isolated project based on examples here from Jeanette Stallons http://www.adobe.com/devnet/facebook.html
@Runtime
- Running from IE6, it hangs at XD Proxy window after logging in
- consequently, it never gets a chance to call FB.api calls w/ your new params etc.
I'll repost to facebook bug tracker as well -- still waiting for my
registration mail to come in.
Thanks and appreciate any input!
Original comment by javagu...@yahoo.com
on 17 Nov 2010 at 1:36
Are you sure that you changed the request method from GET to JSGET without
prefixing the request method with JS it won't work.
Original comment by wey...@gmail.com
on 22 Nov 2010 at 4:04
Hi weyert,
Yes, I mde the patch change and I debugged through the calls. The problem is
that FB.login doesn't route through using JSGET, and FB.login is where I am
hung now.
Perhaps I should re-post somewhere else; w/ facebook-actionscript-api my error
is now that XD Proxy window hangs after login
Original comment by javagu...@yahoo.com
on 2 Dec 2010 at 5:38
Attached is an updated version for the new 1.5 Graph API.
@javagu
FB.login is already done by the JavaScript API. My patch is for the #2032
stream error in IE when using SSL for API calls and doesn't change anything
about the login process.
Original comment by adrian.s...@gmail.com
on 14 Dec 2010 at 8:58
Attachments:
How did you get this to work? I am having the same trouble and I have tried to
implement it. Am I suppose to use JSEventListners now?
Original comment by kendall....@gmail.com
on 10 Feb 2011 at 3:23
Well I tried to get it to post using JSPOST....nothing! nice try though!
Original comment by kendall....@gmail.com
on 10 Feb 2011 at 4:06
I was using JSPOST to upload a photo...I guess this wouldn't work under the
circumstances...
Original comment by kendall....@gmail.com
on 10 Feb 2011 at 9:43
How to patch??
Original comment by chong.la...@gmail.com
on 12 Feb 2011 at 8:43
Having spent most of the day on this problem, we've found a 'slap yourself in
the face' solution to be to publish for flash player 10 as opposed to 9 (as we
had previously been doing). Seems to work perfectly in IE now. :(
Original comment by percype...@gmail.com
on 7 Mar 2011 at 4:58
[deleted comment]
I was also trying to find a solution but the only one is to publish it with
flash player 10..
Original comment by dcomp...@gmail.com
on 19 Mar 2011 at 9:21
FP10 solution is not working for me.
Original comment by ogun...@gmail.com
on 21 Apr 2011 at 10:31
I can't reproduce this issue on IE6 (Windows XP), IE7 (Windows Vista), or IE8
(Windows XP) using the FlashWebExample in the GraphAPI_Examples_1_6_1.zip.
Since this is such an old issue, and the reporter hasn't responded to any
comments, I am marking as WontFix. If anyone is still getting a stream error
for this, please start a new issue and we will address them individually.
Original comment by rovertn...@gmail.com
on 27 May 2011 at 9:00
I was facing same issue.Main reason of this issue is Flash Player version.
Use Flash Player 10+ FaceBookGraphApi SWC file is compatible with Flash Player
10.
This solution is only for who are using swc from GraphAPI_Examples_1_6_1.
Original comment by uddha...@gmail.com
on 25 Aug 2011 at 10:53
I am just now getting this issue when calling
Facebook.api("me",onMyDataReturned, null, URLRequestMethod.GET);
[IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2
text="Error #2032: Stream Error. URL:
https://graph.facebook.com/me?access%5Ftoken=AAACoZCcNhNtsBANrzR52spNm2DEAOawLYa
g8Stn3uakEpaU5OshlHZCdZABFnbX0AW0PZCUSBEIMszz7m4gtVzZATtZACbNNCpanuJ4sJ70AZDZD"]
Granted, the access token provides a failed error noting the access token has
expired, but it should still not throw a Stream error.
As a note, when I'm logged in, it seems Facebook API calls run fine. However,
when trying to launch Facebook with a stored access token if the user has
logged out, I initialize Facebook by passing said access token,
Facebook.init(APP_ID, onInit, {}, accessToken);
But I'm finding that when onInit is returned, Facebook.getAuthResponse() has no
expireDate nor does it have a uid. I tried adding status:true and oauth:true to
the options, but it made no difference. Is this somehow related?
Publishing to Flash 10.2 on Chrome, but using Flash Player 11.2 r202 plugin.
Original comment by ort...@gmail.com
on 13 Jul 2012 at 1:12
I should add I tried using the 1_8_1 Web swc and also compiling from Source
1_8_1. Same error.
Original comment by ort...@gmail.com
on 13 Jul 2012 at 1:14
Nevermind; I'm seeing now why it doesn't have a UID - looking through the
source code, I see that the access token passed to the init function does
nothing! It's not used in FBAS.init in any way - in fact, it gets immediately
replaced if FBAS.init() finds another active session. I was under the
impression it would assist in OAuth 2.0?
I then have to wonder what the point of including the access_token in
Facebook.init if it doesn't seem to have an actual logistical use.
Anyway, I manually "assumed" that I had the appropriate access token,
expiration date and User ID, but it seems calls I attempt to make simply return
a steam error instead of parsing the error message included in the response.
Original comment by ort...@gmail.com
on 13 Jul 2012 at 4:04
I was getting this error when trying to do FacebookMobile.login and was getting
the same 2032 URLLoader error. Turns out this error is due to facebook blocking
your device/pc for numerous connection attempts. I was confirmed this by
reading other forums and by doing a simple test of the same login procedure
from a different device, and it worked there.
Original comment by christia...@gmail.com
on 2 Aug 2012 at 2:35
Original issue reported on code.google.com by
eamonn.f...@gmail.com
on 26 Oct 2010 at 11:01