microg / microg/GmsCore

Tinder crashes upon using facebook.accountKit

Open
#693 21 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

I'm on a Pocophone F1 using LineageOS 16 and the newest NanoDroid with microg. Everything else works fine/as expected.

Steps to reproduce:

  1. Install Tinder via Play Store
  2. Open Tinder
  3. Try to login via phone number
  4. 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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the phone-number login flow on the reported LineageOS 16 and microG setup, then inspect the logcat around AccountKitActivity and PhoneContentController. Compare the failing ActivityNotFoundException and null intent behavior with the Android authentication flow; done means Tinder's phone login no longer immediately crashes in this environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
authentication, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.