Skip to content
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

Region defaulting to eu1 in production environment #290

Open
abhishek-mavonic opened this issue Oct 25, 2024 · 2 comments
Open

Region defaulting to eu1 in production environment #290

abhishek-mavonic opened this issue Oct 25, 2024 · 2 comments

Comments

@abhishek-mavonic
Copy link

abhishek-mavonic commented Oct 25, 2024

Hi, This is an issue which I am facing just in production environment where the region is defaulting to eu1 even when I am explicitly passing in1 as region while initializing the sdk. While trying to run my app locally, the region is working as expected and send events to in1 region.

export async function initializeClevertap(): Promise<CleverTap> {
  const clevertapModule = await import("clevertap-web-sdk");

  clevertapModule.default.init(process.env.NEXT_PUBLIC_CLEVERTAP_ACCOUNT_ID || "", "in1");
  clevertapModule.default.privacy.push({ optOut: false });
  clevertapModule.default.privacy.push({ useIP: true });
  clevertapModule.default.setLogLevel(3);

  return clevertapModule.default;
}
@singhkunal2050
Copy link
Contributor

Hello @abhishek-mavonic ,
Have you verified the NEXT_PUBLIC_CLEVERTAP_ACCOUNT_ID env variable for the in1 region, Please ensure you are using it correctly in your production env.

@abhishek-mavonic
Copy link
Author

abhishek-mavonic commented Oct 25, 2024

@singhkunal2050 Yeah, NEXT_PUBLIC_CLEVERTAP_ACCOUNT_ID Env is added properly. Can you let me know in which cases can this issue happen even when in1 region is added explicitly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants