microg / GmsCore

Free implementation of Play Services
https://microg.org
Apache License 2.0
8.38k stars 1.7k forks source link

Deliveries in-app login not working #423

Open exentio opened 7 years ago

exentio commented 7 years ago

Hi, I'm having an issue with Deliveries, I need to login to have synchronization. When I press the "Connect with Google account" button, there should be a popup asking which account I want to use for the login, but instead nothing happens. I'm posting here because I think it's a microG issue. There is the logcat part I think it's important

09-10 10:48:48.651  1578  1670 I ActivityManager: START u0 {act=com.google.android.gms.auth.GOOGLE_SIGN_IN cmp=de.orrs.deliveries/com.google.android.gms.auth.api.signin.internal.SignInHubActivity (has extras)} from uid 10130 on display 0
09-10 10:48:48.678  1578  4316 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms } U=0: not found
09-10 10:48:48.679  1578  4379 W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@567071c
09-10 10:48:48.679 12169 12329 E GmsClient: unable to connect to service: com.google.android.gms.measurement.START on com.google.android.gms
09-10 10:48:48.694  1578  4386 I ActivityManager: START u0 {act=com.google.android.gms.auth.GOOGLE_SIGN_IN pkg=com.google.android.gms (has extras)} from uid 10130 on display 0
09-10 10:48:48.695 12169 12169 W AuthSignInClient: Could not launch sign in Intent. Google Play Service is probably being updated...
09-10 10:48:48.705 12169 12169 W FA      : Service connection failed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
09-10 10:48:48.713  1578  1670 W InputMethodManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@cb0bf25 attribute=null, token = android.os.BinderProxy@75b98d0
09-10 10:48:48.887  1578  3253 D WifiStateMachine: updateCapabilities for config:PocketCube-38FCfalse,false
09-10 10:48:48.910  1578  3467 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms } U=0: not found
09-10 10:48:48.911  1578  4318 W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@d1cd8fa
09-10 10:48:48.911 12169 12329 E GmsClient: unable to connect to service: com.google.android.gms.measurement.START on com.google.android.gms
09-10 10:48:48.911 12169 12169 W FA      : Service connection failed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
09-10 10:48:48.912 12169 12329 E FA      : Failed to send current screen to service
09-10 10:48:48.912 12169 12329 E FA      : Discarding data. Failed to send event to service
09-10 10:48:48.916  1578  1670 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms } U=0: not found
09-10 10:48:48.917  1578  4434 W ActivityManager: Unbind failed: could not find connection for android.os.BinderProxy@ac0beab
09-10 10:48:48.917 12169 12329 E GmsClient: unable to connect to service: com.google.android.gms.measurement.START on com.google.android.gms
09-10 10:48:48.917 12169 12169 W FA      : Service connection failed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
Locash commented 7 years ago

Are you running the newest version of GmsCore 2.4.105gf289a13? Also What device and ROM are you using?

exentio commented 7 years ago

Yes, that's the version. My device is a Redmi 4 Prime (markw) with Resurrection Remix, Android 7.1.2 But actually also with Marshmallow I had the same issues, and a friend of mine with an OnePlus One and Omni 7.1.2 has this problem too

shujarafi commented 6 years ago

When I tap on Sign IN or cancel button nothing happens, Kitkat 4.4.4

Locash commented 6 years ago

@shujarafi I had that issue in gms releases from 2.4-81 to 2.4-105 on a device with stock kit Kat but not same device with Android 5 or 6 custom roms. This is a issue I think with device specific roms tweaked by manufacturers.But switching back to the 2.4-79 release it went back to working for me.

Here it is. https://microg.org/fdroid/repo/com.google.android.gms-10087438.apk

ale5000-git commented 6 years ago

@shujarafi @Locash Your bug is #368, it happens on all ROMs with KitKat.

RealVaVa commented 6 years ago
  1. not fixed?
chilliger commented 6 years ago

sign in with google does not work for me with LineageOS for microG (0.2.4-107) in Sign for Spotify and SofaScore

patrickdrd commented 5 years ago

same here:

W/AuthSignInClient(19332): Could not launch sign in Intent. Google Play Service is probably being updated...