Replies: 3 comments 1 reply
-
Thanks for the feedback!
You should be able to use the same debug token for different hosts, but you have to set We can definitely improve the documentation to make it more clear. @hsubox76 Can you help with it?
#5512 will fix it and prints the token on subsequent reloads. At the meantime, you can find it by going to the
For example, you can use the same token in CI, another dev machine, etc. by setting |
Beta Was this translation helpful? Give feedback.
-
Adding a link to the docs page that needs to be changed, for reference: https://firebase.google.com/docs/app-check/web/debug-provider#with-npm |
Beta Was this translation helpful? Give feedback.
-
I made an edit in OP. |
Beta Was this translation helpful? Give feedback.
-
Edit: after seeing the replies, I finally realized that all of my original questions can be answered by one simple fact: the token is just a string stored in IndexedDB, then compared with remote server. I wouldn't have had any of these confusions if the doc had mentioned it's a non-magical string in IndexedDB, which (1) is by origin, (2) can be used in other places if you copy it over, (3) can be lost on clearing cache
Original:
I'm using appCheck + debug token + js sdk v9 + callable functions. After some trial and errors I was able to make it work as intended, but the AppCheck doc is fairly new, and I'm still confused about the debug token.
Some suggestions to the doc:
Some things I'm still confused about:
self.FIREBASE_APPCHECK_DEBUG_TOKEN = true
, the token will show in the devtools console only once , and never again on subsequent reloads. Well, what if I missed it? How do I get it again?Beta Was this translation helpful? Give feedback.
All reactions