Deliveries in-app login not working
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
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}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure from the Deliveries “Connect with Google account” button and inspect the logged SignInHubActivity and AuthSignInClient flow, using the supplied logcat output. Done means the account-selection popup appears and the synchronization login can proceed without the reported API_UNAVAILABLE failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100