GmsCore: Tinder crashes upon using facebook.accountKit
I’m on a Pocophone F1 using LineageOS 16 and the newest NanoDroid with microg. Everything else works fine/as expected.
Steps to reproduce:
- Install Tinder via Play Store
- Open Tinder
- Try to login via phone number
- Immediate crash to home screen
Logcat:
01-18 19:32:25.630 15500 15500 E AndroidRuntime: FATAL EXCEPTION: main
01-18 19:32:25.630 15500 15500 E AndroidRuntime: Process: com.tinder, PID: 15500
01-18 19:32:25.630 15500 15500 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {com.tinder/com.facebook.accountkit.ui.AccountKitActivity}: android.content.ActivityNotFoundException: No Activity found to handle null
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3822)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3854)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1816)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6718)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: Caused by: android.content.ActivityNotFoundException: No Activity found to handle null
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2007)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.Activity.startIntentSenderForResultInner(Activity.java:4845)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.Activity.startIntentSenderForResult(Activity.java:4812)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.support.v4.app.FragmentActivity.startIntentSenderForResult(SourceFile:796)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.Activity.startIntentSenderForResult(Activity.java:4779)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.support.v4.app.FragmentActivity.startIntentSenderForResult(SourceFile:781)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.facebook.accountkit.ui.PhoneContentController$d.c(SourceFile:499)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.facebook.accountkit.ui.PhoneContentController$d.b(SourceFile:478)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.facebook.accountkit.ui.PhoneContentController$d.a(SourceFile:410)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.facebook.accountkit.ui.PhoneContentController$d.a(SourceFile:273)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.facebook.accountkit.ui.af.onActivityCreated(SourceFile:66)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at com.facebook.accountkit.ui.PhoneContentController$d.onActivityCreated(SourceFile:204)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.Fragment.performActivityCreated(Fragment.java:2531)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1318)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentManagerImpl.addAddedFragments(FragmentManager.java:2426)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2205)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2161)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2062)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentManagerImpl.dispatchMoveToState(FragmentManager.java:3051)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:3008)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.FragmentController.dispatchResume(FragmentController.java:204)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.Activity.performResume(Activity.java:7322)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3814)
01-18 19:32:25.630 15500 15500 E AndroidRuntime: ... 11 more
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 1
- Comments: 21
Looks like TikTok registration fails with the same issue:
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. For know you can only use an older version of failing apps.
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.