Facebook Developers

it's driving me nuts! my users want my blood because they're getting "connection reset" all the time and there's nothing i can do to fix it but wait!

AAARRRGGGHH!!

no it isnt a geographic thing

everyone is getting them all over the world at least by the complaints ive received from my users...

connection reset is an apache setting so something isnt working on fb's web servers

We have been experiencing site-wide difficulties today. Applications may experience ‘Connection Reset’ and other timeout errors during this period. We are aware of this problem and are working on a fix.


Matt Choi

the problem is that the facebook developers were so worried about getting facebook up and running before their deadline that they didn't look everything over so the whole site is basically falling apart. there have been things happening ever since facebook started all becasue the developers didn't think they needed to check over their work.

yes that is a good way to fix some of the problems, true that it won't fix everything but it will help with the connection timing out. The reason the connection is timing out is b/c the facebook page itself gets cut off from recieving information from the developers site, all because facebook doesn't follow anything properly and doesn't test their crap before they put it out.

Last edited by Dick6669 (2008-04-12 03:57:51)

Yes I have been working on one but I have not figured it all out. I have a great rating and about 40 fans. My problem is I don't know how to add an add application button  and will need a picture grid  would also like to allow the users to exchange gifts. Right now I am going a little nuts.  Oh yeah I'm the only one that can post on the wall. Seen a box for application url and the e-mail box is yellow.  Thanks  Stumped    http://www.facebook.com/apps/applicatio … 4531284257

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

Thanks God.

I thought it was just me.

This has happened, so far, on every browser I've tried:  Mozilla, Firefox, Safari, Netscape, Opera, and IE.

Getting a bit sick of the ol' Ctrl+R routine.  The apps will eventually load, but it takes a couple of refreshes sometimes.  It's still happening intermittently to me.

ParadiseP01 wrote:

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) 

I don't see how this is at all relevant for the current problem; API calls have nothing to do with the errors being experienced.

Hej in the forum
Funny, my app hash(head) been running without problems(I log in twice a day) maby becorse it issent acherly a facebook app yet, thou there have been NO connection problems, other then the usuel "trying to ion out the link" messege. I first heard about the problem on owned witch I log in to twice a day to, come to think about it around 5 hours ago there was some trouble, but that was with getting on facebook, wary commen guess its about the 1.000.000 users wanting to connect?!?
Hope the issue gets resolved.
The @ngel Man