New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ErrorCode 17999 #12808
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @jostster, which App Check provider(s) are being used in the project? |
We are using |
Looks like more users are seeing this according to our support team. Users have stated they haven't changed devices but maybe they have restored from backup or for some reason the system is holding on to an old token? |
In the case where the backup is creating the invalid state, the proposed fix for #12629 may address this. |
That is a possibility but I didn't see anything from that issue about 17999 error code. We have also asked users with this issue to delete and reinstall the application which they say isn't resolving their issue. I have added back code into our next release that will reset the attest key when a 17999 occurs. We will see if that resolves the issue. |
Description
iOS users randomly receive ErrorCode 17999
Could be a regression of #11926 which was fixed. I am unable to replicate this locally but many users are saying they are encountering this with some saying a re-install isn't resolving it.
I feel that the AppCheck token isn't being re-generated when a 17999 error is received.
Reproducing the issue
Unable to repro locally, but users just attempt to login with username / password using
signInWithEmailPassword
with AppCheck enabled.Firebase SDK Version
10.23.1
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
App Check, Authentication, Crashlytics, DynamicLinks
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetIf using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: