Help with new facebook auth -> white screen not returning to app nor executing callback after logging

[fern...@bliive.com]

Hi, there!

I am currently using Firebase together with Phonegap. On that scenario, I am trying to register users using facebook oauth (the new version which was released few days ago).

Hence, I must use authWithOAuthPopup, and Phonegap cannot handle redirect.


When I firstly call authWithOAuthPopup, the facebook page correctly appears, asking for the user permissions. However, when the app gets the permissions, the screen turns blank and nothing else happens. I can check that the application managed to get the permissions, and because of that, if I call authWithOAuthPopup again, a white screen appears without ever closing.

It seems that the internal browser used for that authentication is never closed, and hence it does not call the authWithOAuthPopup callback.


Has anyone else experienced this issue, knowing how to proceed?
I googled a lot and found some instances of the same issues, but on different environments (and usually without solutions..)


Thanks in advance,
Fernando.

[fern...@bliive.com]

Hey!
I discovered my problem, so I am leaving here how I corrected it, if it may be useful to somebody experiencing the same.

I realized that the last page that appeared on my app was a firebase's page ending in /blank/page.html#_=_

Based on that, I checked that firebase.js has a condition to close the current browser if a && a.url && (a = hc(a.url), a.host === ne && "/blank/page.html" === a.pb, which I changed to a && a.url && (a = hc(a.url), a.host === ne && ("/blank/page.html" === a.pb || "/blank/page.html#_=_" === a.pb), to cover my case.

I don't know why I get a #_=_ on the end of the link, but I can affirm that this happened on 2 android devices with two different versions of android. After the change I made, the browser inAppBrowser closed correctly and then it returned to my app, everything good now! :)


Best regards

[Rob DiMarco]

Hi Fernando -

Thanks for the report! We'll get this sorted out ASAP, and will release a fix in the next 24 hours.

Thanks -

Rob DiMarco

Engineer @ Firebase

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rob DiMarco]

Hi Fernando -

Thanks for your patience as I tracked this down and got it sorted out.

We've just released a new version of the Firebase Web Client (v1.1.1) which fixes known issues regarding redirect-based OAuth both on desktop web and PhoneGap / Cordova.

When you get a moment, check out the latest at https://cdn.firebase.com/js/client/1.1.1/firebase.js and let us know if you continue to run into any trouble.

Thanks -

Rob DiMarco
Engineer @ Firebase

[Fernando HG]

Hi Rob,

I have tested this version, and I don't experience the issue on it! :)

Thanks for the attention,

You received this message because you are subscribed to a topic in the Google Groups "Firebase Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebase-talk/NPdIj758MU0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebase-tal...@googlegroups.com.

[Rob Groenendaal]

Hi Rob,

I'm having the same issue on Android. After pressing the Facebook logon button I get redirected to Facebook and enter my credentials, after that the page goes blank and stays there forever.

Already tried with Firebase 1.1.1 but same result (also the fix as Fernando did not fix it for me).

I'm testing on Android 4.4.4

Best regards,

Rob Groenendaal

Op vrijdag 10 oktober 2014 07:57:52 UTC+8 schreef Rob DiMarco:

[Rob DiMarco]

Hi Rob -

Can you ping me off-list and we can dig into the details? We'll update the main thread once we've tracked down the issue, so that others can make use of the information.

Thanks -

Rob DiMarco

Engineer @ Firebase

[Rob Groenendaal]

Hi Rob,

thanks for helping me out off-site.

For everyone else facing the same problem, check if you installed the inAppBrowser.

I thought I had installed it, but apparently is was missing. Added it and the solution worked as expected.

Best regards

Rob Groenendaal

 

Op zaterdag 18 oktober 2014 00:57:25 UTC+8 schreef Rob DiMarco: