Issue 290 Still Occurring in 1.6.1: Blank window on log in.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using Android 3.0+, log in to Facebook using the mobile API
2. You will notice a blank white window with the words success.
3. A hack has been posted in Issue 290, but is not a proper fix.

What is the expected output? What do you see instead?
The expected output would be for the window to disappear on log in. Instead we 
have to use a timer to read the title window, but this is not an acceptable fix.

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

Please provide any additional information below.
Users commented in Issue 290 that it was still occurring in version 1.6.1 but 
bug was closed out.

Original issue reported on code.google.com by sondun2...@gmail.com on 28 Jun 2011 at 1:48

[GoogleCodeExporter]

Hmm, can you go to the MobileLoginWindow class and put a break point on line 
135 approx (the line where the if statement starts) to tell us what the 
location var is equal to (you could just trace it out too)?

Original comment by rovertn...@gmail.com on 30 Jun 2011 at 4:02

[GoogleCodeExporter]

In my case the location var is equal to:
https://www.facebook.com/connect/uiserver.php?app_id=xxx&method=permissions.requ
est&display=touch&next=http://www.facebook.com/connect/login_success.html&type=u
ser_agent&fbconnect=1&perms=read_stream,user_status,read_friendlists

Note: Replaced my app ID with xxx above.

Original comment by bjarnehe...@gmail.com on 13 Jul 2011 at 7:09

[GoogleCodeExporter]

That is the correct success url. Is your callback at least being called?

Original comment by rovertn...@gmail.com on 22 Jul 2011 at 8:01

[GoogleCodeExporter]

can you try adding this piece of code to approx line 110 of MobileLoginWindow 
(after the first event listener) and see if this works:

webView.addEventListener(
    Event.COMPLETE,
    handleLocationChange,
    false, 0, true
);

Original comment by rovertn...@gmail.com on 22 Jul 2011 at 8:40

[GoogleCodeExporter]

I will try this tonight. I the problem is the callback is not called. The 
that's why we must set a timer and continuously read the content for the word 
success. 

Original comment by sondun2...@gmail.com on 22 Jul 2011 at 9:51

[GoogleCodeExporter]

Did the fix work?

Original comment by rovertn...@gmail.com on 10 Aug 2011 at 3:15

[GoogleCodeExporter]

Adding the event listener worked for me on the Galaxy Tab 10.1. Can we get this 
change committed?

Original comment by jaaronf...@gmail.com on 1 Sep 2011 at 9:32

[GoogleCodeExporter]

Verified the issue and solution in GraphAPI_Source_1_7.zip as well.

Original comment by jasondi...@gmail.com on 7 Sep 2011 at 2:32

[GoogleCodeExporter]

Just committed this change. Looking to get it added to the release SWCs soon.

Original comment by ryanstew...@gmail.com on 17 Sep 2011 at 8:40

[GoogleCodeExporter]

Issue 329 has been merged into this issue.

Original comment by ryanstew...@gmail.com on 17 Sep 2011 at 8:41

[GoogleCodeExporter]

Original comment by ryanstew...@gmail.com on 17 Sep 2011 at 8:42

• Changed state: Accepted