Failed Google Sign-In Scott H Tech.

umalemon · July 17, 2018, 3:53pm

Corona’s latest daily builds have problems with Scott H Tech’s GoogleSignin.

2018.3311, 3312

There was no problem with 3319.

java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/android/gms/common/api/Api$zzf; 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : Java Stack Trace: 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.google.android.gms.auth.api.Auth.\<clinit\>(Unknown Source:0) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : plugin.googleSignIn.LuaLoader$signIn.invoke(LuaLoader.java:333) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.JavaToNativeShim.nativeTouchEvent(Native Method) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.JavaToNativeShim.touchEvent(JavaToNativeShim.java:430) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.input.RaiseTouchEventTask.executeUsing(RaiseTouchEventTask.java:39) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.CoronaRuntimeTaskDispatcher$TaskEvent.Send(CoronaRuntimeTaskDispatcher.java:170) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.events.EventManager.sendEvents(EventManager.java:91) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.Controller.updateRuntimeState(Controller.java:308) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.graphics.opengl.CoronaGLSurfaceView$CoronaRenderer.onDrawFrame(CoronaGLSurfaceView.java:425) 07-18 00:45:46.884 25983 26498 I Corona&nbsp; : com.ansca.corona.graphics.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1623)

rob · July 17, 2018, 4:51pm

I’m confused. 3319 is newer than 3311. Can you confirm what version of Corona you’re having issues with? The latest public build is 3326 and the latest daily build is 3332.

Thanks

Rob

umalemon · July 17, 2018, 5:32pm

Sorry, Problem build 3331 and 3332.

umalemon · July 18, 2018, 12:49am

I sent a bug report here.

Maybe it is the form of the author.

https://goo.gl/forms/QjOJsFGghSEQqkJW2

anon63346430 · July 22, 2018, 7:21pm

Yes the latest daily build has completely broken the plugin and this is stopping me releasing updates!

rob · July 23, 2018, 2:16pm

@umalemon does your app fail with 3326?

Do you have a simple test app that demonstrates the failing?

Rob

umalemon · July 23, 2018, 4:04pm

@ Rob

I tried with 3326 and daily build 3334 but it was an error.

The error display is the same as my report.

googleSignIn.signIn ()

A problem has occurred with.

@ Rob

I tried with 3326 and daily build 3334 but it was an error.

The error display is the same as my report.

googleSignIn.signIn ()

A problem has occurred with.

googleSignIn.signIn(googleSignInID, nil,nil,function ( ev )  if (ev.isError == true) then   native.showAlert("Google Sign In", ev.error, {"Ok"})  else   native.showAlert("Signed In", json.encode(ev), {"Ok"})  end end)

rob · July 23, 2018, 8:59pm

The report you made went to the plugin developer. We do not have access to it. Please make a simple project that has the issue, put it in a .zip file and share it with us. The biggest difference between 3319 and 3326 is support for Android SDK 27 over 25. This is a required change as new apps created for Google Play have to use the new version next week. You can update with older API’s for some additional time. This update to support API level 27 also required updates to plugin support libraries and this is likely a case that the plugin developer will need to recompile and update his plugins.

While there isn’t much we can do about this, we would like to have a simple test case, so if the developer needs to have some back and forth with our engineers, we have a baseline to work with.

Thanks

Rob

anon63346430 · July 23, 2018, 9:46pm

And herein lies the problem with external plugin developers providing functionality that should probably be in core. After all, there is a Facebook plugin (internally supported) but not Google Play?

So lets say - hypothetically - that the plugin dev has decided to disappear/go on holiday/got too busy/abandoned his projects, then where does that leave the other devs that are relying on that plugin being maintained?

IMHO. plugins are a great extension but should not be relied upon to replace what should be core functionality.

umalemon · July 24, 2018, 12:32am

@ Rob

I contacted the developers last week, but I have no reply.

@ SGS

I am worried about that.

We do not have the way if they end support.

umalemon · July 30, 2018, 6:05am

Hello.

The plugin was updated and the problem was fixed.

I got a contact from the developer.

thank you everyone.

rob · July 17, 2018, 4:51pm

I’m confused. 3319 is newer than 3311. Can you confirm what version of Corona you’re having issues with? The latest public build is 3326 and the latest daily build is 3332.

Thanks

Rob

umalemon · July 17, 2018, 5:32pm

Sorry, Problem build 3331 and 3332.

umalemon · July 18, 2018, 12:49am

I sent a bug report here.

Maybe it is the form of the author.

https://goo.gl/forms/QjOJsFGghSEQqkJW2

anon63346430 · July 22, 2018, 7:21pm

Yes the latest daily build has completely broken the plugin and this is stopping me releasing updates!

rob · July 23, 2018, 2:16pm

@umalemon does your app fail with 3326?

Do you have a simple test app that demonstrates the failing?

Rob

umalemon · July 23, 2018, 4:04pm

@ Rob

I tried with 3326 and daily build 3334 but it was an error.

The error display is the same as my report.

googleSignIn.signIn ()

A problem has occurred with.

@ Rob

I tried with 3326 and daily build 3334 but it was an error.

The error display is the same as my report.

googleSignIn.signIn ()

A problem has occurred with.

googleSignIn.signIn(googleSignInID, nil,nil,function ( ev )  if (ev.isError == true) then   native.showAlert("Google Sign In", ev.error, {"Ok"})  else   native.showAlert("Signed In", json.encode(ev), {"Ok"})  end end)

rob · July 23, 2018, 8:59pm

The report you made went to the plugin developer. We do not have access to it. Please make a simple project that has the issue, put it in a .zip file and share it with us. The biggest difference between 3319 and 3326 is support for Android SDK 27 over 25. This is a required change as new apps created for Google Play have to use the new version next week. You can update with older API’s for some additional time. This update to support API level 27 also required updates to plugin support libraries and this is likely a case that the plugin developer will need to recompile and update his plugins.

While there isn’t much we can do about this, we would like to have a simple test case, so if the developer needs to have some back and forth with our engineers, we have a baseline to work with.

Thanks

Rob

anon63346430 · July 23, 2018, 9:46pm

And herein lies the problem with external plugin developers providing functionality that should probably be in core. After all, there is a Facebook plugin (internally supported) but not Google Play?

So lets say - hypothetically - that the plugin dev has decided to disappear/go on holiday/got too busy/abandoned his projects, then where does that leave the other devs that are relying on that plugin being maintained?

IMHO. plugins are a great extension but should not be relied upon to replace what should be core functionality.

umalemon · July 24, 2018, 12:32am

@ Rob

I contacted the developers last week, but I have no reply.

@ SGS

I am worried about that.

We do not have the way if they end support.