New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vercel analytics "Awaiting data" #23
Comments
In fact, I have the same problem so I confirm that there is something wrong with this package. |
I have the same problem here, some updates? |
Same as #25 |
@iranagame I see. Thanks for your help. I see that your PR has been merged, but I still get same result. I've tried adding the module manually, but could It be that Vercel overrides with the old version? |
I'm afraid this issue is not the same as #25 @iranagame! Vercel provider sends event within body not query. (BTW 0.1.7 released with few improvements) @madsh93 Do you probably have a public URL I can check your deployment logs? |
Hi @pi0 yes absolutely! Https://kassebil.dk |
@pi0 Sorry for the wait! I've looked into this issue again. With a minimal reproduction repository, I've located the issue to when you add GA ID. Not sure what happens, but this is definitely here the issue lies. For now I've removed this, and I receive data on Vercel again.
EDIT: |
Sorry for the long wait! 😬 Is this still occurring for you? |
Not sure if this was fixed. But as I've replaced most of my code and no longer use Vercel Analytics I can't say if this is still an issue. I've closed it for now |
Hi
I am not sure the problem is this module, however Vercel refers to this module in their docs.
My problem is, I have enabled Vercel analytics and for a few months I have been getting "Awaiting data".
Vercel docs state I don't have to add this module manually, however it does not seem to make it work.
https://vercel.com/docs/analytics
Has anybody got Nuxt and Vercel analytics to work?
Edit: I have been in contact with the Vercel Support team, who tried re-enabling and re-deploying, with no success. They said it might be caused by having set Content Security Policy to disallow vitals.vercel-insights.com - which I have not.
The text was updated successfully, but these errors were encountered: