Open orangecoloured opened 1 year ago
Another deploy, another logged vist
That's strange. Can you check if Ackee sends the correct CORS headers? Is the visit logged by a browser or by the deployment system? Scripts might ignore the CORS headers.
Looks like it's logged by the deployment system. When I visit the deployed snapshot I get proper response
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://ackee.rckt.cc/api. (Reason: CORS header โAccess-Control-Allow-Originโ missing). Status code: 204.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://ackee.rckt.cc/api. (Reason: CORS request did not succeed). Status code: (null).
Btw, I have a check for window
object for initialisation and tracking. So, weird if it's a request that's happening on the "backend" side.
Hello, I have exactly the same issue, let me know if I can give more details to help for the investigation
Same issue here. Give me a shout and I'll post what ever info is helping to debug this :) Thank you for an awesome analytics tool!
๐ Describe the bug
I have ackee and my website both hosted on netlify.
But I see requests logged from the preview builds.
๐ To Reproduce
Probably have the tracked app hosted on netlify and see this happening on deploy?
๐ก Expected behavior
I expected that the whitelisted origins prevent loggin requests from other sources.
๐ผ๏ธ Screenshots
โ๏ธ Environment