feat(appcheck): add helpful log for registering debug tokens#16232
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
|
Not putting the debug token itself in this new log message to prevent accidental leaks. |
If the debug provider fails to return a valid FAC token, assume the token is unregistered. To assist developers, log a direct link to the Firebase console where they can register the debug token printed at app startup.
As currently implemented, the project ID and app ID will be printed to the console (interpolated into the URL).
Precedent on logging these fields
firebase-ios-sdk/FirebaseDatabase/Sources/Api/FIRDatabase.m
Lines 74 to 75 in ed8932b
firebase-ios-sdk/FirebaseRemoteConfig/Sources/RCNConfigFetch.m
Lines 668 to 669 in ed8932b
firebase-ios-sdk/FirebaseMessaging/Sources/Token/FIRMessagingTokenInfo.m
Lines 100 to 103 in ed8932b
Example (on attesting with unregistered debug token):
The last line from above is from the new log:
Verified it takes you to the debug token manager for the given app ID.
Tangential docs: cl/923512169
cc: @weixifan @andrewheard @rlazo