Android Samsung Firebase身份验证UID有时仅返回数字
最近，我注意到使用Firebase身份验证的某些Android三星设备已将其用户UID从字母和数字（例如：A123FASDFIJ123T9IASDFLJ112FD）更改为仅数字（例如：14912412412341923419287364123）。
这很令人困惑，因为我认为Firebase身份验证UID是恒定的，不应该改变。
我收到的报告来自三星用户，特别是运行Android 12。该操作系统上是否有可能引起此问题的东西，例如以不同的方式匿名化Firebase身份验证ID？
我正在获得Firebase身份验证UID如下：
FirebaseAuth.getInstance().currentUser.element.uid
编辑：在2015年通过此帖子阅读，Google宣布他们正在从Integer UID变为GUID格式。因此，我的某些用户可能使用多个设备，其中一些设备从2015年或之前设置了UID，这可能会在多设备方案中引起冲突。也许这是一种可能的解释。 https://groups.google.com/g/g/firebase-talk/c/c/c/c/c/c/c/c/c/ S9MV4S46QS0
Recently I'm noticing that some Android Samsung devices using Firebase authentication have changed their user UIDs from letters and numbers (for example: A123fASDFij123t9iasdflj112fd) to only numbers (for example: 149124123419287364123).
This is quite puzzling, because I thought Firebase authentication UIDs are constant and shouldn't change.
The reports I've gotten are from Samsung users, in particular running Android 12. Is there something on that OS that might be causing this issue, such as anonymizing Firebase authentication IDs in a different way?
I am getting the Firebase authentication UID as follows:
FirebaseAuth.getInstance().currentUser.element.uid
Edit: Was reading through this post in 2015, which Google announced they're changing from integer uid to GUID format. So it's possible some of my users are using multiple devices, and some of those devices had a uid set from 2015 or prior, which might be causing a conflict in multi device scenarios. Maybe that's one possible explanation.
https://groups.google.com/g/firebase-talk/c/s9mv4S46Qs0
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论