feat: Only log local debug tokens when not yet registered#95
Conversation
Updated `GACAppCheckDebugProvider` to only log the local debug token at app startup if it has not yet been successfully used. If the debug token has already been successfully exchanged for an App Check token in a previous run then it has already been registered in the Firebase Console. By only logging when necessary, developers may be more likely to notice when they need to re-register a debug token, such as when switching simulators or devices.
ncooke3
left a comment
There was a problem hiding this comment.
I'm exploring one small fix. The debug token is stored in a centralized spot. This registration flag should be on a per app basis, to avoid inaccuracies.
… and resourceName
To support multi-app environments (e.g., running multiple Firebase apps or configurations in the same simulator), namespace the debug token registration status flag stored in UserDefaults.
|
|
Self: After merging, move release tag. |
This will go into upcoming AppCheckCore 11.3.0.
Updated
GACAppCheckDebugProviderto only log the local debug token at app startup if it has not yet been successfully used. If the debug token has already been successfully exchanged for an App Check token in a previous run then it has already been registered in the Firebase Console. By only logging when necessary, developers may be more likely to notice when they need to re-register a debug token, such as when switching simulators or devices.