Facebook Login hangs if "plugin.google.play.services" is included in the build settings

Social Media
#21

Ok i managed to find where it is coming from. (for us, not sue it’s the same for the pb mentioned in the first post, but seems like the same symptoms)

Short before the call to facebook.login we had a  native.setActivityIndicator( true )

We remove the line and the problems was gone.

So i can reproduce this behavior in the SampleApp if we add a  setActivityIndicator true.

With the plugin, the application get stuck after facebook.login() , without it’s ok.

I have no clue why removing the plugin remove the bugs. But now we know what to do to go on.

Not sure if you still need the bug report.

#22

Hi,

this issue was making me mad. Same issue as described. Moreover I can add that no every Android devices is affected. Os <= 4 have no problems. Ditto for Kindle ones. Samsung Galaxy 3 + have this problem. So there is no hash problem (in my case) cause facebook.login works on many devices except ones with Os 4+
I will try to change AdMob plugin for giving you my ultimate confirmation.

Thanks

#23

Can someone file a bug report please?  It needs your config.lua and build.settings in the zip file.  I can’t go to Engineering without it.

Please post the bug # back here (you will get it in an email after you file it)

Rob

#24

I can confirm that not setting native.setActivityIndicator( true ) fixes the problem. However is not a proper solution.

#25

After being asked to file a bug report twice, no one has done it. This thread and issue is still live, so someone, anyone, needs to file a bug report so that the Corona engineers can get to the bottom of the problem. 

#26

Ok i made a bug report already.

I joined build.setting, config.lua and also the main.lua of the facebook template modified.

 Case 33605 from the email akcnowledgement.

#27

Thank you.

#28

Hi Rob, 

Whats the update on this? I dont use setActivityIndicator but i use loadingSpinner and still face the same issue.

#29

I see the bug filed as been closed.  You have to cancel your loading spinner in your facebook event listener.  Are you saying the listener never fires?  Have you put in prints statements to see if its firing?  Are you looking at your device’s console log looking for errors?  Make sure to not filter just on the Corona activity.  Just run:

adb logcat

you’re going to get an excessive amount of messages, but you will just have to sort through them looking for errors from Google Play, Facebook or any print statements you add to your Corona app.

Rob

#30

Hi Rob, 

Whats the update on this? I dont use setActivityIndicator but i use loadingSpinner and still face the same issue.

#31

I see the bug filed as been closed.  You have to cancel your loading spinner in your facebook event listener.  Are you saying the listener never fires?  Have you put in prints statements to see if its firing?  Are you looking at your device’s console log looking for errors?  Make sure to not filter just on the Corona activity.  Just run:

adb logcat

you’re going to get an excessive amount of messages, but you will just have to sort through them looking for errors from Google Play, Facebook or any print statements you add to your Corona app.

Rob