Closed daviddomkar closed 9 months ago
I can't reproduce it...
I hope following these two examples help you out:
It would be surprising if this is windows only, but if it is, this should be reported to the Firebase team. It could be a bug in the firebase/app-check implementation
I can't reproduce it...
I hope following these two examples help you out:
- https://github.com/posva/nuxt--vuefire-example-spark-plan
- https://github.com/posva/nuxt--vuefire-example-blaze-plan
It would be surprising if this is windows only, but if it is, this should be reported to the Firebase team. It could be a bug in the firebase/app-check implementation
I appreciate your time trying to reproduce and for the links. After some more digging into this, I isolated the issue to the createToken
function of the Firebase Admin SDK AppCheck client. I reported my findings in the issue in Firebase Admin SDK repository: https://github.com/firebase/firebase-admin-node/issues/2308
Reproduction
https://github.com/DavidDomkar/firebase-appcheck-windows-error-reproduction
Steps to reproduce the bug
Expected behavior
I would expect no errors in the console when using useCollection or useDocument on the server during SSR and app check enabled.
Actual behavior
When doing useCollection or useDocument in setup function of the vue page/layout/component or app.vue with SSR enabled with app check on windows, server logs the following error to the console:
Additional information
I tested this on two windows machines, where this problem occurred. However, when I tested on macos, no errors were present.
I also tried setting up appcheck with ReCaptchaV3 and ReCaptchaEnterprise, but both have the same issue.
I tried changing node versions and downgrading dependencies, but nothing worked. (my environment is node 18.17.1)