Pink box containing "This page contains the following errors: ..." after login.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.App running on BlackBerry PlayBook, no code change since it previously worked.
2.Login.
3.See error message: "This page contains the following errors:

error on line 2 at column 206: EntityRef: expecting ';'

Below is a rendering of the page up to the first error."

What is the expected output? What do you see instead?

The login should succeed and the web view should disappear.

What version of the product are you using? On what operating system?

1.7 (latest) on PlayBook

Original issue reported on code.google.com by daniel.b...@gmail.com on 9 Sep 2011 at 3:15

Attachments:

• Error1.png

[GoogleCodeExporter]

The following may be related:

http://mrrena.blogspot.com/2009/07/entityref-expecting-at-line-1.html

This would seem to suggest that somewhere, some XML contains ampersands, and it 
is expecting them to be of the form:

&

... but they are just bare &.

Who knows, but it's a thought.

Original comment by daniel.b...@gmail.com on 9 Sep 2011 at 3:19

[GoogleCodeExporter]

I see the same issue on Playbook, however, on Android things work properly. The 
code base to access Facebook is a shared class between the two projects and 
both environments are using 1.7. Also, I had no code changes from the time 
things were working on Playbook to when they failed. 

Any thoughts on where to start debugging?

Regards,
Rajesh

Original comment by rajesh.c...@gmail.com on 11 Sep 2011 at 10:23

[GoogleCodeExporter]

This issue is being caused because of some changes in the Facebook apis.

Read this:
http://bugs.developers.facebook.net/show_bug.cgi?id=20388

Looks like the content-type of the response is returned as "text/xml" instead 
of "text/html". This issue has been reported on iOS as well and on iPhone it is 
being resolved by updating the Facebook App. Some of them are also suggesting 
adding request headers to set the USER-AGENT to something else (such as 
Mozilla, etc). as the content-type returned is based on this.

On Playbook this issue is still prevails and updating or deleting the "Facebook 
App" does nothing. StageWebView doesn't give us any option to add any custom 
request headers.

This is a nasty situation. I have a major App release that relies totally on 
Facebook Connect. It was scheduled to release a couple of days back but we 
pulled it off because this issue started sometime on September 8.

Wondering what the next step should be?

1. Report a Bug on facebook (the current bug is reported specific to iOS but 
couldn't find it reported for the graph api in general). 
2. Report Bug for Playbook? - As this is happening only on Playbook - Same App 
on Android (Samsumg Galaxy S) works absolutely fine.
3. Report the issue with Adobe - StageWebView class sucks as all we can do is 
set a location and track its changes - Which aren't consistent on all platforms!

Original comment by chetan.m...@gmail.com on 14 Sep 2011 at 6:47

[GoogleCodeExporter]

Found a temporary fix for the issue which can be used until Facebook resolves 
this bug. Basically we have to change the display="touch" with display="popup" 
in the following code in the AS3 graph API:

1. MobileLoginWindow.as - Line# 121.

Change
vars.display="touch";
to
vars.display="popup";

2. Facebook.as - Line# 213-214

Change
display:String = "touch";
to
display:String = "popup";

This solved the issue for me. Although the UI now looks very different and not 
very "touch friendly" (buttons are too small). At least it works for the moment.

Vote for this bug http://bugs.developers.facebook.net/show_bug.cgi?id=20430 to 
escalate it's priority.

Original comment by chetan.m...@gmail.com on 14 Sep 2011 at 7:18

[GoogleCodeExporter]

Sigh, I came to the same conclusion and entered a different bug at Facebook:
http://bugs.developers.facebook.net/show_bug.cgi?id=20617

Regards,
Rajesh

Original comment by rajesh.c...@gmail.com on 14 Sep 2011 at 11:51

[GoogleCodeExporter]

thanks chetan, your solution works great. I would have never thought to do that.

Original comment by kamilsal...@gmail.com on 20 Sep 2011 at 4:19

[GoogleCodeExporter]

chetan, thank you so much for this solution! This would have been a breaker for 
the playbook version of my app!

Original comment by marc.wei...@googlemail.com on 10 Nov 2011 at 10:25