You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Referring to the docs here: https://vuefire.vuejs.org/guide/other-firebase-services.html#Other-Firebase-Services, I'm getting a FCM messaging object back from the getMessaging(firebaseApp) but the messaging object contains the incorrect vapid key, keeping me from using getToken() in the same firebase/messaging lib. I couldn't find anywhere in the docs how to attach the public vapid key to the vuefire.config.
Proposed solution
Could there be a way to have the vuefire.config in nuxt.config to have a holder to set the public vapid key so the messaging object from getMessaging has the correct key?
What problem is this solving
Referring to the docs here: https://vuefire.vuejs.org/guide/other-firebase-services.html#Other-Firebase-Services, I'm getting a FCM messaging object back from the getMessaging(firebaseApp) but the messaging object contains the incorrect vapid key, keeping me from using getToken() in the same firebase/messaging lib. I couldn't find anywhere in the docs how to attach the public vapid key to the vuefire.config.
Proposed solution
Could there be a way to have the vuefire.config in nuxt.config to have a holder to set the public vapid key so the messaging object from getMessaging has the correct key?
Describe alternatives you've considered
doesn't set the correct vapidKey either, not sure where it's even getting this key from.
Also I apologize, maybe this just needs to be a question?
The text was updated successfully, but these errors were encountered: