Events from Production not being tracked in posthog

Bug Description

Bug description

Hi, I have implemented posthog on multiple next js project never came accross this issue,

The events get tracked from localhost, but not from production, the error on browser console in production is this -

Attachment "productionPostHogIssues.PNG": https://us.posthog.com/uploaded_media/0194f4b3-ab13-0000-205a-a02c0510f640

Attachment "productionPostHogIssues.PNG": https://us.posthog.com/uploaded_media/0194f4b3-af8a-0000-2eb1-7e25dac67c56

'use client';

import { Elements } from '@stripe/react-stripe-js';
import { loadStripe } from '@stripe/stripe-js';
import { QueryClientProvider } from '@tanstack/react-query';
import { NuqsAdapter } from 'nuqs/adapters/next/app';
import posthog from 'posthog-js';
import { PostHogProvider } from 'posthog-js/react';
import { useEffect } from 'react';

import { TooltipProvider } from '@/components/ui/tooltip';
import config from '@/config';
import { getQueryClient } from '@/lib/query-client';

const stripePromise = loadStripe(config.stripe.publishableKey);

export default function Providers({ children }: { children: React.ReactNode }) {
const queryClient = getQueryClient();

useEffect(() => {
posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY as string, {
ui_host: process.env.NEXT_PUBLIC_POSTHOG_HOST,
api_host: process.env.NEXT_PUBLIC_POSTHOG_HOST,
person_profiles: 'identified_only', // or 'always' to create profiles for anonymous users as well
});
}, []);

return (
<PostHogProvider client={posthog}>
<NuqsAdapter>
<Elements stripe={stripePromise}>
<QueryClientProvider client={queryClient}>
<TooltipProvider>{children}</TooltipProvider>
</QueryClientProvider>
</Elements>
</NuqsAdapter>
</PostHogProvider>
);
}

Please help I have been stuck with this for some time now

Debug info

- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

Start at the Providers entry point shown in the issue by reproducing the problem in the production deployment and inspecting the browser-console error and deployed NEXT_PUBLIC_POSTHOG_* values. Compare production initialization with localhost; done means production events reach PostHog without the reported error.