profile.setFBML broken? - RC2 (+ebswift's tutorial)

Oct 23, 2008 at 5:02 PM
Edited Oct 23, 2008 at 5:04 PM
Did Facebook just change something? My calls to profile.setFBML - which were working fine this morning - are now throwing exceptions.

Element is not an instance of type facebook.Schema.profile_setFBML_response

Dim result As Boolean = FH.Facebook.API.profile.setFBML(UserId, profileMarkup, wallMarkup, String.Empty)

[LinqToXsdException: Element is not an instance of type facebook.Schema.profile_setFBML_response]
Microsoft.Xml.Schema.Linq.XTypedServices.ToXTypedElement(XElement xe) +284
Microsoft.Xml.Schema.Linq.XTypedServices.Parse(String xml) +64
facebook.profile.setFBML(Int64 uid, String profile, String profile_main, String mobile_profile) +289
setup_form.SetFBML(Int32 swagId, Int32 binId, Int32 artistId) in C:\Clients\Websites\AT&T\att-facebook\setup-form.aspx.vb:83
setup_form.saveButton_Click(Object sender, EventArgs e) in C:\Clients\Websites\AT&T\att-facebook\setup-form.aspx.vb:57
System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e) +90
System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +76
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +177
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1746

Using the FB tools, I can see that the setFBML response looks like
<?xml version="1.0" encoding="UTF-8"?>

<profile_setFBML_response
xmlns="http://api.facebook.com/1.0/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://api.facebook.com/1.0/ http://api.facebook.com/1.0/facebook.xsd">
1
</profile_setFBML_response>


Though I dont know if that's what it was yesterday.

Oct 23, 2008 at 5:06 PM
Of course, the moment I post that, everything starts working again. Still, nothing has changed.
Oct 23, 2008 at 9:28 PM
I had a bunch of error emails come through with this error.  I guess Facebook were releasing untested changes yet again and had to rollback after they realised they'd broken their own website.