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

Social Media
#1

Build Used: 2014.2332 

Have added the following plugin to build.settings since I want to use admob-v2:

        [“plugin.google.play.services”] =

        {

            publisherId = “com.coronalabs”

        }, 

When executing the following line, the app hangs (Android) and the OS prompts that the app is not responding.

facebook.login( facebookAppID, facebookListener, { “publish_actions”,“user_friends” } )

If admob v1 (“CoronaProvider.ads.admob”) is used instead of “plugin.google.play.services”, the app doesnt hang.

With build 2014.2264 (first build with admob-v2), this problem does not exist. It seems to have creeped in sometime after that.

Please help fix this problem since I want to use the latest build, Facebook and AdMob v2.

#2

Can you put together a simple test app that shows the problem.  Make sure to include your build.settings and config.lua.  Then file a bug report using Report a bug above.

Engineering will need this before they can determine what the problem is.

Thanks

Rob

#3

The problem does not occur in the sample Facebook app. However in my app, the last build that it works properly on is 2014.2302

It fails on 2014.2303, so there could be some issue in whatever changed in this build.

The only difference between working and not-working in builds post 2014.2302 is the presence of “plugin.google.play.services” in build.settings

#4

In the build notes for 2014.2303 (in which the problem started to happen), the following entry is made (change in FB sdk):

http://developer.coronalabs.com/release/2014/2303

  • Android: Update the Facebook SDK to the version 3.14.1.
#5

Updating to that SDK is required by Facebook to support their V2 Graph API.  The iOS plugin has been using it for a week or so longer.  Since the problem doesn’t happen with the Facebook Sample app, we are going to need that example app that has the issue.  If you suspect it’s the AdMob v2 plugin, then you should be able to include it in the Facebook sample and duplicate the issue. 

Rob

#6

Hi

In fact i got the issue as well.  On Android also.

On my app when the call to facebook.login is done the app stay stucked. No specific errors in the logcat.

Same behavior as described by fstudios

If i remove  [“plugin.google.play.services”]  from my build then the facebook.login () line is working as expected.

And me neither, I could not manage to reproduce it in the sample app.

Has any body experienced this use-case as well?

The build i am using is:

2014.2325

#7

We need a filed bug report on this please.  Make sure to include your config.lua and build.settings in the zip file pleas.e

Thanks

Rob

#8

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.

#9

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

#10

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

#11

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

#12

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. 

#13

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.

#14

Thank you.

#15

Can you put together a simple test app that shows the problem.  Make sure to include your build.settings and config.lua.  Then file a bug report using Report a bug above.

Engineering will need this before they can determine what the problem is.

Thanks

Rob

#16

The problem does not occur in the sample Facebook app. However in my app, the last build that it works properly on is 2014.2302

It fails on 2014.2303, so there could be some issue in whatever changed in this build.

The only difference between working and not-working in builds post 2014.2302 is the presence of “plugin.google.play.services” in build.settings

#17

In the build notes for 2014.2303 (in which the problem started to happen), the following entry is made (change in FB sdk):

http://developer.coronalabs.com/release/2014/2303

  • Android: Update the Facebook SDK to the version 3.14.1.
#18

Updating to that SDK is required by Facebook to support their V2 Graph API.  The iOS plugin has been using it for a week or so longer.  Since the problem doesn’t happen with the Facebook Sample app, we are going to need that example app that has the issue.  If you suspect it’s the AdMob v2 plugin, then you should be able to include it in the Facebook sample and duplicate the issue. 

Rob

#19

Hi

In fact i got the issue as well.  On Android also.

On my app when the call to facebook.login is done the app stay stucked. No specific errors in the logcat.

Same behavior as described by fstudios

If i remove  [“plugin.google.play.services”]  from my build then the facebook.login () line is working as expected.

And me neither, I could not manage to reproduce it in the sample app.

Has any body experienced this use-case as well?

The build i am using is:

2014.2325

#20

We need a filed bug report on this please.  Make sure to include your config.lua and build.settings in the zip file pleas.e

Thanks

Rob