I have never seen so many dropped connections on Facebook before. Today is really really bad. Every other page view is a dropped connection.
I hope this is fixed soon.
Offline
It does seem really bad right now. I'm just getting lots of page not found error on apps
Offline
Looking for a bug report but don't see one. They reported there were problems yesterday, but I'd have thought they'd have fixed it by now.
Offline
Any news when this is going to be resolved l... I love facebook but when every other click takes me to a connection reset and i have to refresh or try again 3 times before I can get anywhere it kinda takes the fun out of stuff!!
Offline
In case it's helpful, this is our experience with the problems and whenever we see the issue we click on other top apps to ensure issue is on FB end.
1. Problems have been occurring most of the week but intensified greatly over the last 48 hours
2. Most apps on FB were down on Friday for good portions of the day. By down, I mean frequent connection resets or for a period of time a new error message. It was affecting a number of the top 20 apps at the same time
a. 4PM - 6PM EST (1PM - 3PM PST)
b. 9PM - 10PM EST (6PM - 7PM PST)
c. 12AM - 1:30AM EST (9PM - 10:30PM PST)
3. We see all the same issues today:
a. 10:30AM - present EST (7:30AM - present PST)
It may appear to be back to normal for a few hours, but the underlying problem is there. The apps have not been stable for more than 12 hours straight since Thursday, but they are essentially unuseable on Friday and today for large portions of the day
Offline
The best thing to do is do what I do when sending API calls...
Ignore any errors and continue processing your code. Folks know when they see a blank page after clicking a link that it is a network or server issue and usually refresh the page anyway.
My logic, What do I care if Facebook sends me back error message 109 or 350 or whatever? Means something to them but to me means API failed so what?
The only time errors matter is in development. Then you need to know this info to fix your code. But once your code works it is a finished product. You can't fix (or code for) FB platform issues as it is their issues.
Reason last, why do you want your app to crash or hang or create giant log files with error messages beyond your control anyway?
I'm just offering this idea as the best work around for Facebook API errors on their side.
Example of how this has helped me: I was using the loggedinuser method of FB:name which was trashed by Facebook this week (and may be what is causing all these problem). The only affect this had on my app's profile boxes was a change in message from: "Hello Paul" to Hello" being displayed. Not that this would have been a trappable error, but the logic is the same. If they had sent back error 666 (loggeinuser no longer supported) on my call to SetFBML I would have ignored it and had the same results! ![]()
Testing for errors are only good on good services. Facebook API is not such a service as they change things constantly with no warning or explanation. Your million user app may work today and crash tomorrow regardless of how well your error checking is.
BTW error codes above are fictious as I don't waste time looking at them or their meaning (except in developing) ![]()
Last edited by ParadiseP01 (2008-04-12 10:03:13)
Offline
sweetsteve wrote:
Looking for a bug report but don't see one. They reported there were problems yesterday, but I'd have thought they'd have fixed it by now.
This is the bug:
http://bugs.developers.facebook.com/sho … gi?id=1960
It went up to P2 yesterday, but they still don't seem to have done anything about it. I guess P2 means "quite bad, but we're not gonna let it interrupt our weekend, since it's only apps which are affected"
Last edited by mikep (2008-04-12 10:08:20)
Offline
BTW the bug no is 1960
http://bugs.developers.facebook.com/sho … gi?id=1960
Offline
mikep wrote:
It went up to P2 yesterday, but they still don't seem to have done anything about it. I guess P2 means "quite bad, but we're not gonna let it interrupt our weekend, since it's only apps which are affected"
LMAO Good one mikep! ![]()
Only would change that to read: "quite bad, but we're not gonna let it interrupt our weekend, since it's only app" developers that will get blamed for it and users will just remove their apps making it easier for us to (mis)manage"
Last edited by ParadiseP01 (2008-04-12 10:19:52)
Offline