search

microg / GmsCore

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

[co.hinge.app] Hinge #1404

Open atomspring opened 3 years ago

atomspring commented 3 years ago

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)

marxistvegan commented 2 years ago

Anyone figure out a solution to this?

robinpaulson commented 2 years ago

Yeah, I'm getting a similar response when I use Hinge. The system asks for permission to show GMS over other apps, disabling that makes the "white overlay with 3 pulsing lines" disappear. I don't get a text message. When the overlay disappears, I'm left with a box to enter the verification code. Either entering a random code and pressing "Next" or leaving it produces the toast "Oof, looks like a bug at our end, we'll get right on to that" or similar words.

Android 9/Lineage 16 v0.2.24.214816 (the latest available)

For what it's worth, Bumble uses a very similar method and works flawlessly.

DiddlyDongDo commented 2 years ago

I'm also getting this same issue, I have previously been able to get around if you can restore from a functionion version of the app using TitaniumBackup from another phone with full google play services. The App itself works just fine on microg after initalization/setup. It just won't authenticate with microG. I'm willing to help however necessary to get this fixed. Simliar issue on #1281.

Android 11/Lineage OS 18.1 v0.2.24.214816

mathew2214 commented 2 years ago

I'm also getting this same issue, I have previously been able to get around if you can restore from a functionion version of the app using TitaniumBackup from another phone with full google play services. The App itself works just fine on microg after initalization/setup. It just won't authenticate with microG. I'm willing to help however necessary to get this fixed. Simliar issue on #1281.

Android 11/Lineage OS 18.1 v0.2.24.214816

that doesnt work. the Hinge app insists it needs uninstalled and reinstalled from the play store

DiddlyDongDo commented 2 years ago

I'm also getting this same issue, I have previously been able to get around if you can restore from a functionion version of the app using TitaniumBackup from another phone with full google play services. The App itself works just fine on microg after initalization/setup. It just won't authenticate with microG. I'm willing to help however necessary to get this fixed. Simliar issue on #1281. Android 11/Lineage OS 18.1 v0.2.24.214816

that doesnt work. the Hinge app insists it needs uninstalled and reinstalled from the play store

Hi, I must have missed a step. After restoring it go into the aurora store and manually check and re-install the newest update over it. I have not been using Hinge recently, and you can also use migrate to back it up from a working environment to a microg based environment.

tslocum commented 1 year ago

I was able to register for a new Hinge account just now without restoring any Hinge app data. I have Hinge version 9.12.2 and MicroG 0.2.27.223616 installed. Normally the registration would get stuck during the verification process, but this time it verified successfully. The registration process still got stuck later on, but after force closing and reopening Hinge I was presented with the usual welcome screen for newly registered accounts. I have not experienced any issues since.

dylangerdaly commented 1 year ago

This works now, I just successfully logged into Hinge with my phone number on the latest version of microG.

:+1:

robinpaulson commented 1 year ago

I can't get hinge to verify. Microg v0.28, Los 16, hinge 9.23. After entering my phone number and hitting next, this page opens in my browser:

https://hinge-layer-prod.firebaseapp.com/__/auth/handler?apiKey=AIzaSyB-apSzB00iSHaEIG-5nalT2DDVSAHcPXA&authType=verifyApp&apn=co.hinge.app&hl=en&eventId=dd3f121a-b629-43f6-97f1-789698d47484&v=XX21001000&eid=p&appName=%5BDEFAULT%5D&sha1Cert=7d5f1d2ace98a03b2c3a1a6b0dcb2b7f5d856f67&publicKey=CIfEyb8FEtwBCs8BCj10eXBlLmdvb2dsZWFwaXMuY29tL2dvb2dsZS5jcnlwdG8udGluay5FY2ll%0Ac0FlYWRIa2RmUHVibGljS2V5EosBEkQKBAgCEAMSOhI4CjB0eXBlLmdvb2dsZWFwaXMuY29tL2dv%0Ab2dsZS5jcnlwdG8udGluay5BZXNHY21LZXkSAhAQGAEYARogUQe_4S0Gj4MUkJa9R_6mBlG6-df8%0AkzjFVFSWTE7sUzciIQC5RWIbcXe_KRzoA_MhDsDxMCt0IZRqivo-VCiAxU0qZRgDEAEYh8TJvwUg%0AAQ%3D%3D%0A

alex1632 commented 1 year ago

Same here. The Link only seems to process in Android's default browser (which you have to reset to if you use something else). Even after checking the captcha, it tries to redirect and returns with a message saying "no such app". I can also see F-Droid popping up for a fraction of a second, but there, Hinge is of course not listed.

LineageOS 19, MicroG 0.2.28.231657, Hinge 9.23, 9.24 tested. Android Log does not say anything about that issue, sadly.

alex1632 commented 1 year ago

ok, it seems I figured a way out. Use the Fulguris Browser if you have F-Droid, because it redirects correctly. Also used Hinge 9.26. Works just fine. You can switch back the browser app on your phone afterwards.