[co.hinge.app] Hinge

Affected app
Name:Hinge
Package id: co.hinge.app

Describe the bug
After uneventful install, I try to create an account using my phone number. Firebase Auth appears to reach out but encounters some kind of error, and I'm stuck at a white overlay with 3 pulsing lines, indicating GMS is waiting for a response. This screen never disappears, and I cannot proceed.

To Reproduce
Steps to reproduce the behavior:

1. Install Hinge
2. Click "Login with phone number"
3. Enter number, click next
4. See error

Expected behavior
I'm expecting a text verification number, but never get one.
System
Android Version: 11
Custom ROM: CalyxOS 2.2.0

microG
microG Core version: 0.2.17.204714-14(5e4ccf0)
microG Self-Check results: All checked

Additional context
Perhaps related to #1198
02-23 23:06:18.213 1925 1940 W System : A resource failed to call release. 02-23 23:06:18.342 25620 26404 W ConnectionTracker: Exception thrown while unbinding 02-23 23:06:18.342 25620 26404 W ConnectionTracker: java.lang.IllegalArgumentException: Service not registered: com.google.android.gms.measurement.internal.zzja@edf514f 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1781) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at android.app.ContextImpl.unbindService(ContextImpl.java:1874) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at android.content.ContextWrapper.unbindService(ContextWrapper.java:792) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at com.google.android.gms.common.stats.ConnectionTracker.a(SourceFile:1) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at com.google.android.gms.common.stats.ConnectionTracker.unbindService(SourceFile:6) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at com.google.android.gms.measurement.internal.zzjb.zzF(SourceFile:6) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at com.google.android.gms.measurement.internal.o5.a(SourceFile:5) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at com.google.android.gms.measurement.internal.e.run(SourceFile:5) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at java.util.concurrent.FutureTask.run(FutureTask.java:266) 02-23 23:06:18.342 25620 26404 W ConnectionTracker: at com.google.android.gms.measurement.internal.z2.run(SourceFile:6)

Start by reproducing Hinge phone-number sign-in on Android 11 with the reported microG and CalyxOS versions, using the Firebase Auth flow and the attached log as entry points. Compare the behavior with issue #1198 and determine why verification remains on the GMS loading overlay; done means the flow completes and a text verification code is received.