-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tinder crashes upon using facebook.accountKit #693
Comments
The exception looks kind of like #689 . Might be the same thing; what is the expected output? |
Huh. I actually looked at your issue before while searching for a solution, strange I didn't notice this. Sure could be! The first 4 screens show the procedure, screen 2 is the expected output. The app crashes right after activating the "Login with phone number" button with the error(s) mentioned in the OP, but doesn't crash while activating the other two buttons. |
I googled some stuff about getting phone numbers to log in with gms, and found https://developers.google.com/android/reference/com/google/android/gms/auth/api/credentials/CredentialsApi . Maybe it has to do with this? Btw, I don't know anything about android dev. |
Doesn't explain what happens if the intent is null though 🤔 (Still don't know anything about android dev, but is this actually a microG problem? It doesn't seem like this is part of the google play stuff.) |
Well, looks like nobody else has interest and/or the ability to at least point us in the right direction. |
It appears it is a missing part in microg copying the Firebase functionality. Marvin will focus on microg with quite an amount of time from march on (See here). However, I do not know if this will be within his immediate focus. Overall I would advise not to update apps reliant on GSF if not absolutely necessary (and then make only the smallest version jump possible), as the API changed a lot, which has not been followed by microg yet. |
Thank you so much for your answer! That explains a lot of issues I had with different apps. Ah well, Marvins work with this project is simply awesome and I can't even begin to grasp the amount of time and knowledge he continues to pour into it. It'd be nice to have this growing issue fixed asap, but, as we all know, this project lives and dies with the volunteers sacrificing their free time to push the ongoing development forward. So no complains here, simply gratitude. In the meantime, I'm SOL, though. The few apps I use which rely on GSF aren't available in APK form, at least from "trustworthy" sources. Especially older versions. Again, thanks for the update! |
Short update from me: I managed to aquire a few older APKs regarding the apps with issues. It doesn't seem to be a problem regarding the current Firebase implementation, since even APKs from 2017 show the same or this issue:
I can still use that account from other devices, so I'm pretty sure that this is some deeper issue regarding microg, not necessarily the Firebase implementation. I'll logcat the behaviour later today and post ist. |
This issue seems to be fixed in latest versions of tinder/microg, can go through the phone auth flow without crash |
Still the same issue for me, are you using the official microg sources or NanoDroid? I might have to try the LineageOS for microg ROM. |
So I just flashed and setup the latest LOS16+microg ROM for my device (berrylium) and the issue still persists. Would you mind describing your setup? |
@Strel0ka LOS15+microg from for oneplus3, i fetched the android app bundle using https://github.com/onyxbits/raccoon4 and then installed the split apks with https://github.com/Aefyr/SAI (because latest versions of tinder are only distributed as AABs I can't seem to install them with yalp/aurora) |
@crushv Maybe this is a device/LOS16 specific bug. I installed the NanoDroid Playstore on top of the latest LOS16+microg and got the app that way, i'll try your described approach in a few hours. I don't think it'll change anything, but who knows. Thanks! |
Another short push/update from me. I'm currently on the official Lineage16+microg ROM for beryllium and flashed the latest NanoDroid (with microG GmsCore (0.2.6.15181-75)) on top of it. The issue still persists, though I was able to find one other instance of this specific error in the meantime: Click. I'm rooted via magisk(v19), maybe this will help in a fix? |
Still an issue unfortunately. |
Still an issue. |
Looks like TikTok registration fails with the same issue:
|
I no longer have this issue after upgrading to LineageOS 17.1 (Android 10) |
This way tiktok is another issue: #1364 |
No longer an issue here either on 17.1 (guacamole), can anyone still reproduce this? |
I've reinstalled the app, logged in just fine and was greeted by a notice stating I was banned from the app. |
I'm on a Pocophone F1 using LineageOS 16 and the newest NanoDroid with microg. Everything else works fine/as expected.
Steps to reproduce:
Logcat:
The text was updated successfully, but these errors were encountered: