Why does Firebase pendingAuthResult return null when the app is killed?

未关闭
#1,045 10 条评论 4 个 reaction 已指派 1 人 在 GitHub 查看

@malcolmdeck 已经在做这个了。

开始于 2020年5月20日。

评估

这个 Issue 还没有评估数据。

描述

api: auth
Step 1: Describe your environment
  • Android device: Xiaomi Mi A1
  • Android OS version: Android 8.1.0
  • Google Play Services version: 4.3.3
  • Firebase-core version: 17.2.1
  • Firebase-auth version: 19.2.0
Step 2: Describe the problem:

When the app in the background is killed while performing Apple sign-in in Chrome, the authentication behaves inconsistently.

Steps to reproduce:
  1. Go to GenericIdpActivity
  2. Start the Apple sign-in flow
  3. Before finishing the sign-in flow, terminate the app in Android Studio to simulate system killing the app
  4. Finish signing in
  5. Both auth.currentUser and auth.pendingAuthResult are null in onStart()
Observed Results:

If I then restart the app, I am suddenly signed in and the pending result is present. And it doesn't disappear no matter what I do.

Expected Results:

The pending result shouldn't be null if the app is killed while in the background. That is the whole point of the pending result. Generally, the current behavior when the app is killed seems really inconsistent and buggy.

Related SO question:

https://stackoverflow.com/questions/59718353/why-does-firebase-pendingauthresult-return-null

主要语言
Kotlin
星标
9.3k
派生
7.4k
平均合并
7 天 9 小时
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

firebase/quickstart-android 的其他 Issue

查看 firebase/quickstart-android 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。