[Bug] Canceling Facebook Login Issue With Android

Social Media
#1

When I tap an FB Connect button, the standard FB login screen comes up.  With my iOS version of the app, if I close this FB login screen without entering FB credential and return to my app, the app recognizes this and resume without any problem.  However, with the Android version of the same app, if I close the FB login screen without entering FB credential, I get the repeat of the following on my terminal forever and ever until I force kill the app:

I/Corona  ( 7674): event.name = fbconnect

I/Corona  ( 7674): event.type = session

I/Corona  ( 7674): event.token = nil

I/Corona  ( 7674): isError = false

I/Corona  ( 7674): didComplete = nil

I/Corona  ( 7674): Session Status = loginCancelled

Note:  The terminal command I use to monitor this is ./adb logcat Corona:V *:S

I tried this on both Daily Build 1041 and 1054, and they behave exactly the same.

I tested this on FBTest project I filed with CoronaLabs a while back, and it has similar effect, except the terminal output is slightly different.  The following repeatedly rolls out in rapid succession.

I/Corona  ( 9629): event.name = fbconnect

I/Corona  ( 9629): event.type = session

I/Corona  ( 9629): event.token = nil

I/Corona  ( 9629): isError = false

I/Corona  ( 9629): didComplete = nil

I/Corona  ( 9629): Session Status: logout

Is there a different set of code for Android build that I need to add to handle Facebook cancellation/logout event to solve this problem?

Naomi

#2

I filed a bug report for this:  Case 21863

 

I tested this on Nexus 4.

 

BTW, I close FB login screen by tapping on X button.

 

Naomi 

#3

I filed a bug report for this:  Case 21863

 

I tested this on Nexus 4.

 

BTW, I close FB login screen by tapping on X button.

 

Naomi 

#4

This is a major problem with Kindle version of the app.  Unlike the non-Kindle devices (btw, I haven’t looked into Nook yet)  I don’t know how I may force kill the app on Kindle device.  With Galaxy devices and Nexus devices, I know I can force kill the app by going to the setting (outside the app), but with Kindle devices, it appears that only way for me to stop this suspended state and resume the app is to uninstall the app completely, reinstall and relaunch the app from scratch, losing all the saved data.

That just isn’t an option.

Am I missing something?

Naomi

Edit:  I found it.  Wow, it’s buried deep.  I can force quit the app with Kindle too (needed Google to figure this out.)  But honestly, this is so not elegant.

#5

This is a major problem with Kindle version of the app.  Unlike the non-Kindle devices (btw, I haven’t looked into Nook yet)  I don’t know how I may force kill the app on Kindle device.  With Galaxy devices and Nexus devices, I know I can force kill the app by going to the setting (outside the app), but with Kindle devices, it appears that only way for me to stop this suspended state and resume the app is to uninstall the app completely, reinstall and relaunch the app from scratch, losing all the saved data.

That just isn’t an option.

Am I missing something?

Naomi

Edit:  I found it.  Wow, it’s buried deep.  I can force quit the app with Kindle too (needed Google to figure this out.)  But honestly, this is so not elegant.