Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

iOS - Google Sign in - Revoked IDToken remains active until the token expire

未关闭
#531 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
32/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
ios, swift

调研方向

首先检查 GoogleSignIn 7.1.0 中围绕 GIDSignIn.sharedInstance.hasPreviousSignIn() 和 restorePreviousSignIn 的行为,然后将其与撤销权限后的 tokeninfo endpoint 进行比较。重现报告的延迟,并确定 SDK 是否提供在 token 过期前检测撤销的受支持方式;当预期行为及其处理方式已记录,或已由经过验证的修复覆盖时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

bug

I'm using - GoogleSignIn (7.1.0) framework in my iOS application and I can see that the token seems valid until the expiration date is reached. I use the accepted approach as called has Previos Sign In and calling restorePrevios Sign in, but the received user object still contains the user's data. I have tried Apple and Facebook login, but both of them revoked the access as soon as the Application permission was revoked, only Google keep sending it.

The code snippet, I used:
(if GIDSignIn.sharedInstance.hasPreviousSignIn() {
GIDSignIn.sharedInstance.restorePreviousSignIn { user, error in)
}
})

I have also tried calling https://oauth2.googleapis.com/tokeninfo?id_token=\(idToken) which responded 200 after 15 minutes of the permission revoke, so it looks like the token is fully valid until the expiration data

It's important for us that the user can still access his account for some time and will be deleted in about 2 hours after the token creation, which is super annoying.
I have attached a screenshot about the GIDGoogleUser, which contains all the data, it was about 5 minutes after the permission revoke.

Image

主要语言
Objective-C
星标
751
派生
282
平均合并
4 天 20 小时
30 天内合并 PR
11

贡献指南

打开贡献指南

从这里开始

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

google/GoogleSignIn-iOS 的其他 Issue

查看 google/GoogleSignIn-iOS 的全部 Issue

相似的 Issue

更多 Objective-C Issue

把新 issue 发到你的邮箱

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